🚨 [security] Update rake: 12.3.1 → 13.0.1 (major)

[depfu]

---

🚨 Your version of rake has known security vulnerabilities 🚨

Advisory: CVE-2020-8130
Disclosed: August 29, 2019
URL: https://github.com/advisories/GHSA-jppv-gw3r-w3q8

OS Command Injection in Rake

There is an OS command injection vulnerability in Ruby Rake < 12.3.3 in
Rake::FileList when supplying a filename that begins with the pipe character
|.

🚨 We recommend to merge and deploy this update as soon as possible! 🚨

---

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

↗️ rake (indirect, 12.3.1 → 13.0.1) · Repo · Changelog

Release Notes

13.0.1 (from changelog)

Bug fixes

• Fixed bug: Reenabled task raises previous exception on second invokation Pull Request #271 by thorsteneckel

• Fix an incorrectly resolved arg pattern Pull Request #327 by mjbellantoni

13.0.0 (from changelog)

Enhancements

• Follows recent changes on keyword arguments in ruby 2.7. Pull Request #326 by nobu

• Make `PackageTask` be able to omit parent directory while packing files Pull Request #310 by tonytonyjan

• Add order only dependency Pull Request #269 by take-cheeze

Compatibility changes

• Drop old ruby versions(< 2.2)

12.3.3 (from changelog)

Bug fixes

• Use the application's name in error message if a task is not found. Pull Request #303 by tmatilai

Enhancements:

• Use File.open explicitly.

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

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

---

👉 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)