Fix double beta release and wrong release channel detection - #16
Merged
Conversation
Krathe82
pushed a commit
to Krathe82/DandersFrames
that referenced
this pull request
Jun 6, 2026
Fix double beta release and wrong release channel detection
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.
Follow-up to #7.
Double release:
nightly-beta.ymlcreates the tag via API withPAT_TOKEN, which already triggersrelease.ymlthroughon: push: tags. The additionalgh workflow runcall caused a second identical build.Wrong channel:
git describe --exact-match --tags HEADis ambiguous when multiple tags point to the same commit (e.g.v4.0.5andv4.0.5-beta.1). The tag is now passed explicitly from the CI context viaOVERRIDE_TAG.