🚨 [security] Upgrade codecov: 2.3.1 → 3.6.5 (major)

[depfu]

---

🚨 Your version of codecov has known security vulnerabilities 🚨

Advisory: CVE-2020-7597
Disclosed: February 19, 2020
URL: https://nvd.nist.gov/vuln/detail/CVE-2020-7597

Moderate severity vulnerability that affects codecov

codecov-node npm module before 3.6.5 allows remote attackers to execute arbitrary commands.The value provided as part of the gcov-root argument is executed by the exec function within lib/codecov.js. This vulnerability exists due to an incomplete fix of CVE-2020-7596.

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

---

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?

✳️ codecov (2.3.1 → 3.6.5) · Repo

Release Notes

3.6.4

Fix for Cirrus CI

3.6.3

AWS Codebuild fixes + package updates

3.6.2

command line args sanitised

3.6.1

Fix for Semaphore

3.6.0

AWS CodeBuild
Semaphore v2

3.3.0

Added pipe --pipe, -l

3.1.0

Custom Yaml file
Token from .codecov.yml

3.0.4

Security fixes

3.0.3

Fix for not git repos

3.0.1

Fixing security vulnerability

3.0.0

Removed support for node 0.12

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

Sorry, we couldn't find anything useful about this release.

---

👉 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 #29.