fix(release): accept grouped release titles

[yordis]

• Grouped release pull requests must remain recognizable after their component versions move into the release body.
• The initial client release must be recoverable without skipping directly to a later version.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: d14c9c14-aa9f-40c6-987d-d937ace29730

📥 Commits

Reviewing files that changed from the base of the PR and between c9ba45b and 0cbdb70.

📒 Files selected for processing (1)

• release-please-config.json

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

Walkthrough

The release configuration changes grouped release pull request titles to the chore${scope}: release format by removing the component and version placeholders.

Changes

Release title format

Layer / File(s)	Summary
Grouped release title pattern release-please-config.json	The grouped release pull request title pattern omits ${component} ${version}.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 0cbdb

This localized configuration change updates release title handling for grouped and initial releases; no actionable merge-blocking risk remains beyond normal checks and review.

Poem

A rabbit reviewed the release sign,
“No extra parts—its shape is fine.”
Scope hops in, release stays clear,
Component and version disappear.
chore: neat and bright,
Ready for the merge tonight.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: support for grouped release titles.
Description check	✅ Passed	The description explains why grouped release titles must remain recognizable and how the initial client release must be recovered.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch yordis/fix-release-title-parsing

---

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