fix(ci): allow release branch scopes in PR title validation

[marythought]

Summary

• Adds release/v0\.\d+ regex pattern to the allowed scopes in the PR title validation workflow
• Fixes Validate PR title check failing on release-please PRs targeting release branches (e.g. chore(release/v0.13): release 0.13.1-SNAPSHOT #348, chore(release/v0.11): release 0.11.1-SNAPSHOT #315, chore(release/v0.10): release 0.10.1-SNAPSHOT #289)

Release-please uses the pattern chore(${branch}): release ${version} for PR titles, which produces scopes like release/v0.13 for release branch PRs. These scopes were not in the allowed list, causing CI to fail.

Test plan

• Verify this PR's own Validate PR title check passes
• Confirm chore(release/v0.13): release 0.13.1-SNAPSHOT #348 passes after this merges (or re-run its check)

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Enhanced pull request validation workflow to recognize and properly handle release automation processes.

[gemini-code-assist]

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

[coderabbitai]

📝 Walkthrough

Walkthrough

The GitHub Actions workflow configuration now recognizes release-automation pull requests by extending the Conventional Commits validator to accept commit scope patterns matching release/v0.\d+, enabling these PRs to pass semantic validation checks.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow Configuration .github/workflows/checks.yaml	Added new scope pattern release/v0\.\d+ to the Conventional Commits action's allowed scopes list with corresponding comment documentation for release-automation PRs.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A scope for releases, now recognized with glee,
v0.\d+ patterns flowing wild and free,
Release automation hops along the way,
Checks pass with joy throughout the day! 🎉

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title clearly and specifically describes the main change: allowing release branch scopes in PR title validation, which directly addresses the primary purpose of the changeset.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/release-branch-pr-title-scope

---

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 and usage tips.}

[github-actions]

X-Test Failure Report

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

X-Test Results

✅ java-main
✅ java-v0.13.0
✅ js-main
✅ js-v0.13.0
✅ go-main
✅ go-v0.13.0