Conversation
Tags created through the GitHub Release UI are lightweight and ignored by the plain git describe invocation used by setlocalversion. This results in an invalid VERSION value in /etc/os-release. Add a manually dispatched workflow that creates an annotated tag for the selected revision and prepares a draft GitHub Release from that tag. The draft can then be reviewed and published to trigger the existing release builds. Validate published release tags before starting those builds to prevent artifacts from being generated from lightweight tags. Fixes: #77 Signed-off-by: Ozan Durgut <ozan.durgut@analog.com>
This branch has not been 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
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.
Tags created through the GitHub Release UI are lightweight and ignored by the plain git describe invocation used by setlocalversion. This results in an invalid VERSION value in /etc/os-release.
Add a manually dispatched workflow that creates an annotated tag for the selected revision and prepares a draft GitHub Release from that tag. The draft can then be reviewed and published to trigger the existing release builds.
Validate published release tags before starting those builds to prevent artifacts from being generated from lightweight tags.
Fixes: #77