fix(ci): set group-pull-request-title-pattern for rust-core release group

[goldmedal]

Problem

The merge of the rust-core release PR (#2467) did not create releases/tags and the crates.io publish never ran. Root cause is a known release-please bug (#2306):

The linked-versions plugin emits a grouped release PR titled chore(main): release wren-rust-core libraries (no version). Without a matching group-pull-request-title-pattern, release-please rejects it on merge —

✖ Bad pull request title: 'chore(main): release wren-rust-core libraries'

— so it creates no releases/tags, release_created stays false, and publish-wren-crates is skipped. The version bump itself worked: all three crates + the manifest are at 0.2.0 on main, just untagged/unpublished.

Fix

Add the matching pattern so the grouped PR is recognized both when generated and when parsed on merge:

"group-pull-request-title-pattern": "chore${scope}: release wren-rust-core libraries"

Effect after merge

On the next Release Please run, release-please re-detects the already-merged, still-untagged #2467, now parses its title successfully, and creates the wren-manifest-macro-v0.2.0 / wren-core-base-v0.2.0 / wren-semantic-core-v0.2.0 releases → release_created becomes true → publish-wren-crates runs and publishes 0.2.0 to crates.io (bottom-up, via Trusted Publishing).

No source or version changes — config only.

Summary by CodeRabbit

• Chores
  • Standardized the title format for grouped release pull requests.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 23fad9b0-d7ed-4956-b9aa-6691927ce544

📥 Commits

Reviewing files that changed from the base of the PR and between 3ea5676 and c82ab6f.

📒 Files selected for processing (1)

• release-please-config.json

---

Walkthrough

The release configuration adds a grouped pull request title pattern for Wren Rust Core library releases.

Changes

Release title configuration

Layer / File(s)	Summary
Grouped pull request title pattern release-please-config.json	Adds group-pull-request-title-pattern with the configured release title format.

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

Poem

I’m a rabbit with a tidy release queue,
Titles now bloom in a pattern true.
One hop, one name, one polished line—
Rust libraries ready to shine!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the release-please config change for the Rust core release group.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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 fix/release-please-group-title

---

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