Update mocha 2.1.0 → 2.4.2 (minor)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ mocha (2.1.0 → 2.4.2) · Repo · Changelog

Release Notes

2.4.2 (from changelog)

External changes

• Don't trust Object#is_a? in presence of mock objects (#656) - thanks to @casperisfine

2.4.1 (from changelog)

External changes

• Fix regression in matchers when used with keyword arguments (#654 & #655) - thanks to @ElvinEfendi for reporting

Internal changes

• Reduce duplication & consolidate #to_matcher method definitions (600ee2a, e9de64e, #655)
• Change #to_matcher method to use keyword arguments (3b60b7d, #655)

2.4.0 (from changelog)

External changes

• Improve rendering of keyword arguments (#652) - thanks to @casperisfine

Internal changes

• Improvements to #mocha_inspect unit tests (#650)

2.3.0 (from changelog)

External changes

• Fix nested parameter matching for keyword arguments (f94e250, #648) - thanks to @CodingAnarchy for reporting

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 38 commits:

• [skip ci] Update documentation for v2.4.2
• Bump version to 2.4.2 & prepare for release
• Don't trust `Object#is_a?` in presence of Mocks
• [skip ci] Fix release notes for v2.4.1
• [skip ci] Update documentation for v2.4.1
• Bump version to 2.4.1 & prepare for release
• Merge pull request #655 from freerange/fix-has-entry-with-keyword-args-regression
• Change to_matcher method to take keyword arguments
• Consolidate to_matcher definitions in one place
• Reduce duplication in to_matcher methods
• Fix regression in ParameterMatchers#has_entry, etc
• [skip ci] Update documentation for v2.4.0
• Bump version to 2.4.0 & prepare for release
• Improve rendering of keyword arguments
• Improve unit tests for Hash#mocha_inspect
• Improve unit tests for Array#mocha_inspect
• [skip ci] Update documentation for v2.3.0
• Bump version to 2.3.0 & prepare for release
• Fix nested parameter matching for keyword arguments
• [skip ci] Update documentation for v2.2.0
• Bump version to 2.2.0 & prepare for release
• Include the original test name in expired stub error messages
• Drop support for Ruby v2.0
• Add Ruby v3.3 to CI build matrix
• Improve sequence failure message
• Add block syntax for sequences
• Add missing YARD tag for API#states name param
• Add missing YARD tag for API#sequence name param
• Use Ruby v1.9 Hash syntax in docs
• Merge pull request #626 from freerange/tidy-up-minitest-modules
• Use minitest vs mini_test everywhere
• Use Minitest vs MiniTest everywhere
• Do not require "minitest/unit"
• Reduce duplication in identifying Minitest version
• Support multiple methods in responds_with matcher
• Reinstate missing CNAME for GitHub Pages site
• [skip ci] Update docs to fix those for Mock#method_missing
• Avoid rubocop directive ending up in YARD docs

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[depfu]

Closed in favor of #418.