docs: Release-As must ride a top-level commit message, not a squash bullet#76
Conversation
…ullet PR #73 carried "Release-As: 0.9.0" inside the first bulleted sub-message of its two-commit squash body and release-please ignored it, computing 0.8.16 instead. Document the pitfall and the reliable vehicle (a single-commit micro-PR whose own message carries the footer) - which is exactly what this commit is: it pins the next release. Supersedes #75 (CodeRabbit's MD018 fix folded in; amending that PR would have required a force-push, and adding a second commit would have buried this footer in a squash bullet - the very bug documented). Release-As: 0.9.0 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 31 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?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 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. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
1 participant
Supersedes #75 with CodeRabbit's MD018 fix applied (no line starts with a bare
#NNreference). Opened as a fresh single-commit PR rather than pushing a second commit to #75, because a two-commit squash would bury theRelease-As: 0.9.0footer in a bulleted sub-message — exactly the pitfall this note documents.Once merged, release-please recomputes #74 as 0.9.0 (containing the two #73 fixes + this note).
Docs-only — auto-approve + trusted-author auto-merge should carry it in without manual action.
🤖 Generated with Claude Code