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 upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ mocha (>= 0.9.12, <=1.1.0 → >= 0.9.12, <= 1.13.0) · Repo · Changelog
Release Notes
1.13.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 21 commits:
[skip ci] Update documentation for v1.13.0 release
Bump version to 1.13.0 & prepare for release
Check documentation can be generated as part of CircleCI build
Add --fail-on-warning option to yard rake task
Add a weekly scheduled build to the CircleCI build
Add Ruby v1.8 to the CircleCI build matrix
Add API token to fix CircleCI badge in README
Add ParameterMatchers#has_keys
Provide wrapped option for #mocha_inspect on hashes & arrays
Fix misleading exception message in ParameterMatchers#has_entry
Use CircleCI instead of TravisCI for automated builds
Remove TravisCI config and associated files
Update documentation to replace refs to TravisCI with refs to CircleCI
Only add dependency on rubocop if we're actually going to use it
Fix rake dependency constraints for older Ruby versions
Configure CircleCI builds
Switch to newer default Travis CI build env
Use latest Ruby versions in Travis CI builds
Use latest JRuby v9.2.18 in Travis CI builds
Use consistent JRuby versions in Travis CI builds
Use more recent version of JRuby in Travis CI build matrix
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