ci: recover npm release publishing

[flyingrobots]

Summary

• add manual Release workflow dispatch for an existing tag
• publish npm from Node 24 with bundled npm 11 instead of self-upgrading npm 10
• report registry publish status from explicit job outputs and update existing GitHub Release notes
• document the idempotent recovery path in the release runbook

Context

The v17.0.0 tag published JSR and created the GitHub Release, but npm did not publish. The npm publish job failed before running npm publish because npm i -g npm@latest crashed on the GitHub Node 22 image with MODULE_NOT_FOUND: promise-retry.

After this merges, run the Release workflow manually with tag=v17.0.0. JSR should skip as already published; npm should publish; the existing GitHub Release notes should be updated with the actual registry status.

Validation

• npx vitest run test/unit/scripts/release-policy-shape.test.ts
• npx prettier --check .github/workflows/release.yml docs/method/release.md
• Ruby YAML parse of .github/workflows/release.yml
• npm run lint:md -- docs/method/release.md
• pre-push IRONCLAD M9: 445 files / 6796 tests

[coderabbitai]

Warning

Rate limit exceeded

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

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: 222f534d-7e15-42e9-bda7-532e22f044f6

📥 Commits

Reviewing files that changed from the base of the PR and between 04545ef and 2513e0e.

📒 Files selected for processing (2)

• .github/workflows/release.yml
• docs/method/release.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/v17.0.0-npm-publish-recovery

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[github-actions]

Release Preflight

• package version: 17.0.0
• prerelease: false
• npm dist-tag on release: latest
• npm pack dry-run: passed
• jsr publish dry-run: passed

If you tag this commit as v17.0.0, release workflow will publish.