Add release provenance verification - #81
Merged
Merged
Conversation
There was a problem hiding this comment.
Verdict
APPROVE
No material findings in the supplied change.
Scope health
Convergence: slowing. Review mode: initial.
Recommended action: CONTINUE_INCREMENTAL.
-
20 changed files
Prior findings
| Finding | Status |
|---|---|
| — | No prior finding state |
New findings
No new findings.
Fix-induced regressions
- None evidenced.
Uncertainty
- No material uncertainty recorded.
Validation
- Reviewed release artifact flow, checksum/SBOM verification, attestation sequencing, and distribution/plugin identity validation from the supplied immutable diff. Exact-head CI was reported as passed.
Residual risks
- None identified.
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.
Summary
Implements issue #76's release-provenance and installation-verification machinery.
Why
Skilldeck's first trusted release needs users and operators to be able to independently verify the released package, generated Claude plugin, and SBOM without treating a download as implicitly trusted.
Validation
.venv/bin/pytest -q— 156 passed.venv/bin/ruff check scripts src tests.venv/bin/ruff format --check scripts src tests.venv/bin/mypy srcpython3 scripts/build_plugin.py --checkgit diff --checkRelease boundary
This PR creates verification machinery only. It does not create a tag, publish to PyPI, or deploy anything. The first real publication and external PyPI/GitHub attestation readback remain the issue #80 release gate.