Update mocha: 1.14.0 → 1.15.0 (minor) #1080
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 (1.14.0 → 1.15.0) · Repo · Changelog
Release Notes
1.15.0 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 25 commits:
[skip ci] Update documentation for v1.15.0 releaseBump version to 1.15.0 & prepare for releaseDeprecate support for Ruby versions earlier than v2.0Extract handle_method_call from method_missingRemove unnecessary splatting in InvocationRemove ParametersMatcher from Invocation#call_descriptionFix typo in assert_method_visibility arg nameRemove redundant to_sym in AssertionsRemove redundant to_sym in MockeryRemove hook method method_body no longer neededMerge pull request #539 from freerange/fix-performance-testRun test:performance rake task on CISet Minitest.seed for test:performance taskRun test tasks before release tasksRemove support for Ruby v1.8Merge pull request #533 from freerange/consistent-definitions-for-respond-toAdd another example for API#sequenceFix examples using mock constructor with blockinclude_private -> include_all for respond_to?Make AnyInstance#respond_to? signature consistentConsistent naming for 2nd arg to respond_to?Require both args for Mock#respond_to_missing?Avoid arity check in Mock#respond_to_missing?Rely on Object#respond_to? in MockTestUpdate instructions for obtaining Rubygems API keyDepfu 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