🚨 [security] Update body-parser 1.19.0 → 2.0.0 (major) #139
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this 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?
✳️ body-parser (1.19.0 → 2.0.0) · Repo · Changelog
Security Advisories 🚨
🚨 body-parser vulnerable to denial of service when url encoding is enabled
Release Notes
2.0.0
1.20.3
1.20.2
1.20.1 (from changelog)
1.20.0
1.19.2
1.19.1
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.
Release Notes
3.1.2 (from changelog)
3.1.1 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 33 commits:
Release 3.1.2build: [email protected]build: [email protected]Fix return value for un-parsable stringsbuild: [email protected]Release 3.1.1build: [email protected]build: [email protected]docs: add documentation for "bytes" functionFix "thousandsSeparator" incorrecting formatting fractional partlint: include code in markdownbuild: [email protected]build: support Node.js 17.xdocs: add quotes around example in thousandsSeparatorbuild: [email protected]build: support Node.js 16.xbuild: support Node.js 15.xbuild: [email protected]build: [email protected]build: support Node.js 14.xbuild: support Node.js 13.xbuild: [email protected]build: [email protected]build: [email protected]build: [email protected]build: support Node.js 12.xbuild: [email protected]build: [email protected]build: use GitHub Actions instead of Travis CIbuild: [email protected]build: [email protected]build: [email protected]docs: fix npm version badgeRelease Notes
0.5.2 (from changelog)
0.5.1 (from changelog)
0.5.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 13 commits:
Release 0.5.2: Added getEncoder/getDecoder to .d.ts; minor devDependency fixes.Add getEncoder/getDecoder to typescript definitions. Fixes #229Switch code coverage checker from instanbul to c8Use iconv 2.x for tests, as 3.x dropped support of older Node versionsfix: semver fix version to 6.1.2Release 0.5.1: Added cp720 encoding (Persian/Farsi, #221)Added cp720 encoding (Persian/Farsi)Release 0.5.0: Added UTF-32 encodingUpdate .travis.ymlAdd support for UTF-32 (#216)Update README.mdUpdate README.mdUpdate README.md (#217)Release Notes
3.0.0 (from changelog)
2.5.2 (from changelog)
2.5.1 (from changelog)
2.5.0 (from changelog)
2.4.3 (from changelog)
2.4.2 (from changelog)
2.4.1 (from changelog)
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.
🆕 call-bind (added, 1.0.7)
🆕 define-data-property (added, 1.1.4)
🆕 es-define-property (added, 1.0.0)
🆕 es-errors (added, 1.3.0)
🆕 function-bind (added, 1.1.2)
🆕 get-intrinsic (added, 1.2.4)
🆕 gopd (added, 1.0.1)
🆕 has-property-descriptors (added, 1.0.2)
🆕 has-proto (added, 1.0.3)
🆕 hasown (added, 2.0.2)
🆕 object-inspect (added, 1.13.2)
🆕 set-function-length (added, 1.2.2)
🆕 side-channel (added, 1.0.6)
👉 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](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) 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