Merged
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
2023-10-10, Version 18.18.1 'Hydrogen' (LTS), @richardlau
Notable Changes
This release addresses some regressions that appeared in Node.js 18.18.0:
The libuv 1.45.0 and 1.46.0 updates that were released in Node.js 18.18.0 have been temporarily reverted.
Commits
3e3a75cc46] - Revert "build: sync libuv header change" (Richard Lau) #5003614ece2c479] - Revert "deps: upgrade to libuv 1.45.0" (Richard Lau) #50036022352acbe] - Revert "deps: upgrade to libuv 1.46.0" (Richard Lau) #50036d9f138189c] - Revert "deps: add missing thread-common.c in uv.gyp" (Richard Lau) #500367a3e1ffbb8] - fs: make sure to write entire buffer (Robert Nagy) #4921104cba95a67] - test: addtmpdir.resolve()(Livia Medeiros) #49079cc @nodejs/lts
Note that this is not a "full" Node.js 18 release -- it is a "quick" release to fix the regressions noted above that were introduced in Node.js 18.18.0. I will not have time to do a full Node.js release this month, so any requests for additions to this release will likely be denied unless a very strong case can be made.