I don't want to jeopardise support for older versions of Ruby.

Even the reference in the documentation [1] suggests that you should
prefer alias_method vs alia...

I disabled the cop for the YamlEquivalent matcher, because it's possible
that classes not allowe...

Since eval is only used in a test, I'm happy to disable the cop in this
case.

Regexp#match? has only been available since Ruby v2.4 and I don't want
to jeopardise support for...

I've disabled the cop around monkey-patching code, because the whole
point is that this is copy-...

I've disabled the cop around monkey-patching code, because the whole
point is that this is copy-...

The other violations result in a "Infinite loop detected" when running
rubocop, so I'm going to ...

I've disable the cop around monkey-patching code, because the whole
point is that this is copy-p...

Note that auto-correct didn't work, so I fixed this manually.

I've disable the cop around monkey-patching code, because the whole
point is that this is copy-p...

For some reason the following violations were not automatically excluded
by the automatically ge...

I did this by running the following command:

rubocop --auto-gen-config

Given that the add_development_dependency method seems to have been a
method on Gem::Specificati...

The ">= 0" is the default constraint and I think it makes the code more
readable to omit it.

The Gem::VERSION constant was only introduced in Rubygems v1.3.2 [1].
Prior to this, the version...

The Rubyforge website no longer exists, nor have any redirects been
setup, despite multiple requ...

Given that *any* version of Rubygems will satisfy the ">= 0"
requirement, this line seems redund...

While this information is available in the following commits, this saves
us repeating the same g...

I think this is more idiomatic Ruby.

The current specification_version is 4. The only change from version 3
to version 4 appears to b...

Looking back through the gemspec history it looks as if this was the
intention of these conditio...

I can't see that this has ever been used.

It turns out that Travis CI doesn't support Ruby v2.1.11

The content was mostly stolen from this blog post [1].

Closes #236.

[1]: http://jamesmead.org/...

Change gem version badge to svg and add SemVer stability badge

This reverts commit 7a1a58d9b8760987f488e6404609e931e060f009.

We haven't got any backers or spo...

Avoid mocks for partial mocking leaking into subsequent tests

Previously ObjectMethods#mocha & ClassMethods::AnyInstance#mocha were
building mock objects for ...

Remove `ModuleMethod#method_exists?`

This is similar to the change in commit
8f58eddf0ff658ad255cf60cedab3c767bbb15c7.

Commit e87c03...

Prevent use of Mocha outside the context of a test/example

Hopefully this addresses #292.

If no Mockery has been instantiated when a call is made to any m...

Now that the Mockery instance is being explicitly instantiated and
destroyed, I think this resto...

Previously the Mockery singleton instance was lazily instantiated the
first time it was needed. ...

Both Mocha::Integration::MiniTest::Adapter and
Mocha::Integration::TestUnit::Adapter were alread...

This is a minor release, not just a patch release, because it introduces
at least one new deprec...

Define respond_to_missing? on Mocha::Mock

Fixes #321.

As of Ruby 2.4, Forwardable warns when delegating to a private method.
Warnings are...

Rename mocha/mini_test.rb to mocha/minitest.rb

* Deprecate requiring 'mocha/mini_test'
* Update documentation in README

As suggested in #289.

Display file and line number in deprecation warning

The newlines before and after each deprecation warning and
the multiple leading asterisks make t...

Fixes #312.

I've also removed the code which displayed the backtrace for
deprecation warnings i...

This is now redundant.

JRuby v9.1.15.0 was released on 07 Dec 2017 [1].

[1]: http://jruby.org/2017/12/07/jruby-9-1-15-...