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 merge
Merges this PR once your tests are passing and conflicts are resolved
@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?
✳️ rake (< 12.3 → <= 12.3.1) · Repo · Changelog
Commits
See the full diff on Github. The new version differs by 41 commits:
bump version to 12.3.1
Fixed rdoc style
rubocop -a
Merge pull request #262 from gfx/did_you_mean-v1.2.0
support did_you_mean >= v1.2.0 which has a breaking change on formatters
Merge pull request #252 from grzuy/fix_multitask_failures
Prefer #refute over negated #assert
Merge pull request #259 from grzuy/fix_leading_whitespaces
Keep original test case testing spaces in some arguments
Merge pull request #261 from aycabta/use-jruby-9.1.16.0
Use JRuby 9.1.16.0
Make space trimming consistent for all task arguments. Fixes #260
Merge pull request #258 from grzuy/ruby_2_5_ci
Merge pull request #254 from grzuy/remove_dup_inclusion
make AppVeyor test with ruby 2.5 also
Removes duplicated inclusion of Rake::DSL
Merge pull request #256 from ruby/avoid-install-needless-deps
To use gem install insteaad of bundle install
Merge pull request #253 from radar/patch-1
Remove date field from rake.gemspec
Don't run tasks if it depends on already invoked but failed task. Fixes #189
rubocop -a
Merge pull request #250 from dylanahsmith/re-raise-load-error-without-path
Re-raise a LoadError that didn't come from require in the test loader
Merge pull request #249 from esparta/fix_readme_minimal_ruby_version
[skip ci] Fix minimal ruby version on README
rubocop -a
Merge remote-tracking branch 'origin/v11'
prefer to use %x literal instead of back-tick
Support non-bundler environment
Merge pull request #244 from aycabta/2.5.0
Merge pull request #245 from aycabta/force-installation-bundler
Force installation Bundler
Use 2.5.0 and more latest Ruby versions
Merge pull request #242 from stomar/ftp-publishing
Add missing information on FTP publishing to README
Merge pull request #240 from aycabta/jruby-9.1.15.0
Use JRuby 9.1.15.0 on .travis.yml
Merge pull request #239 from donv/patch-1
[skip-ci] Fixed typo
bump release date
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