fix(ci): remove custom title pattern, use release-please default#312
Conversation
The custom pattern "chore: release${component}" couldn't match old
merged PRs titled "chore: release main". The root package has an empty
component, producing "chore: release" which collided with old titles
where the action appended the branch name.
Removing the custom pattern lets release-please use its default title
format which avoids collisions with the old PR history.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Entire-Checkpoint: d18d1a271e2a
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
Summary
pull-request-title-pattern: "chore: release${component}"still can't match old merged PRs titled"chore: release main"— the root package has an empty component, producing"chore: release"which collides when release-please tries to parse old titles with" main"appended"chore(main): release <package> <version>"), which won't collide with the old PR historybootstrap-shafrom fix(ci): add bootstrap-sha to skip old unparseable release PRs #311, this should unblock release-pleaseTest plan
🤖 Generated with Claude Code