[niheaven]

Description

Drop the v prefix from the release title.

Motivation and Context

name: Version ${{ github.ref_name }} used the tag name verbatim, so a v0.6.0 tag produced Version v0.6.0. Every release so far is titled without the prefix (Version 0.5.3).

The version is now derived in the build step and passed through GITHUB_ENV, since workflow expressions have no way to strip a prefix.

How Has This Been Tested?

$tag -replace '^v', '' checked against v0.6.0, v1.2.3-rc1, and an unprefixed 0.5.3.

Checklist:

• I have read the Contributing Guide.
• I have ensured that I am targeting the develop branch.
• I have updated the documentation accordingly.
• I have updated the tests accordingly.
• I have added an entry in the CHANGELOG.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 3bbd70e4-1cde-4a55-994b-2b4ae2584f9e

📥 Commits

Reviewing files that changed from the base of the PR and between d997caa and 3769837.

📒 Files selected for processing (1)

• .github/workflows/release.yml

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 4 remain after this review.

---

Summary by CodeRabbit

• Chores
  • Release titles now display version numbers without the leading “v”—for example, “Version 0.6.0” instead of “v0.6.0.” The version number remains unchanged; only its presentation in the release title differs. This change does not affect the software version or any product functionality. Release titles use this format for future releases.

Walkthrough

The release workflow sets the release name to Version plus the tag without its leading v. The changelog records this release-title change.

Changes

Release naming

Layer / File(s)	Summary
Set and document release name .github/workflows/release.yml, CHANGELOG.md	The workflow sets the release name to Version plus the tag without its leading v, then uses that name for the GitHub Release. The changelog records the change.

Priority: ⬇️ Low

Merge Risk: ⚪ Minimal · up to 37698

Supported releases receive the intended title, such as Version 0.6.0; no merge-blocking risk remains.

Architecture Summary

Architecture risk: 🔵 Low · up to 37698

The change affects 1 system.

Changed systems: CHANGELOG.md

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

• observed — CHANGELOG.md (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

• observed — Modified behavior in CHANGELOG.md: Adds the Unreleased heading and a Continuous Integration entry documenting the release-title prefix change, with a link to issue #6761.
• observed — Modified behavior in .github/workflows/release.yml: The workflow sets RELEASE_NAME to Version plus the tag with a leading v removed.
• observed — Modified behavior in .github/workflows/release.yml: The release action now uses RELEASE_NAME instead of constructing its name directly from the full tag.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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 clearly and concisely describes the main change: removing the v prefix from release titles.
Description check	✅ Passed	The description directly explains the release-title change, its motivation, implementation, testing, and changelog update.

---

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

[coderabbitai]

Actionable comments posted: 1

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: f026f74c-75d1-472e-b18c-4eb15e8e91ff

📥 Commits

Reviewing files that changed from the base of the PR and between 3769837 and d997caa.

📒 Files selected for processing (1)

• .github/workflows/release.yml

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 4 remain after this review.