chore: add pull request title pattern for releases

[SoulPancake]

Description

What problem is being solved?

How is it being solved?

What changes are made to solve it?

References

Review Checklist

• I have clicked on "allow edits by maintainers".
• I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
• The correct base branch is being used, if not main
• I have added tests to validate that the change in functionality is working as expected

Summary by CodeRabbit

• Chores
  • Updated release automation configuration to standardize pull request title formatting.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 21282751-d051-4def-8575-399daf432937

📥 Commits

Reviewing files that changed from the base of the PR and between 9d39016 and 33bd943.

📒 Files selected for processing (1)

• release-please-config.json

---

Walkthrough

A pull-request-title-pattern configuration field was added to release-please-config.json, standardizing the generated pull request title format to release: v${version}.

Changes

Cohort / File(s)	Summary
Configuration release-please-config.json	Added pull-request-title-pattern field to standardize pull request title format as release: v${version}.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

• sergiught
• rhamzeh

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 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 main change: adding a pull request title pattern configuration for releases in the release-please-config.json file.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/use-pr-title-pattern

---

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

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.85%. Comparing base (9d39016) to head (33bd943).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #272   +/-   ##
=======================================
  Coverage   69.85%   69.85%           
=======================================
  Files         140      140           
  Lines       10748    10748           
=======================================
  Hits         7508     7508           
  Misses       3240     3240           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Copilot]

Pull request overview

Adds a release-please configuration tweak so the automatically generated release PRs use a consistent, conventional-commit-style title that includes the version.

Changes:

• Configure release-please to format release PR titles as release: v${version}.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.