Skip to content

fix: remove npm self-upgrade step crashing Release workflow#28

Merged
mynameistito merged 1 commit intomainfrom
fix/release-npm-upgrade-failure
Apr 16, 2026
Merged

fix: remove npm self-upgrade step crashing Release workflow#28
mynameistito merged 1 commit intomainfrom
fix/release-npm-upgrade-failure

Conversation

@mynameistito
Copy link
Copy Markdown
Owner

@mynameistito mynameistito commented Apr 16, 2026

Problem

The Release workflow fails on the "Upgrade npm for OIDC support" step:

npm error code MODULE_NOT_FOUND
npm error Cannot find module 'promise-retry'

The GitHub Actions runner's cached npm 10.9.7 has an incomplete node_modules install (missing promise-retry), so npm install -g npm@latest crashes because npm can't load its own dependencies to run.

Fix

Remove the step entirely. npm 10.9.7 already supports OIDC/provenance publishing (that feature was added in npm 9.5.0), so the upgrade was unnecessary and just added fragility.

Test plan

  • Merge and verify Release workflow passes the formerly-failing step

Summary by cubic

Removed the npm install -g npm@latest step from the Release workflow to stop crashes caused by the runner’s corrupt cached npm (missing promise-retry). The existing npm 10.9.7 already supports OIDC/provenance, so no upgrade is needed.

Written for commit 6dae066. Summary will update on new commits.

Note

Remove npm self-upgrade step crashing the Release workflow

The npm install -g npm@latest step in release.yml was causing the Release workflow to crash. Removing it means the workflow now uses whichever npm version the runner or setup-node provides.

Macroscope summarized 6dae066.

The 'npm install -g npm@latest' step fails with MODULE_NOT_FOUND: promise-retry
because the GitHub Actions runner's cached npm 10.9.7 has an incomplete install.
npm 10.9.7 already supports OIDC provenance (added in npm 9.5), so the upgrade is unnecessary.
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 16, 2026

Warning

Rate limit exceeded

@mynameistito has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 44 minutes and 44 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 44 minutes and 44 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: d89a4fd6-761d-44c8-8da3-46efddf23f28

📥 Commits

Reviewing files that changed from the base of the PR and between f8ab883 and 6dae066.

📒 Files selected for processing (1)
  • .github/workflows/release.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/release-npm-upgrade-failure

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@sonarqubecloud
Copy link
Copy Markdown

Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

@mynameistito mynameistito merged commit b865870 into main Apr 16, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant