Serialize Package Release runs with a per-ref concurrency group

[thedavidmeister]

Today's 11-merge train raced eleven Package Release runs; three ran within the same minute, all attempting the gate/publish sequence concurrently (one published 0.1.1, the others failed messily). rain.solmem's workflow already carries the fix — a per-ref concurrency group with cancel-in-progress: false so a mid-publish run is never killed and pending runs are superseded. This copies that stanza verbatim (comment included) into this repo's wrapper. Flagged by the issue #24 producer as a solmem-parity gap.

QA

• Discriminating tests: n/a - CI workflow config only; no repo behavior. YAML validated by push (workflow parses; run appears queued for this branch's push event on main-only trigger = no run, as expected).
• Mutations applied: n/a - no code changed.
• Oracle: rain.solmem .github/workflows/package-release.yaml (verbatim stanza, green release history since 2026-08-18).
• Category check: serialize release runs per ref without cancelling mid-publish; covered exactly.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 59 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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 within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 63eea269-5561-44f6-a010-08d40cfd7650

📥 Commits

Reviewing files that changed from the base of the PR and between b2b2269 and a5c2de4.

📒 Files selected for processing (1)

• .github/workflows/package-release.yaml

---

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