Repository navigation
fix(release-finalize): title the GitHub Release with its bare tag - #25
Merged
Merged
Conversation
The app dropped the "Release " prefix in its in-repo finalize (aragon/app 30f00b903); the shared workflow still added it, so the prefix came back with the migration.
jjavieralv
approved these changes
Oct 29, 2026
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
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.
GitHub Releases created by the shared finalize were named `Release @aragon/app@1.42.0`; the Releases page already says they are releases and the prefix only truncates the tag in the sidebar. The app had dropped it in its in-repo finalize (aragon/app 30f00b903) and the prefix came back when the app moved onto this workflow. The title is now the tag itself, as `release-self.yml` already does. PR titles keep the `Release ` form.
🤖 Generated with Claude Code