Upgrade rake to version 13.0.4

[depfu]

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.0 → ~> 13.0) · Repo · Changelog

Release Notes

13.0.4 (from changelog)

• Fix rake test loader swallowing useful error information. Pull request #367 by deivid-rodriguez

• Add -C/–directory option the same as GNU make. Pull request #376 by nobu

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 21 commits:

• Bump version to 13.0.4
• Merge pull request #386 from ruby/cleanup
• Use require_relative to specify release version
• Don't need to specify Rubygems version
• Extract gemspec and removed needless files
• Merge pull request #367 from deivid-rodriguez/remove_unhelpful_rescue
• Fix rake test loader swallowing useful error information
• Merge pull request #350 from jasonkarns/rule-prereq-symbol
• Merge pull request #374 from deivid-rodriguez/lazily_load_set
• Merge pull request #376 from nobu/directory-option
• Merge pull request #378 from nobu/suppress-warning
• Merge pull request #379 from deivid-rodriguez/remove_unnecessary_require
• Removed the deprecated test configurations
• Merge pull request #380 from olleolleolle/ci-yaml-quotes
• CI: use "3.0" to avoid YAML
• Remove unnecessary require
• Merge pull request #377 from nobu/update-test-versions
• Suppress deprecation warning for $\ since ruby 3.0
• Add recent ruby versions to test
• Add -C/--directory option the same as GNU make
• Lazily load `set`

---

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

• Circle CI, Semaphore and Travis-CI are all excellent options.
• If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
• If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with depfu/.

---

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)

[depfu]

Closed in favor of #7.