ci: fix Publish workflow npm upgrade (Corepack)#23
Merged
Conversation
Global npm install -g failed on Node 22.22.x (MODULE_NOT_FOUND: promise-retry in @npmcli/arborist). Use corepack prepare instead of upgrading through the broken bundled npm. Drop check-latest on setup-node to match integration tests and avoid bleeding-edge toolchains. Made-with: Cursor
proxymesh
approved these changes
Apr 6, 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.
Fixes failed
Upgrade npm for trusted publishing (OIDC)step:npm install -g npmerrored withCannot find module 'promise-retry'on the bundled npm (Node 22.22.x on ubuntu-latest).>=11.5.1viacorepack enableandcorepack prepare npm@11.5.1 --activateinstead of global npm self-upgrade.check-latest: trueon setup-node so publish matches proxy integration tests and avoids pulling the newest 22.x patch by default.After merge, re-run the failed Publish workflow or trigger
workflow_dispatchto verify.Made with Cursor