Skip to content

ci(npm-publish): refresh README ecosystem footer + fix pnpm-11 version bump#157

Merged
jaysin586 merged 1 commit into
mainfrom
ci/readme-ecosystem-footer
Jun 25, 2026
Merged

ci(npm-publish): refresh README ecosystem footer + fix pnpm-11 version bump#157
jaysin586 merged 1 commit into
mainfrom
ci/readme-ecosystem-footer

Conversation

@jaysin586

@jaysin586 jaysin586 commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

What

  1. Fixes the pnpm-11 version-bump bug. This repo derived 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-version then read the version via node -p.
  2. Adds the README ecosystem-footer refresh (after 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 with node. Best-effort — a failed fetch only warns, never fails the release.

🤖 Generated with Claude Code

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>
@coderabbitai

coderabbitai Bot commented Jun 25, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@jaysin586, we couldn't start this review because you've reached your PR review rate limit.

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 @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 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 configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: eceda9a7-ecb5-4d7d-9510-3b603eeafeca

📥 Commits

Reviewing files that changed from the base of the PR and between edbb620 and da0faa6.

📒 Files selected for processing (1)
  • .github/workflows/npm-publish.yml

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

@jaysin586 jaysin586 changed the title ci(npm-publish): refresh README ecosystem footer on release ci(npm-publish): refresh README ecosystem footer + fix pnpm-11 version bump Jun 25, 2026
@jaysin586 jaysin586 merged commit d9de7de into main Jun 25, 2026
2 of 3 checks passed
@jaysin586

Copy link
Copy Markdown
Contributor Author

❌ Release workflow failed. Please check the workflow logs

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