ci: add deterministic release artifact contract - #321
Merged
Conversation
codeforester
force-pushed
the
bug/215-20260814-release-artifact-contract
branch
from
August 14, 2026 14:15
e1ae06f to
59836b4
Compare
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.
Summary
scripts/release-artifactbuilder and verifier for the v2 release lineIssue
Closes #215
Validation
./tests/validate.shbats tests/release-artifact.batsshellcheck --severity=warning scripts/release-artifact tests/release-artifact.bats tests/validate.sh tests/lint-warnings.shshfmt -d -ln bash -i 4 -sr scripts/release-artifact tests/validate.sh tests/lint-warnings.shgit diff --checkCI Impact
Adds the release-artifact script to the repository quality and validation gates.
Docs Impact
Updates the release process and single-file distribution guidance with the canonical artifact workflow.
Release Impact
This PR does not publish a tag, GitHub Release, Homebrew formula, or downstream pin. The existing release guard remains fail-closed until the reviewed RC/GA gates and #240 cutover are complete.