Repository navigation
ci(npm): run the package check and releases on Node 26 - #143
Merged
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
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.
What
Moves the
npm-packageCI job and the publish job from Node 22 to Node 26, the runtime the project moved to. npm stays pinned at 11.21.1 in the publish job. The comment that justified the pin by "Node 22 ships npm 10" now says the pin keeps a Node update from changing npm.crossecute/sdk#12 makes the same move for the SDK.
Checked
The
npm-packagejob on this PR runscheck-consumer.shon Node 26.