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?
✳️ minitest (~> 5.4.2 → ~> 5.15.0) · Repo · Changelog
Release Notes
5.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 17 commits:
prepped for release- Fixed #skip_until for windows paths. (MSP-Greg)- Fixed marshalling of specs if they error. (tenderlove, jeremyevans, et al)Added minitest-heat to readme. (garrettdimon)Added failing test to show specs can't marshal if they raise. (jeremyevans)- Updated deprecation message for block expectations. (blowmage)- Use Kernel.warn directly in expectations in case CUT defines their own warn. (firien)+ Use Etc.nprocessors by default in order to maximize cpu usage. (tonytonyjan)+ Enable Ruby deprecation warnings by default. (casperisfine)Fixed typo for 5.0.0 in History.rdoc. (tnir)- Close then unlink tempfiles on Windows. (nobu)+ Added -S <CODES> option to skip reporting of certain types of outputRuby 1.9 is a taaad dead by now.Use assert_match instead of assert_equal to test the error message. (mame)Added rematch plugin reference in README (ddnexus)! assert_throws returns the value returned, if any. (volmer)updated ruby version statusDepfu 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