This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
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.
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 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)
Welcome to Depfu 👋
This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
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 (~> 1.5.0 → ~> 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