docs: update PROVENANCE.md for GitHub artifact attestations#21
Merged
docs: update PROVENANCE.md for GitHub artifact attestations#21
Conversation
Contributor
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
kinyoklion
approved these changes
Apr 2, 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.
Requirements
N/A — documentation-only change.
Related issues
Companion to PR #19 / #20 which migrated the release workflow from
slsa-framework/slsa-github-generatortoactions/attest@v4.Describe the solution you've provided
Updates
PROVENANCE.mdto reflect the migration from SLSA provenance to GitHub artifact attestations. The old instructions usedslsa-verifieragainst a.intoto.jsonlfile downloaded from the GitHub release assets. The new instructions usegh attestation verify, which queries GitHub's attestation API directly — no separate provenance file download is needed.Key changes:
slsa-verifier verify-artifactwithgh attestation verify ... -R launchdarkly/openfeature-ruby-servercurlstep to download.intoto.jsonl(attestations are now stored in GitHub's API, not as release assets)gh attestation verifyformatDescribe alternatives you've considered
Could have kept the SLSA verifier instructions alongside the new ones for backward compatibility with older releases, but since the workflow has already been migrated, only the new instructions are relevant going forward.
Additional context
Items for reviewer attention
actions/attestyet in this repo, thegh attestation verifyoutput shown is based on the documented format. Verify it matches reality after the first attested release.gh attestation verifycommand syntax — confirm-R launchdarkly/openfeature-ruby-serveris the correct owner/repo format per the GitHub CLI attestation docs.Link to Devin session: https://app.devin.ai/sessions/7d5bda4d9dbe4ae0b950b30a50485e60
Requested by: @keelerm84
Note
Low Risk
Documentation-only change updating provenance verification guidance; no runtime code or release logic is modified.
Overview
Updates
PROVENANCE.mdto reflect a migration from SLSA.intoto.jsonlrelease-asset provenance to GitHub artifact attestations.Replaces the
slsa-verifier+curldownload flow withgh attestation verifyagainst GitHub’s attestation API, and refreshes the example output and external links accordingly.Written by Cursor Bugbot for commit 522a33b. This will update automatically on new commits. Configure here.