ci: fix npm publish workflow#15
Merged
Merged
Conversation
The publish workflow upgraded npm via `npm install -g npm@latest` to obtain a version that supports trusted publishing. On the current ubuntu-latest runner this corrupts the bundled npm and fails with `Cannot find module 'promise-retry'`, blocking releases on every tag push. Bumping `setup-node` to Node 24 ships an npm new enough for trusted publishing out of the box, so the in-place upgrade step is dropped.
MickeyShnaiderman-RecoLabs
approved these changes
Apr 26, 2026
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
2 participants
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
The
Publish NPMworkflow has been failing at thenpm install -g npm@lateststep onubuntu-latestwith:This is a deterministic self-corruption bug in the bundled-npm → npm@latest in-place upgrade path on Node 22 — it left
@npmcli/arboristunable to resolvepromise-retryand blocked the v0.2.2 release (see run 24951082111).The original step exists only to obtain an npm version new enough for trusted publishing. Node 24 already ships with such an npm, so this PR:
actions/setup-nodetonode-version: '24'npm install -g npm@lateststep entirelyOnce merged, the publish workflow can be re-run against tag
v0.2.2to ship the release.Test plan
Publish NPMworkflow on tagv0.2.2and confirm the package is published to npm