Repository navigation
Use publishable tags for prebuilt releases - #78
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
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.
GitHub rejects a published release whose tag is a raw 40-character commit SHA. Manual builds now use
build-<SHA>and tag builds retain the triggeringv*tag; the artifact download URL and draft tag share that value, while filenames and source provenance stay pinned to the full SHA.Clarifies that a recorded address/checksum-only packaging correction must preserve every other archive member and verify final published URLs and digests. No application, binary or image changes.
Validation: actionlint 1.7.12 with ShellCheck 0.11.0, 12 manifest tests, and extracted workflow-shell checks for manual/tag builds, SHA rejection and URL/draft consistency passed. The release batch already completed server make check with four known Dashboard failures (WEB-TEST-002); this workflow-only follow-up does not rerun model combinations. Local make check cannot start with the installed older Go toolchain. Small follow-up independently inspected by the main thread.
Need help on this PR? Tag
@codesmithwith what you need. Autofix is disabled.