Upgrade express: 4.16.3 → 4.17.0 (minor) #30
Closed
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 upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ express (4.16.3 → 4.17.0) · Repo · Changelog
Release Notes
4.17.0
4.16.4
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 73 commits:
4.17.0docs: remove Gratipay linkstests: ignore unreachable linebuild: update example dependenciesdeps: cookie@0.4.0build: support Node.js 12.xbuild: test against Node.js 13.x nightlybuild: Node.js@10.15deps: range-parser@~1.2.1deps: serve-static@1.14.1deps: send@0.17.1deps: finalhandler@~1.1.2build: support Node.js 11.xbuild: Node.js@8.16build: Node.js@6.17tests: add express.text test suiteAdd express.text to parse bodies into stringtests: add express.raw test suiteAdd express.raw to parse bodies into Bufferdeps: serve-static@1.14.0deps: send@0.17.0tests: add express.static test suitetests: add express.urlencoded test suitetests: add express.json test suitedeps: body-parser@1.19.0deps: qs@6.7.0deps: type-is@~1.6.18deps: accepts@~1.3.7deps: statuses@~1.5.0deps: setprototypeof@1.1.1docs: add link to contributing guidedeps: parseurl@~1.3.3deps: proxy-addr@~2.0.5deps: content-disposition@0.5.3build: marked@0.6.2build: hbs@4.0.4build: test against Node.js 12.x nightlytests: assert calls order in middleware basic testsdocs: use const in readme exampletests: fix typos in descriptionsdocs: fix typo in jsdoc commentdocs: add listening address to exampleexamples: minor fixes to some examplesdocs: fix typos in historydocs: fix typo in contributingSupport multiple hosts in X-Forwarded-HostImprove error message for null/undefined to res.statusImprove error message for non-strings to res.sendFilebuild: support Node.js 10.xbuild: support Node.js 9.xbuild: test against Node.js 11.x nightlybuild: coveralls@2.12.0tests: use supertest to perform assertions4.16.4build: update example dependenciesbuild: supertest@3.3.0build: mocha@5.2.0build: restructure CI build stepsFix issue where "Request aborted" may be logged in res.sendfiledeps: safe-buffer@5.1.2build: supertest@2.0.0deps: proxy-addr@~2.0.4deps: body-parser@1.18.3deps: qs@6.5.2lint: move removed middlewares list to a variableFix JSDoc for Router constructorexamples: fix typo in multi-router examplebuild: update example dependenciesbuild: Node.js@8.12build: should@13.2.3build: Node.js@8.11build: Node.js@6.14build: Node.js@4.9Depfu 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