Repository navigation
Use shared CLI binary release automation - #16
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.
Add a binary release workflow using the pinned tools automation. The existing project verification gate runs before packaging/attesting Linux and macOS Intel/ARM archives and publishing a new release.
The shared publisher verifies complete artifacts and checksums, refuses existing release identities, and verifies every uploaded draft asset before publishing. Existing release tags and assets remain unchanged.
Validation: actionlint passed; full project checks run in CI.
Preserve the existing five-target build and artifact verification while aligning archive names with the shared installer contract.
Need help on this PR? Tag
@codesmith-botwith what you need.