docs: bake CI hardening into a 2.2.1 release#30
Merged
Conversation
Cuts a 2.2.1 patch so the in-toto provenance file (PR #28) and the SHA-pinned OSS-Fuzz base image (PR #29) ship in a tagged GitHub Release. Both were ``ci:`` commits that release-please skipped. Practical effect: Scorecard's Signed-Releases check will see the provenance bundle in v2.2.1's release assets and lift from 8/10 to 10/10. No source/behaviour change versus v2.2.0 — the wheel and sdist bytes are identical apart from version metadata. Body change: extend the release-pipeline diagram in CONTRIBUTING.md to mention the new provenance asset. Release-As: 2.2.1 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.
Why
Cuts a 2.2.1 patch so the in-toto provenance file (PR #28) and the SHA-pinned OSS-Fuzz base image (PR #29) ship in a tagged GitHub Release. Both were `ci:` commits that release-please skipped.
Practical effect: Scorecard's Signed-Releases check will see the provenance bundle in v2.2.1's release assets and lift from 8/10 → 10/10. No source/behaviour change versus v2.2.0 — wheel and sdist bytes are identical apart from version metadata.
The visible body change is a small extension to the release-pipeline diagram in CONTRIBUTING.md to mention the new provenance asset. `Release-As: 2.2.1` in the squash message forces release-please to cut the patch.
🤖 Generated with Claude Code