Repository navigation
A release keeps its draft's tag while attaching the installers - #48
Merged
aleksandrychev merged 1 commit intoOct 12, 2026
Merged
Conversation
Marking a prepared draft as a pre-release without sending its tag made GitHub clear the tag, so it had to be picked again before publishing. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Signed-off-by: Ihor Aleksandrychiev <ihor.aleksandrychiev@northern.tech>
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.
For v0.1.0, the Release workflow attached the installers to the prepared draft, but its update marking the draft as a pre-release didn't send the tag, and GitHub cleared it (the draft showed
untagged-…), so the tag had to be picked again before publishing. The update now sends the tag along.🤖 Generated with Claude Code