chore: force tag creation in release config for draft 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 ensure consistent tag creation during the release process.

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 1d981ac8-c737-40e7-8795-785729a4ec8d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Walkthrough

The PR adds a single configuration flag to release-please-config.json, enabling force-tag-creation: true at the root level. This setting instructs release-please to create release tags unconditionally, overriding default tag condition logic.

Changes

Release-Please Configuration

Layer / File(s)	Summary
Force tag creation setting release-please-config.json	Enables force-tag-creation: true in the release-please root configuration to ensure release tags are created even when default conditions would prevent it.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• openfga/dotnet-sdk#200: Both PRs modify release-please-config.json's release-please settings to control release behavior.
• openfga/dotnet-sdk#210: Both PRs modify release-please-config.json to adjust release-please tag and release behavior.

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.
Title check	✅ Passed	The title accurately describes the main change: enabling force-tag-creation in the release-please configuration for draft releases.
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.

_{✏️ 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/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

This PR updates the release-please configuration for the .NET SDK repository so draft releases force tag creation during release automation.

Changes:

• Enables force-tag-creation in release-please-config.json.

---

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