ci(release): drop the "Release " prefix from release names

[LMLiam]

Summary

GitHub Releases are currently titled Release v0.1.X. This drops the Release prefix so a release is titled after its tag (e.g. v0.1.22).

Change

.github/workflows/release-and-publish.yml:

-          name: Release ${{ inputs.tag_name }}
+          name: ${{ inputs.tag_name }}

Notes

• The 16 existing releases (v0.1.5–v0.1.21, 0.1.4) have already been renamed to drop the prefix.
• Per the repo's release model, this PR needs a baseVersion bump in gradle.properties to actually cut a release on merge (currently 0.1.21, which is already tagged — see fix(release): handle existing tag when the version is not bumped #28/fix(release): correct step-output casing in the verify-version workflow #30).

Summary by CodeRabbit

• Chores
  • Updated automated GitHub release naming to use tag names directly without additional prefixes.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 5b415a46-7885-40ee-a417-c47feb08e103

📥 Commits

Reviewing files that changed from the base of the PR and between fdc0ff3 and 9bbf2f5.

📒 Files selected for processing (1)

• .github/workflows/release-and-publish.yml

---

📝 Walkthrough

Walkthrough

This PR removes the "Release " prefix from the GitHub Release name field in the release-and-publish workflow. The release name now uses only the provided tag_name, simplifying release naming and reducing redundancy.

Changes

Release Workflow

Layer / File(s)	Summary
Release name field update .github/workflows/release-and-publish.yml	The GitHub Release name field is changed to use ${{ inputs.tag_name }} directly instead of prefixing it with Release .

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minutes

Poem

A prefix gone, so clean and bright, ✨
Release names now shine so right!
Tag names bare, no "Release" shroud,
Simplicity speaks clear and loud! 🐰

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: removing the 'Release ' prefix from release names in the CI workflow.
Description check	✅ Passed	The description covers summary and changes but omits most template sections (modules affected, versioning, testing, checklist) that don't apply to this CI-only change.
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.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}