Repository navigation
Move CI to Node 24 actions - #2
Merged
Merged
Conversation
checkout and setup-node v4 run on the deprecated Node 20 runtime. The registry check after publish also gave up after 30 seconds, while npm can take a few minutes to show a new version. Bump to 1.0.2.
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.
checkout and setup-node v4 run on the deprecated Node 20 runtime, which every job warns about. Moves both workflows to v6. Also lets the post-publish registry check wait up to three minutes, since npm can take that long to show a new version. Bumps to 1.0.2 so the tag publish can run end to end with the new NPM_TOKEN.