Repository navigation
feat: release reviewed versions with verified build provenance - #63
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.
Outcome
Release Scharf from a reviewed version/notes PR instead of requiring a separately authenticated desktop/CLI to create a tag. Merging this initial PR requests and publishes v1.4.2, including merged #61/#62; this PR itself publishes nothing. The user retains merge control.
Trust boundary and permissions
Only a push to cybrota/scharf main changing
release/version.txtcan publish. The exact event SHA is checked out and tested after deterministic version metadata generation. The same originating workflow creates the tag, builds five ZIPs/checksums, signs GitHub/Sigstore provenance, verifies repository/workflow/source-SHA/source-ref identity, and publishes a draft only after all bytes pass verification. This avoids GITHUB_TOKEN-created tags failing to trigger a separate workflow.Only the release job receives contents:write, id-token:write, attestations:write. Read-only PR jobs cannot publish/sign. No new PAT, stored signing key, settings/secrets changes, auto-merge, or cross-repository token. Homebrew remains a separate reviewed PR after independent artifact verification.
Failure behavior
Strict stable semantic-version ordering uses all tags (v1.4.1 baseline, preserving historical misnumbered v0.5.1). No forced tag movement, asset replacement, or published-release modification. Reruns accept only the identical tag commit and exact matching existing asset bytes; incomplete matching drafts resume. Mismatches fail closed. External administrators remain trusted and API operations cannot be atomic against unrelated writers.
Validation
Docs and sources
See docs/releasing.md and ADR 006 for bootstrap, retry, verification and Homebrew procedure. Primary references: GitHub attestations, workflow token triggers, gh verification, GoReleaser reproducible builds.