docs(release-skill): document the new-npm-package publish gotcha

[shumkov]

What was done

Adds a section to the project release skill capturing a release-process gotcha hit while cutting 4.1.0-beta.2.

The gotcha: release.yml's Release NPM packages job publishes via npm trusted-publishers OIDC, which can only publish to packages that already exist on npm — it can't bootstrap a brand-new @dashevo/* package. So the first release after someone adds a new npm package fails on that package with exit code 1 / registry 404, even though --access public and --tolerate-republish are already set (they are not the fix).

This bit @dashevo/document-history-contract (added in #4171) on both beta.1 and beta.2.

The doc covers:

• Symptom recognition (workspace exit 1, npm view … E404).
• The one-time fix: token-authenticated npm publish --access public --tag <major.minor-suffix> --otp=… at the released version, then gh run rerun … --failed so --tolerate-republish skips everything and the run goes green.
• The CDN negative-cache read-404 caveat (confirm via the PUT 200 line in ~/.npm/_logs).
• Prevention: first-publish new packages before the release that ships them.

Docs-only.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@shumkov, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 21 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: a41ba868-bda4-4249-bd1b-d53eb26f1d61

📥 Commits

Reviewing files that changed from the base of the PR and between ae554fd and 8622d64.

📒 Files selected for processing (1)

• .claude/skills/release/SKILL.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/release-skill-new-package-publish

---

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.}

[thepastaclaw]

🕓 Ready for review — 31 ahead in queue (commit 8622d64)
Queue position: 32/32 · 2 reviews active
ETA: start ~23:30 UTC · complete ~23:51 UTC (median 21m across 30 recent reviews; 2 slots)
Queued 3m ago · Last checked: 2026-07-23 18:10 UTC