docs: consumer-side reproducible-build verification (#225) - #311
Merged
Conversation
Flips the reproducible-build story to the consumer side: #216 proves our build is reproducible internally; this documents how a third party verifies it independently. - docs/REPRODUCIBLE-BUILD.md — the exact tooling (SDK 10.0.x, ContinuousIntegrationBuild=true), the rebuild command, how to hash the shipped assembly (the deterministic artifact — NOT the .nupkg envelope, whose zip timestamps are non-deterministic), how to compare against the release manifest, how to file a discrepancy, and the third-party attestation conventions (reproducible-builds.org / vouchsafe.io / attest-build-provenance over a rebuild). - release.yaml now generates reproducible-build-manifest.json — the expected sha256 of every shipped TFM assembly, extracted from the .nupkg — and attaches it to the GitHub Release. Verified the extraction/hash logic against the live 0.16.1 package (all 11 TFM assemblies). - README gains a "Verify the build" section linking the procedure. Closes #225 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…p (SC2010) actionlint/shellcheck flagged SC2010 (Don't use ls | grep) in the Generate reproducible-build manifest step added for #225. Select the first non-symbols .nupkg with a glob loop + case guard instead, and fail explicitly if none is found. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This was referenced Jul 24, 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.
Summary
Flips the reproducible-build story to the consumer side (issue #225). #216 proves our build is reproducible internally (builds twice, compares hashes); this documents and enables independent third-party verification — so "our builds are reproducible" stops being an unverifiable claim.
docs/REPRODUCIBLE-BUILD.md— the exact tooling (SDK10.0.x,ContinuousIntegrationBuild=true), the rebuild command, how to hash the shipped assembly (the deterministic artifact — not the.nupkgenvelope, whose zip entry timestamps are non-deterministic), how to compare against the manifest, how to report a discrepancy, and the third-party attestation conventions (reproducible-builds.org / vouchsafe.io /attest-build-provenanceover a rebuild).release.yamlnow generatesreproducible-build-manifest.json— the expectedsha256of every shipped TFM assembly, extracted from the.nupkg— and attaches it to the GitHub Release.Acceptance criteria (#225)
docs/REPRODUCIBLE-BUILD.md(tooling, command, expected hashes, discrepancy procedure)release.yamlpublishesreproducible-build-manifest.jsonwith expected hashesValidation
release.yaml..nupkg— correctly extracted and hashed all 11 target-framework assemblies. (The manifest step itself only runs on a real release.)Closes #225