docs,ci: consumer-side reproducible-build verification (#145) - #233
Merged
Conversation
Makes the deterministic-build claim (#135) independently verifiable: - docs/REPRODUCIBLE-BUILD.md: how a third party clones at the tag, rebuilds with the documented ContinuousIntegrationBuild command, compares sha256s against the published manifest, files a discrepancy, and publishes an attestation (Reproducible Builds project / vouchsafe.io). - scripts/reproducible-manifest.{sh,py}: build each shipped assembly deterministically and emit reproducible-build-manifest.json (assembly hashes + reference OS/SDK). Verified locally: valid 64-char SHAs for both assemblies. - release.yaml: the update-release-artifacts job now generates the manifest (matching #135's ubuntu/net10.0 deterministic build) and attaches it to the GitHub Release. - README: a 'Verify the build' section linking the procedure. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
Addresses the zizmor template-injection finding on #233: the manifest step interpolated ${{ github.event.release.tag_name }} directly into the run block. Pass it through an env var instead so a crafted tag name can't inject shell. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…producible-verify
This was referenced Jul 29, 2026
This was referenced Aug 5, 2026
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.
Makes the deterministic-build claim from #135 independently verifiable — the consumer-side flip.
What's added
docs/REPRODUCIBLE-BUILD.md— the full procedure: match the reference environment, clone at the tag, rebuild with the documented-p:ContinuousIntegrationBuild=truecommand,sha256sumand compare against the published manifest, file a discrepancy, and publish a third-party attestation (Reproducible Builds project / vouchsafe.io).scripts/reproducible-manifest.{sh,py}— build each shipped assembly deterministically and emitreproducible-build-manifest.json(per-assembly SHA-256 + reference OS/SDK + the exact build command). The.pyis split out so the piped hashes stay on stdin (a heredoc-inlined script collides with the interpreter's own stdin).release.yaml— theupdate-release-artifactsjob now generates the manifest (on ubuntu/net10.0, matching [Maintenance] CI/CD: Build reproducibility verification (deterministic builds across runners) #135's deterministic build — not the Windows packing build, so the hashes are what a third party reproduces) and attaches it to the GitHub Release.Verified locally
The generator builds both projects with the CI flag and emits valid 64-char SHA-256 hashes for both assemblies, sorted, well-formed JSON. (Same-environment reproducibility itself is already gated by #135.)
Design note
The manifest is generated with the deterministic build command (ubuntu,
ContinuousIntegrationBuild=true) rather than the release's Windows pack build, because that's the environment the doc tells third parties to reproduce — cross-OS byte-identity isn't guaranteed, so the manifest records the reference OS + SDK to match.Closes #145 when the vNext cycle merges to main.
🤖 Generated with Claude Code