fix(ci): --force on npm self-upgrade — unblock v0.3.1 publish#760
Merged
kokevidaurre merged 1 commit intomainfrom Apr 24, 2026
Merged
fix(ci): --force on npm self-upgrade — unblock v0.3.1 publish#760kokevidaurre merged 1 commit intomainfrom
kokevidaurre merged 1 commit intomainfrom
Conversation
\`npm install -g npm@latest\` fails mid-upgrade with \`Cannot find module 'promise-retry'\` because the new npm package is partially installed and can't resolve its own internal arborist modules. Documented npm bug. Adding --force makes the install bypass the broken intermediate state. Affects both release.yml (tag-triggered) and publish.yml (manual). This is what blocked the v0.3.1 publish to @latest. Co-Authored-By: Claude <noreply@anthropic.com>
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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 v0.3.1 release ran successfully through CI + security but failed at npm publish because the npm self-upgrade step crashed:
```
npm install -g npm@latest
→ Cannot find module 'promise-retry'
→ ##[error]Process completed with exit code 1.
```
Documented npm bug: when
npm@latestself-upgrades fromnpm@10.x, the partially-installed new package can't resolve its own arborist internals mid-install. `--force` bypasses the broken intermediate state.Changes
release.yml: `npm install -g npm@latest` → `npm install -g npm@latest --force`publish.yml: same fix (also affected)Why this blocks the release
Post-merge steps
```bash
git checkout main && git pull
git tag -d v0.3.1
git push origin :refs/tags/v0.3.1
git tag v0.3.1
git push origin v0.3.1 # re-triggers release.yml with the fix
```
Test plan