chore(ci): force tag creation in release config for draft releases

[SoulPancake]

…ases

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 configuration settings to enhance release management processes.

[coderabbitai]

Walkthrough

The PR adds a single configuration setting to release-please-config.json, enabling the force-tag-creation option at the top level of the release-please configuration. This setting controls whether tags are created during the release workflow.

Changes

Release Configuration Update

Layer / File(s)	Summary
Force tag creation configuration setting release-please-config.json	The force-tag-creation configuration key is set to true, enabling forced tag creation in the release-please workflow.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• openfga/js-sdk#377: Modifies release-please-config.json release configuration fields.
• openfga/js-sdk#393: Updates release-please-config.json to add new release-please settings including bootstrap-sha.

Suggested reviewers

• rhamzeh

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
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.
Title check	✅ Passed	The title directly and clearly describes the main change: adding force tag creation to the release configuration.

_{✏️ 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 chore/force-tag-creation-for-draft

---

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

[Copilot]

Pull request overview

Adds force-tag-creation: true to the release-please configuration so that git tags are created even when releases are published as drafts.

Changes:

• Enable force-tag-creation in release-please-config.json to ensure tags are produced for draft releases.

---

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

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.74%. Comparing base (fd8b8f4) to head (5cb19b6).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #422   +/-   ##
=======================================
  Coverage   85.74%   85.74%           
=======================================
  Files          25       25           
  Lines        1305     1305           
  Branches      265      265           
=======================================
  Hits         1119     1119           
  Misses        108      108           
  Partials       78       78           

☔ 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.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.