Repository navigation
feat(github): Add releaseName option to title releases with the prefixed tag - #933
Closed
sentry-junior[bot] wants to merge 1 commit into
Closed
sentry-junior[bot] wants to merge 1 commit into
sentry-junior[bot] wants to merge 1 commit into
Conversation
…xed tag Co-Authored-By: Lorenzo Cian <17258265+lcian@users.noreply.github.com>
Contributor
|
BYK
requested changes
Oct 27, 2026
BYK
left a comment
Member
There was a problem hiding this comment.
Adds a releaseName option to the github target so repos that release several products without release workspaces can title GitHub releases with the prefixed tag instead of the bare changelog heading.
Our goal should be to move those products/projects to workspaces and fix whatever is holding them back.
This branch was successfully deployed
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.
Adds a
releaseNameoption to thegithubtarget so repos that release several products without release workspaces can title GitHub releases with the prefixed tag instead of the bare changelog heading.Our example: objectstore
getsentry/objectstore releases its Python and Rust clients separately from one repo, with one
.craft.ymlper client and no workspaces:Before: the tags are distinct, but both releases take their title from the changelog heading,
## 0.3.0. So the releases page shows two releases both titled0.3.0:py-client@0.3.00.3.0rs-client@0.3.00.3.0#926 already fixes this, but only inside release workspaces. It left non-workspace configs alone on purpose, so single-product repos with
tagPrefix: vdon't suddenly getv1.2.3titles.After: each config opts in with one line:
py-client@0.3.0py-client@0.3.0rs-client@0.3.0rs-client@0.3.0Behavior
releaseName: changelogtitles the release with the changelog heading as-is.releaseName: taguses the same rule feat(github): Prefix release titles with the workspace tag prefix #926 added for workspaces: if the heading starts with the bare version, that version is replaced with the prefixed tag. Any text after the version is kept, and headings that don't start with the version are used as-is.tagin a release workspace andchangelogotherwise. Nothing changes for existing configs. Workspaces can now opt out withreleaseName: changelog.ConfigurationError.getReleaseName()insrc/targets/github.tsnow checks this option instead of only checking whether a workspace is active. The GitHub target docs cover the option in the table and in the monorepo section.via @lcian.
--
View Junior Session [Sentry]