Release proposal: v0.10.42 (Maintenance) #5138
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.
Security release, to go out ~ Tuesday, the 9th of February, 11pm UTC with releases across all active lines as per https://groups.google.com/d/msg/nodejs-sec/G8IA0G4uA88/So3Cw84YDwAJ.
Commits so far:
6dbcb188b0
] - build: enable xz compressed tarballs where possible (Rod Vagg) #4894b0a848c666
] - deps: upgrade openssl sources to 1.0.1r (Shigeki Ohtsu) joyent/node#25368eb4666b9dc
] - doc: clarify v0.10.41 openssl tls security impact (Rod Vagg) #415302bc6f3536
] - tools: backport tools/install.py for headers (Richard Lau) #4149Pending additions being worked on by the security team, I'll get everything else ready here and finish it off in our private repo. Still needs "Notable items" filled out for OpenSSL.
Commit still on
v0.10-staging
that we'll have to get to in a v0.10.43 soon after this release:9cae9b2290
] - domains: fix handling of uncaught exceptions (Julien Gilli) #3887Trying not to include non-security and non-build changes in this release to minimise impact to users (well, minimise their perceived impact at least).