Skip to content

docs: update PROVENANCE.md for GitHub artifact attestations#21

Merged
keelerm84 merged 2 commits intomainfrom
devin/1775079854-update-provenance-docs
Apr 2, 2026
Merged

docs: update PROVENANCE.md for GitHub artifact attestations#21
keelerm84 merged 2 commits intomainfrom
devin/1775079854-update-provenance-docs

Conversation

@keelerm84
Copy link
Copy Markdown
Member

@keelerm84 keelerm84 commented Apr 1, 2026

Requirements

  • I have added test coverage for new or changed functionality
  • I have followed the repository's pull request submission guidelines
  • I have validated my changes against all supported platform versions

N/A — documentation-only change.

Related issues

Companion to PR #19 / #20 which migrated the release workflow from slsa-framework/slsa-github-generator to actions/attest@v4.

Describe the solution you've provided

Updates PROVENANCE.md to reflect the migration from SLSA provenance to GitHub artifact attestations. The old instructions used slsa-verifier against a .intoto.jsonl file downloaded from the GitHub release assets. The new instructions use gh attestation verify, which queries GitHub's attestation API directly — no separate provenance file download is needed.

Key changes:

  • Replaced all SLSA framework references with GitHub artifact attestation references
  • Replaced slsa-verifier verify-artifact with gh attestation verify ... -R launchdarkly/openfeature-ruby-server
  • Removed the curl step to download .intoto.jsonl (attestations are now stored in GitHub's API, not as release assets)
  • Updated sample output to match gh attestation verify format
  • Updated external doc links to point to GitHub's attestation docs

Describe 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

  1. Sample output is representative, not captured from an actual run — since no release has been made with actions/attest yet in this repo, the gh attestation verify output shown is based on the documented format. Verify it matches reality after the first attested release.
  2. gh attestation verify command syntax — confirm -R launchdarkly/openfeature-ruby-server is 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.md to reflect a migration from SLSA .intoto.jsonl release-asset provenance to GitHub artifact attestations.

Replaces the slsa-verifier + curl download flow with gh attestation verify against 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.

@keelerm84 keelerm84 requested a review from a team as a code owner April 1, 2026 21:45
@devin-ai-integration
Copy link
Copy Markdown
Contributor

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@keelerm84 keelerm84 merged commit 314f11e into main Apr 2, 2026
5 checks passed
@keelerm84 keelerm84 deleted the devin/1775079854-update-provenance-docs branch April 2, 2026 16:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants