fix: snap version being nightlyv0 in stable#480
Merged
andrinoff merged 1 commit intofloatpane:masterfrom Apr 9, 2026
Merged
Conversation
Signed-off-by: drew <me@andrinoff.com>
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.
What?
Fixes snapcraft stable version named
nightlyv0by excluding thenightlyv0tag from being pulled, when checking the latest version. The issue with the naming was caused by starting the release after merging a PR commit, therefore starting the process of a nightly build, and the release build simultaneously. This caused the nightlyv0 tag to appear when the release workflow was on the step of checking the latest version, which wasnightlyv0.Why?
The issue caused incorrect metrics in snapcraft, as well as a surprise for people using
latest/stableto seenightlyv0as the version.