fix(ext/node): update node version in process object #27044
Merged
Conversation
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
Signed-off-by: Sebastien Guillemot <[email protected]>
|
|
dsherret
changed the title
|
Updated the headers/node.lib files for v22 ref #26749 |
|
@nathanwhit Do you remember how you created node.lib.tar.gz in #26749 ? |
kt3k
changed the title
|
Landing for now as the contents of header/lib files shouldn't be very important in those test cases |
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.
The process polyfill hardcodes the latest stable node version. On October 29th, nodejs announced that v22.11.0 is the new
stableversion (with v20 moving into maintenance LTS)To reflect this, I've bumped the hardcoded version in the
processpolyfillFor reference, you can see the latest time this hardcoded value was updated here: #22709