fix: add npm upgrade step for staged publishing#83
Merged
Conversation
…orkflow Node latest (v24) ships with npm 11.13.0 which is too old for staged publishing (>= 11.15.0). The explicit npm upgrade step is required.
|
The changes in this PR will be included in the next version bump. Bump files in this PRClick here if you want to add another bump file to this PR This comment is maintained by bumpy. |
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
Node latest (v24) ships with npm 11.13.0, which is too old for
npm stage(introduced in 11.15.0). Add explicitnpm install -g npm@lateststep to:This should unblock publishing of 1.9.2 (currently unpublished due to the npm version issue).
Test plan
bumpy ci release→ detects 1.9.2 unpublished → staged publish succeeds with npm >= 11.15.0