🚨 [security] Update body-parser 1.19.1 → 2.0.0 (major) #228
+629
−85
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.1 → 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
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)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 5 commits:
Release 3.1.2build: [email protected]build: [email protected]Fix return value for un-parsable stringsbuild: [email protected]Release Notes
1.0.5
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 74 commits:
1.0.5build: [email protected]build: add version script for npm version releasesbuild: [email protected]build: [email protected]lint: apply standard 15 styleperf: skip value escaping when unnecessarytests: fix deep-equal assertionslint: remove deprecated String.prototype.substrbuild: support Node.js 19.xbuild: [email protected]build: [email protected]build: [email protected]lint: apply standard 14 stylebuild: [email protected]build: [email protected]build: [email protected]build: [email protected]build: support Node.js 18.xbuild: support Node.js 17.xlint: apply standard 13 stylebuild: [email protected]build: [email protected]build: [email protected]build: support Node.js 16.xbuild: support Node.js 15.xbuild: [email protected]build: [email protected]build: [email protected]build: support Node.js 14.xbuild: support Node.js 13.xbuild: support Node.js 12.xbuild: [email protected]build: support Node.js 11.xbuild: [email protected]build: [email protected]build: use GitHub Actions instead of Travis CIbuild: use nyc for coverage testingbuild: speed up logic in Travis CI build stepsbuild: [email protected]build: [email protected]build: [email protected]build: [email protected]build: [email protected]build: [email protected]build: [email protected]build: [email protected]build: restructure Travis CI build stepsbuild: migrate to Travis CI trusty imagebuild: [email protected]build: [email protected]lint: apply standard 12 styletests: use strict equalitytests: replace deprecated assert.deepEqual with deep-equaldocs: switch badges to badgenbuild: support Node.js 10.xbuild: [email protected]build: [email protected]build: [email protected]build: [email protected]build: [email protected]build: [email protected]build: [email protected]build: [email protected]build: [email protected]build: use yaml eslint configurationbuild: [email protected]build: [email protected]build: [email protected]doc: fix some formattinglint: apply standard 10 stylebuild: support Node.js 9.xbuild: [email protected]build: [email protected]Commits
See the full diff on Github. The new version differs by 26 commits:
v1.1.2[meta] add `auto-changelog`[Robustness] remove runtime dependency on all builtins except `.apply`[Dev Deps] update `@ljharb/eslint-config`, `aud`, `tape`[meta] add `funding` field; create FUNDING.yml[Tests] use `aud` instead of `npm audit`[meta] update `.gitignore`[Tests] switch to nyc for coverage[meta] add `safe-publish-latest`[Dev Deps] update `@ljharb/eslint-config`, `tape`[actions] fix permissionsRevert "Point to the correct file"Merge pull request #16 from svedova/patch-1Point to the correct file[readme] update badges[meta] use `npmignore` to autogenerate an npmignore file[Tests] migrate tests to Github Actions[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `tape`[meta] create SECURITY.md[Tests] fix eslint errors from #15[Dev Deps] update `@ljharb/eslint‑config`, `eslint`, `tape`[Tests] up to `node` `v11.10`, `v10.15`, `v9.11`, `v8.15`, `v6.16`, `v4.9`; use `nvm install-latest-npm`; run audit script in tests[Tests] add `npm run audit`[Tests] remove `jscs`[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `covert`, `tape`Docs: enable badges; update wordingRelease 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
1.13.2 (from changelog)
1.13.1 (from changelog)
1.13.0 (from changelog)
1.12.3 (from changelog)
1.12.2 (from changelog)
1.12.1 (from changelog)
1.12.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 45 commits:
v1.13.2[readme] update badges[Dev Deps] update `@ljharb/eslint-config`, `tape`[Fix] Don't throw when `global` is not defined[Dev Deps] update `globalthis`[Dev Deps] update `error-cause`[Dev Deps] update `error-cause`, `has-tostringtag`, `tape`[meta] add missing `engines.node`[Dev Deps] update `npmignore`[Dev Deps] update `mock-property`[Dev Deps] update `tape`v1.13.1[Fix] in IE 8, global can !== window despite them being prototypes of each otherv1.13.0[Dev Deps] update `error-cause`[Dev Deps] temporarily remove `aud` due to breaking change in transitive deps[New] add special handling for the global object[Dev Deps] pin `glob`, since v10.3.8+ requires a broken `jackspeak`[Dev Deps] update `mock-property`, `tape`[Dev Deps] update `tape`[Dev Deps] pin `jackspeak` since 2.1.2+ depends on npm aliases, which kill the install process in npm < 6[Dev Deps] update `@ljharb/eslint-config`, `aud`, `tape`v1.12.3[Fix] in eg FF 24, collections lack forEach[Dev Deps] update `@ljharb/eslint-config`, `aud`, `error-cause`[Dev Deps] update `aud`, `es-value-fixtures`, `tape`[actions] update rebase action to use reusable workflow[Tests] add `@pkgjs/support` to `postlint`v1.12.2[meta] add support info[Fix] ignore `cause` in node v16.9 and v16.10 where it has a bug[Fix] use `util.inspect` for a custom inspection symbol methodv1.12.1[Fix] properly handle callable regexes in older engines[meta] use `npmignore` to autogenerate an npmignore file[Dev Deps] update `@ljharb/eslint-config`, `error-cause`, `es-value-fixtures`, `functions-have-names`, `tape`[Tests] use `mock-property`[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `aud`, `auto-changelog`, `tape`v1.12.0[meta] fix auto-changelog settings[New] ensure an Error’s `cause` is displayed[Dev Deps] update `eslint`, `@ljharb/eslint-config`[Robustness] cache more prototype methods[New] add `numericSeparator` boolean option[Robustness] cache `RegExp.prototype.test`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)
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)
🆕 get-intrinsic (added, 1.2.4)
🆕 gopd (added, 1.0.1)
🆕 has-property-descriptors (added, 1.0.2)
🆕 has-proto (added, 1.0.3)
🆕 has-symbols (added, 1.0.3)
🆕 hasown (added, 2.0.2)
🆕 set-function-length (added, 1.2.2)
🆕 side-channel (added, 1.0.6)
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