Repository navigation
Attest build provenance of the PHAR and the turbo extension binaries - #6893
Open
ondrejmirtes wants to merge 1 commit into
Open
ondrejmirtes wants to merge 1 commit into
ondrejmirtes wants to merge 1 commit into
Conversation
Sigstore-signed SLSA build provenance, verifiable with gh attestation verify <file> --repo phpstan/phpstan-src, for the binaries the commit job stages into phpstan/phpstan (phpstan.phar, the shared cores and the thin extensions) and for the PIE release assets of phpstan/turbo-ext together with the self-contained binaries inside them. Amp-Thread-ID: https://ampcode.com/threads/T-01a19179-978b-758a-8f1a-7603ee1121c2
| echo "paths<<SUBJECTS" | ||
| printf '%s\n' "$SUBJECTS" | ||
| echo "SUBJECTS" | ||
| } >> "$GITHUB_OUTPUT" |
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.
Adds Sigstore-signed SLSA build provenance attestations (
actions/attestv4.2.2, pinned) for everything this workflow publishes:commitjob: the binaries the commit to phpstan/phpstan adds or changes —phpstan.phar, the shared cores and the thin extensions. Unchanged binaries already in the dist are left out, since this run did not produce them; reused cores are covered because the attestation is made over the exact staged bytes.turbo-pie-releasejob (tags only): the PIE release zips for phpstan/turbo-ext, plus the self-contained.so/.dllinside each, so an extension PIE already installed can be verified too.Both steps run before the commit or the release publish, so nothing unattested ships. Both jobs get
id-token: writeandattestations: write.Verification for users:
The GPG
.ascsignature is unchanged.Not exercised end to end: attestations are only issued on push and tag runs. actionlint (with shellcheck) is clean, and I tested the subject selection against a mock dist checkout (new phar, changed and new binaries included; unchanged core, deleted binary,
.version,.asc,.phar-checksumexcluded; empty selection skips the step).