ci(npm-publish): refresh README ecosystem footer + fix pnpm-11 version bump#157
Conversation
Fetch docs-kit's standalone README updater from the private repo and run\nit during the version bump (after pnpm version, before the commit), folding\nREADME.md into the signed version-bump commit. Best-effort: a failed fetch\nor roster blip only warns.\n\nCo-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 20 minutes and 49 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the 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 credits. 🚦 How do rate 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 see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
Comment |
|
❌ Release workflow failed. Please check the workflow logs |
What
NEW_VERSION=$(pnpm version …)by parsing stdout — pnpm 11 prints multi-line text, so the captured version is garbage. Switched to the safe pattern:pnpm version --no-git-tag-versionthen read the version vianode -p.pnpm version, before the commit) — same as the rest of the fleet.No new dependency: the updater is
curled raw from the private docs-kit repo and run withnode. Best-effort — a failed fetch only warns, never fails the release.🤖 Generated with Claude Code