Repository navigation
Use Node 24 for trusted publishing - #8
Merged
Merged
Conversation
…npm in place **Summary** - The publish job now sets up Node 24 and checks that its npm is 11.5.1 or newer, instead of running `npm install -g npm@^11.5.1`. **Why** - On the runner the in-place upgrade failed with `EACCES` creating `/usr/local/share/man/man5`, because the system Node is not writable, so the `0.2.0` publish stopped before it started. **Details** - `actions/setup-node` installs Node 24 into the runner's tool cache, whose npm supports trusted publishing, and a new step fails with a clear message if the version is ever too old.
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.
Summary
npm install -g npm@^11.5.1failed on the runner withEACCES(the system Node directory is not writable), so the0.2.0publish never ran. The job now uses Node 24 fromactions/setup-node, whose bundled npm supports trusted publishing, and a new step fails clearly if npm is older than 11.5.1.Test plan
bunx prettier --check .githubv0.2.0and approvenpm-publish