Repository navigation
ci: publish GitHub-attested binary releases - #15
Open
beardedeagle wants to merge 3 commits into
Open
beardedeagle wants to merge 3 commits into
beardedeagle wants to merge 3 commits into
Conversation
|
Note The title starts with
|
There was a problem hiding this comment.
🟡 Changes recommended
The release instructions can continue to extract and install an archive after verification fails, potentially installing a rejected archive while reporting success.
1 open issue
What changed in this PR
Adds a binary-release pipeline for Postmaster’s five Linux and macOS targets, with source validation, signed checksums, and GitHub attestations.
Changes:
- Builds, tests, packages, and attests binaries for tag and manual releases, with unsigned pull-request previews.
- Signs release metadata and verifies downloaded draft assets before publication.
- Adds release-tool tests, shared Justfile recipes, and setup and installation documentation.
| File | Description |
|---|---|
| README.md | Links to the release guide. |
| Justfile | Adds shared release build, signing, and verification recipes. |
| docs/src/SUMMARY.md | Adds release documentation to navigation. |
| docs/src/development/releases.md | Documents signing setup, publication, and consumer verification. |
| CHANGELOG.md | Records the new release pipeline. |
| .github/workflows/release.yml | Orchestrates source validation, five-target builds, and publication. |
| .github/release/test_release.py | Tests source restrictions, integrity checks, and publication safeguards. |
| .github/release/sign.sh | Signs checksums with the dedicated Minisign key. |
| .github/release/release.py | Validates sources, packages binaries, and verifies manifests. |
| .github/release/publish.sh | Verifies downloaded draft assets before publishing. |
| .github/release/install-minisign.sh | Installs Minisign after checking its archive digest. |
| .github/CONTRIBUTING.md | Documents release-tool checks for contributors. |
Review effort: Balanced
Comment on lines
+4
to
+5
| push: | ||
| tags: ["v*"] |
This branch has not been deployed
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.

Summary
Publish version-tag and manual binary releases for Postmaster's five Linux/macOS targets. Each target runs release-profile tests, packages the binary and license, smoke-tests the extracted binary, and generates a GitHub build attestation.
The publisher requires the complete target set, binds the tag and source commit in release.json, and attests that metadata and the SHA-256 manifest. It downloads every draft asset and verifies its inventory, checksums, workflow identity, triggering commit/ref, and hosted-runner provenance before publication. Existing releases cannot be replaced.
How was this verified?
6d6e28f: both Quality jobs, both Nix jobs, Docs, release validation, and all five release builds. The publisher is intentionally skipped on PRs. Actual OIDC attestation generation and public publication require a tag/manual release run.Checklist
just ci-rustpasses locally.just docssucceeds and describes the release workflow.