Closed
Conversation
Author
|
Closed in favor of #63. |
This file contains hidden or 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
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?
✳️ express (4.17.3 → 4.18.1) · Repo · Changelog
Release Notes
4.18.1
4.18.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 59 commits:
4.18.1build: Node.js@16.15Fix hanging on large stack of sync routesbench: remove unused parameterbuild: ejs@3.1.7build: supertest@6.2.3build: mocha@9.2.24.18.0bench: print latency and vary connectionsbuild: support Node.js 18.xbuild: use 64-bit Node.js in AppVeyorbuild: support Node.js 17.xtests: mark stack overflow as long runningFix handling very large stacks of sync middlewaredeps: cookie@0.5.0examples: add missing html label associationsexamples: use http-errors to create errorsdocs: remove Node Security Project from security policydocs: fix typo in casing of HTTPtests: fix typo in descriptionbuild: use supertest@3.4.2 for Node.js 6.xdeps: on-finished@2.4.1deps: statuses@2.0.1deps: qs@6.10.3deps: body-parser@1.20.0Use http-errors for res.format errorFix behavior of null/undefined as "maxAge" in res.cookiedeps: depd@2.0.0Invoke default with same arguments as types in res.formatexamples: use updated res.download in exampleAllow options without filename in res.downloaddeps: finalhandler@1.2.0deps: serve-static@1.15.0deps: send@0.18.0Add "root" option to res.downloadDeprecate string and non-integer arguments to res.statusIgnore Object.prototype values in settings through app.set/app.getSupport proper 205 responses using res.sendbuild: support Node.js 16.xbuild: support Node.js 15.xlint: remove unnecessary continue statement in loopdocs: fix incomplete JSDoc commentexamples: fixup htmllint: remove deprecated String.prototype.substrbuild: mocha@9.2.1tests: expand res.sendFile options testsdocs: add install size badgedocs: consolidate contributing in readmedocs: switch badges to badgendocs: update link to github actions cidocs: fix typo in private api jsdoctests: fix position of res.sendfile(path, options) testtests: fix callback in res.download testtests: remove duplicate utilstests: remove usage of shouldtests: update res.append to verify separate header linestests: fix up app.locals teststests: fix req.acceptsLanguage teststests: fix req.acceptsEncodings tests👉 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:
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