Make suffix-free release tags updateable - #184
Merged
Merged
Conversation
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
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.
A release tag such as
v0.2.5did not carry the build commit that every Fabric binary reports. The updater failed its ancestry check, then failed its staged-binary check.This change resolves a suffix-free tag through the GitHub commits API. It builds the exact expected version from the package version and the tagged commit. Legacy tags that already carry a commit keep their exact behavior.
Red proof:
Verification:
v0.2.4+9b425d6check still reports the installed newer build correctly.0.2.4+382c6afand used--tag v0.2.5without an override. It verified and accepted0.2.5+4dc0cac. The old fixture remained unchanged.