PR-F4: Add release verification docs for attestations + SBOM evidence#1206
Merged
PR-F4: Add release verification docs for attestations + SBOM evidence#1206
Conversation
This was referenced Apr 24, 2026
plan.md is already gitignored (/plan.md in .gitignore). Untracked here so it stops shipping in the PR diff; file remains on disk locally for session context. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Top-level docs/source/index.rst toctree is a weirdly prominent place for supply-chain verification content — it sat as a peer of the entire `graphistry` API module. Move the guide to repo root (RELEASE_VERIFICATION.md) until a dedicated docs Security section exists to host it. - mv docs/source/release-verification.md -> RELEASE_VERIFICATION.md - drop toctree entry from docs/source/index.rst - update SECURITY.md link + note the rehoming follow-up (#1208) Follow-up tracked in #1208. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
RELEASE_VERIFICATION.md was punching above its weight as a top-level doc for ~60 lines of supply-chain guidance. Trim hard and fold the essential commands into a "Verifying Releases" section in SECURITY.md. - pypi-attestations verify recipe - gh run download recipe for SBOM evidence - pointer to canonical PyPI attestations docs - pointer to #1208 for the eventual docs Security section Drops operational notes and verbose framing; downstream verifiers get what they need in one place. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The "tracked in #1208" line was internal planning context, not consumer-facing security content. Drop it. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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
docs/source/release-verification.mdwith consumer verification steps for PyPI attestations/provenanceSECURITY.mdrelease-verificationto docs index toctreeplan.mdfor context-free resumption of this sliceWhy
Follow-up for trusted release hardening PR-F4 after PR-F3 merged, tracked in #1205.
Validation
Closes #1205