fix: switch publish workflow to Node 24, drop broken npm upgrade step#62
Merged
fix: switch publish workflow to Node 24, drop broken npm upgrade step#62
Conversation
Node 24 bundles npm 11+ with OIDC trusted publishing support built-in. The npm install -g npm@latest step was failing on GitHub Actions runners due to a broken promise-retry module in the Node 22.22.2 toolcache.
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
1 participant
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.
Summary
actions/setup-nodefrom Node 22 to Node 24npm install -g npm@lateststep entirelyNode 24 bundles npm 11+ which has OIDC trusted publishing support built-in. The npm upgrade step was failing on every publish attempt due to a broken
promise-retrymodule in the GitHub Actions Node 22.22.2 toolcache — this has blocked the 0.8.0 release.