-
-
Notifications
You must be signed in to change notification settings - Fork 17.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 4.14 #3006
Merged
Merged
Release 4.14 #3006
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
d5c9870
to
e550269
Compare
c9531ac
to
98224d2
Compare
FYI everyone + @expressjs/express-tc, 4.14 should have been complete tonight for a release tomorrow, but is currently delayed pending the resolution of a concern. |
As per the Express TC meeting on 6/15, this Express 4.14 release will be released today, 6/16! |
petems
added a commit
to petems/gscan
that referenced
this pull request
Aug 31, 2016
* https://nodesecurity.io/advisories/106 * older express depended on older accepts which required vulnerable negotiator * See PRs for context * jshttp/negotiator@26a05ec * expressjs/express#3006
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.
This is a tracking issue for release 4.14.
Please keep feature requests in their own issues
If you want to make a comment on a particular change, please make the comment in the "Files changed" tab so comments are not lost during a rebase.
List of changes for release:
res.location
/res.redirect
if not already encodedres.redirect
unpredictable sometimes with Unicode and even ANSI/ASCII #2897 The header content contains invalid characters TypeError: The header content contains invalid characters at ServerResponse. #3003res.json
/res.jsonp
performance in Node.js < 6 OptimizeJSON.stringify
performance in V8. #2900res.header
BugFixed: prevent toLowerCase crash the App. #2993===
instead of==
except when testing fornull
orundefined
. #2722accepts
module to 1.3.3 which brings in lots ofnegotiator
improvementscontent-type
module to 1.0.2cookie
module to 0.3.1 which brings newsameSite
optionfinalhandler
module to 0.5.0 which bringserr.headers
supportproxy-addr
module to 1.1.2qs
module to 6.2.0 which brings theencode
option toquery
middlewarerange-parser
module to 1.2.0 which brings options likecombine
send
module to 0.14.1 which bringsRange
& redirect fixes and new optionsserve-static
module to 1.11.1 which bringsRange
& redirect fixes and new optionstype-is
module to 1.6.13vary
module to 1.1.0 which brings field name validationTesting this release
If you want to try out this release, you can install it with the following commands:
Owners/collaborators: please do not merge this PR :)