chore(release): fix duplicated version prefix in release title#8359
Merged
Conversation
communique already includes the version in its title output (e.g., "v2026.2.21: Bug fix roundup..."), but the release workflow also prepends "$VERSION: ", resulting in doubled titles like "v2026.2.21: v2026.2.21: Bug fix roundup...". Strip any existing version prefix from communique's title before prepending it. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
Greptile SummaryFixes the double version prefix bug in GitHub release titles by stripping any existing
Confidence Score: 5/5
Important Files Changed
Last reviewed commit: a261d28 |
Hyperfine Performance
|
| Command | Mean [ms] | Min [ms] | Max [ms] | Relative |
|---|---|---|---|---|
mise-2026.2.21 x -- echo |
26.2 ± 0.8 | 24.8 | 35.2 | 1.00 |
mise x -- echo |
26.3 ± 1.7 | 24.6 | 59.2 | 1.00 ± 0.07 |
mise env
| Command | Mean [ms] | Min [ms] | Max [ms] | Relative |
|---|---|---|---|---|
mise-2026.2.21 env |
25.4 ± 0.6 | 24.2 | 27.6 | 1.00 |
mise env |
25.7 ± 1.5 | 24.2 | 56.4 | 1.01 ± 0.06 |
mise hook-env
| Command | Mean [ms] | Min [ms] | Max [ms] | Relative |
|---|---|---|---|---|
mise-2026.2.21 hook-env |
26.0 ± 0.6 | 24.7 | 28.5 | 1.00 |
mise hook-env |
26.2 ± 0.7 | 24.9 | 30.4 | 1.01 ± 0.03 |
mise ls
| Command | Mean [ms] | Min [ms] | Max [ms] | Relative |
|---|---|---|---|---|
mise-2026.2.21 ls |
24.3 ± 1.0 | 23.2 | 42.1 | 1.00 |
mise ls |
24.4 ± 0.6 | 23.1 | 28.4 | 1.00 ± 0.05 |
xtasks/test/perf
| Command | mise-2026.2.21 | mise | Variance |
|---|---|---|---|
| install (cached) | 163ms | 159ms | +2% |
| ls (cached) | 92ms | 91ms | +1% |
| bin-paths (cached) | 96ms | 94ms | +2% |
| task-ls (cached) | 859ms | 846ms | +1% |
mise-en-dev
added a commit
that referenced
this pull request
Feb 27, 2026
### 🚀 Features - add `--outdated` flag to `mise plugins ls` by @jdx in [#8360](#8360) ### 🐛 Bug Fixes - **(github)** resolve rename_exe search dir for archives with bin/ subdirectory by @jdx in [#8358](#8358) - **(install)** skip tools=true env directives during backend installation by @jdx in [#8356](#8356) - **(ruby)** resolve correct Windows checksums in lockfile by @jdx in [#8357](#8357) ### 📦 Registry - switch terradozer backend to github fork by @chenrui333 in [#8365](#8365) ### Chore - **(release)** fix duplicated version prefix in release title by @jdx in [#8359](#8359) ### New Contributors - @chenrui333 made their first contribution in [#8365](#8365) ## 📦 Aqua Registry Updates #### New Packages (1) - [`huseyinbabal/taws`](https://github.com/huseyinbabal/taws) #### Updated Packages (2) - [`block/goose`](https://github.com/block/goose) - [`pre-commit/pre-commit`](https://github.com/pre-commit/pre-commit)
risu729
pushed a commit
to risu729/mise
that referenced
this pull request
Feb 27, 2026
) ## Summary - Release titles were getting doubled version prefixes like `v2026.2.21: v2026.2.21: Bug fix roundup...` - The `communique` tool already includes the version in its generated title, but the workflow also prepended `$VERSION:` on top of it - Now strips any existing `$VERSION: ` prefix from communique's output before prepending, so the title is always clean ## Test plan - [ ] Next release should have a clean title like `v2026.x.x: Description here` 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > Low risk: a small GitHub Actions workflow tweak that only affects how the release title string is constructed during tag releases. > > **Overview** > Fixes the release workflow’s generated `RELEASE_TITLE` to avoid double-prepending the version when `communique` already includes `$VERSION:` in its first-line title. > > The workflow now parses the first line from `/tmp/release-notes.txt`, strips markdown and any leading `$VERSION: `, then prepends `$VERSION:` exactly once before creating the GitHub release. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit a261d28. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY --> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
risu729
pushed a commit
to risu729/mise
that referenced
this pull request
Feb 27, 2026
### 🚀 Features - add `--outdated` flag to `mise plugins ls` by @jdx in [jdx#8360](jdx#8360) ### 🐛 Bug Fixes - **(github)** resolve rename_exe search dir for archives with bin/ subdirectory by @jdx in [jdx#8358](jdx#8358) - **(install)** skip tools=true env directives during backend installation by @jdx in [jdx#8356](jdx#8356) - **(ruby)** resolve correct Windows checksums in lockfile by @jdx in [jdx#8357](jdx#8357) ### 📦 Registry - switch terradozer backend to github fork by @chenrui333 in [jdx#8365](jdx#8365) ### Chore - **(release)** fix duplicated version prefix in release title by @jdx in [jdx#8359](jdx#8359) ### New Contributors - @chenrui333 made their first contribution in [jdx#8365](jdx#8365) ## 📦 Aqua Registry Updates #### New Packages (1) - [`huseyinbabal/taws`](https://github.com/huseyinbabal/taws) #### Updated Packages (2) - [`block/goose`](https://github.com/block/goose) - [`pre-commit/pre-commit`](https://github.com/pre-commit/pre-commit)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
v2026.2.21: v2026.2.21: Bug fix roundup...communiquetool already includes the version in its generated title, but the workflow also prepended$VERSION:on top of it$VERSION:prefix from communique's output before prepending, so the title is always cleanTest plan
v2026.x.x: Description here🤖 Generated with Claude Code
Note
Low Risk
Low risk: a small GitHub Actions workflow tweak that only affects how the release title string is constructed during tag releases.
Overview
Fixes the release workflow’s generated
RELEASE_TITLEto avoid double-prepending the version whencommuniquealready includes$VERSION:in its first-line title.The workflow now parses the first line from
/tmp/release-notes.txt, strips markdown and any leading$VERSION:, then prepends$VERSION:exactly once before creating the GitHub release.Written by Cursor Bugbot for commit a261d28. This will update automatically on new commits. Configure here.