release-workflow: tag releases as <suite>/<version>#137
Merged
keerthi-go merged 1 commit intomainfrom Apr 27, 2026
Merged
Conversation
The previous tagging scheme used a fixed "debian/" prefix for all release tags (e.g. debian/1.0.0-1). This caused a conflict when the same upstream version was released to multiple distribution branches (e.g. noble, trixie): the tag created by the first release would already exist when the second release attempted to push it, causing the workflow to fail. Fix this by prefixing the tag with the distro codename (inputs.distro-codename) instead of the static "debian/" string, producing tags of the form <suite>/<version> (e.g. noble/1.0.0-1, trixie/1.0.0-1). Each suite+version combination now gets a unique tag, allowing concurrent releases of the same upstream version to different distribution branches. Signed-off-by: Keerthi Gowda <kbalehal@qti.qualcomm.com>
keerthi-go
requested review from
bjordiscollaku,
simonbeaudoin0935 and
vishwasudupa
as code owners
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
2 participants
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.
The previous tagging scheme used a fixed "debian/" prefix for all release tags (e.g. debian/1.0.0-1). This caused a conflict when the same upstream version was released to multiple distribution branches (e.g. noble, trixie): the tag created by the first release would already exist when the second release attempted to push it, causing the workflow to fail.
Fix this by prefixing the tag with the distro codename (inputs.distro-codename) instead of the static "debian/" string, producing tags of the form / (e.g. noble/1.0.0-1, trixie/1.0.0-1). Each suite+version combination now gets a unique tag, allowing concurrent releases of the same upstream version to different distribution branches.