fix(ci): set release-please title pattern to use version instead of component#317
Conversation
…on}'
The default title pattern includes ${component}, but the root package
has no component, producing 'chore: release main' which can't be
parsed back. Using 'chore: release v${version}' is unambiguous and
doesn't depend on component resolution.
Also renamed PR #315 from 'chore: release main' to 'chore: release
v0.25.2' so release-please can match it on the next run.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Entire-Checkpoint: 7339475e2a90
|
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
${component}, but the root package has no component, producing titles like"chore: release main"that can't be parsed backpull-request-title-pattern: "chore: release v${version}"— unambiguous, doesn't depend on component resolution"chore: release v0.25.2"to match the new patternContext
This has been a multi-PR saga (#307, #311, #312, #313) trying to fix release-please after the multi-package config was added. The root issue was always the title pattern —
${component}is empty for the root package.Test plan
v0.25.2tag and GitHub release from PR chore: release v0.25.2 #315🤖 Generated with Claude Code