Skip to content

fix(ci): set release-please title pattern to use version instead of component#317

Merged
FSM1 merged 1 commit into
mainfrom
fix/release-please-title-pattern-v2
Mar 22, 2026
Merged

fix(ci): set release-please title pattern to use version instead of component#317
FSM1 merged 1 commit into
mainfrom
fix/release-please-title-pattern-v2

Conversation

@FSM1

@FSM1 FSM1 commented Mar 22, 2026

Copy link
Copy Markdown
Owner

Summary

  • The root cause of all the release-please failures: the default title pattern includes ${component}, but the root package has no component, producing titles like "chore: release main" that can't be parsed back
  • Sets pull-request-title-pattern: "chore: release v${version}" — unambiguous, doesn't depend on component resolution
  • PR chore: release v0.25.2 #315 renamed to "chore: release v0.25.2" to match the new pattern

Context

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

🤖 Generated with Claude Code

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

coderabbitai Bot commented Mar 22, 2026

Copy link
Copy Markdown

Warning

Rate limit exceeded

@FSM1 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 2 minutes and 15 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 03841b3d-6bb4-4fb4-807e-46f141d64cfc

📥 Commits

Reviewing files that changed from the base of the PR and between 1be3986 and 741dbfb.

📒 Files selected for processing (1)
  • release-please-config.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/release-please-title-pattern-v2

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

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

@FSM1 FSM1 merged commit 9cdea31 into main Mar 22, 2026
14 checks passed
@FSM1 FSM1 deleted the fix/release-please-title-pattern-v2 branch March 22, 2026 03:37
This was referenced Mar 22, 2026
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