Release integrity
Pinned-binary integrations should download GitHub Release assets directly and
verify the complete evidence set before executing the binary. install.sh and
cargo install git-std remain standalone convenience flows for human use.
Targets and asset set
| Platform | Target |
|---|---|
| Linux x86-64 | x86_64-unknown-linux-musl |
| Linux ARM64 | aarch64-unknown-linux-musl |
| macOS x86-64 | x86_64-apple-darwin |
| macOS Apple Silicon | aarch64-apple-darwin |
| Windows x86-64 | x86_64-pc-windows-msvc |
For every target, a release publishes this inseparable set:
git-std-<target>.tar.gz
git-std-<target>.tar.gz.sha256
git-std-<target>.tar.gz.sigstore.json
git-std-<target>.tar.gz.spdx.json
git-std-<target>.tar.gz.provenance.sigstore.json
The archive contains git-std (git-std.exe for Windows) and generated man
pages at its root. The checksum names the exact archive bytes. The SPDX 2.3
document records the archive name, release version, and SHA-256 digest. The
signature bundle is a keyless Sigstore blob signature. The provenance bundle is
generated by GitHub artifact attestations with the archive as its subject.
Local verification
Local verification is offline and does not establish signer identity:
scripts/release/verify.sh git-std-<target>.tar.gz vX.Y.Z
It checks the allowed target name, archive layout, checksum, SPDX version and subject data, and JSON shape/presence of both Sigstore bundles. The release test suite proves success and rejection of altered bytes, checksums, SBOM metadata, and missing bundles:
just test-release
Hosted verification
Hosted verification additionally checks the transparency-log certificate and GitHub provenance identity:
scripts/release/verify.sh git-std-<target>.tar.gz vX.Y.Z --hosted
This invokes cosign verify-blob with the repository workflow identity and
gh attestation verify with the saved provenance bundle. It requires Cosign,
GitHub CLI, network access, and evidence generated by GitHub Actions.
The release workflow is designed for SLSA Build Level 2: a hosted build service generates signed provenance for the exact artifact. This branch has only local verification, so its achieved level is not yet claimed. Claim Build Level 2 for a version only after the hosted workflow and attestation verification succeed.
Real-release verification
A real-release check confirms facts local tests cannot:
- all five jobs cross-build successfully;
- OIDC keyless signing and transparency-log inclusion succeed;
- GitHub stores and verifies each provenance attestation;
- the GitHub Release exposes all 25 expected files without renaming; and
- downloaded bytes pass hosted verification independently.
Manual workflow_dispatch runs build and evidence generation but never create
a Release or publish crates. Only a v* tag enables those jobs.
Release v0.11.15 has archives and .tar.gz.sha256 files for all five targets,
but no Sigstore, SPDX, or provenance companions. The enhanced evidence set is
unreleased on this branch. Update this mapping after the first verified release;
do not infer conformance from a closed issue or a successful local test.
Collecting generated man pages
Release builds capture Cargo JSON messages and match the git-std binary’s
manifest to the workspace package. The collector uses that package’s
build-script-executed.out_dir to locate generated man pages. It does not
search Cargo’s private build directory layout, which changed in Cargo 1.100.
Custom target and build directories therefore do not require new globs.
For cross v0.2.5, the collector maps the container’s /target and /project
mounts to the host directories reported by Cargo metadata.
Collection requires a successful build, one matching build-script output,
and the main git-std.1 page. Missing or ambiguous outputs fail packaging;
other build directories cannot supply fallback pages. Previously staged
man pages are replaced. Signature, provenance, checksum, and smoke gates
remain required before publication.
Run just test-release for layout and rejection fixtures. Before publishing
a packaging correction, dispatch the release workflow on its reviewed branch
and require all five target builds and smoke jobs to pass. Manual dispatch
runs the integrity gates without creating a release or publishing crates.