Update body-parser 1.19.0 → 1.20.2 (minor) #2608
Open
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.
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?
✳️ body-parser (1.19.0 → 1.20.2) · Repo · Changelog
Release Notes
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
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]Release Notes
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.
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
This change is