Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update mocha 2.4.5 → 2.7.1 (minor) #477

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Dec 10, 2024

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.4.5 → 2.7.1) · Repo · Changelog

Release Notes

2.7.1 (from changelog)

External changes

  • Deprecate Configuration#stubbing_method_on_nil= (#694)
  • Indicate when parameter matcher logic is defined by block passed to Expectation#with (#698, b30e443)
  • Improve documentation for Expectation#with, especially when it is passed a block (#698, #682, #606 & #681)

2.7.0 (from changelog)

External changes

Internal changes

  • Workaround for JRuby jar-dependencies issue (#690)
  • Ruby v3.4 stacktrace uses single-quote vs backtick (#688 & #689) - thanks to Vít Ondruch

WARNING: This release fixes a very old bug

  • The bug relates to the use of Expectation#never in combination with other expectations on the same method.

  • Please ensure you fix the relevant deprecation warnings when running against v2.6.1 before upgrading to v2.7.0.

  • Previously, the following test would have passed, but now it will fail with an unexpected invocation error on the foo.bar line.

    foo = mock('foo') foo.stubs(:bar) foo.expects(:bar).never foo.bar

2.6.1 (from changelog)

External changes

  • Fix logic for displaying deprecation warning for expectation with never cardinality (#686) - thanks to @davidstosik for reporting

2.6.0 (from changelog)

External changes

  • Expectation with never cardinality should display deprecation warning (#681) - thanks to @ducmtran for reporting and testing

WARNING: This release results in some incorrect deprecation warnings:

  • The logic for displaying the deprecation warnings is fixed in v2.6.1 (#686).

Internal changes

  • Simplify backtrace related assertions (#680)
  • Remove unused ExpectationList#match_but_out_of_order (f2fa991)

2.5.0 (from changelog)

External changes

Internal changes

  • Fix jaro_winkler compilation errors on MacOS (5c7d14c)
  • Fix typos in IncludesTest test names (6fb5a5a)
  • Fix rubocop version constraint for Ruby > v2.2.0 (d5c6b98)

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

Commits

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


Depfu Status

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 depfu bot added dependencies Pull requests that update a dependency file Technical Debt labels Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file Technical Debt
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants