ci: PEP 740 attestations via astral-sh/attest-action; middleware 0.0.3 - #878
Merged
Conversation
…e 0.0.3 Restores what #873 traded away, without reintroducing the toolchain skew. uv publish UPLOADS attestation files found beside the dists by default (--no-attestations is the opt-out) — it just doesn't MINT them. Astral's own publishing example pairs it with astral-sh/attest-action for exactly that. One toolchain end to end, attestations back. - attest step gated to the real release (a dry run uploads nothing for attestations to accompany); SHA pin f589a42a verified against tag v0.0.6 (lightweight tag, commit direct); the action's input is (glob) — caught by reading action.yml at the pinned SHA, not the README - middleware bumped to 0.0.3: attestations are only provable on a fresh upload, and PyPI versions are immutable. No code change; consumers pin >=0.0.2 and are unaffected. The 0.0.3 upload doubles as the verification (simple-API provenance must flip from 'none') Verified locally: 0.0.2 artifacts pass current twine check (Metadata 2.5), YAML parses. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
blove
enabled auto-merge (squash)
August 30, 2026 20:16
Contributor
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.
Resolves the attestation trade-off from #873 — it turns out there wasn't one.
What I had wrong in #873
I wrote "uv publish doesn't support attestations yet." Half-wrong:
uv publishuploads attestation files found beside the dists by default (--no-attestationsis the opt-out) — it just doesn't mint them. Astral's own GHA publishing example pairs it with theirattest-actionfor the minting step. So we can have one toolchain end to end and attestations; no version skew re-enters because nothing validates metadata twice with different tools.Changes
Generate PEP 740 attestationsstep (real release only — a dry run uploads nothing for them to accompany), pinnedastral-sh/attest-action@f589a42a # v0.0.6, SHA verified against the tag per the action-pin discipline. The input ispaths(whitespace-separated globs) — caught by readingaction.ymlat the pinned SHA rather than trusting my first guess ofpath.examples/chat,cockpit/langgraph/client-tools) pin>=0.0.2/>=0.0.1and are unaffected.Verification plan (after merge)
files[].provenancefor the 0.0.3 wheel + sdist must be non-null — the same query that showednonefor 0.0.2Also verified while investigating: current twine passes our Metadata-Version 2.5 artifacts, so the pypa-action path would work again today too — but it re-arms the two-toolchain skew, which is how #873 happened.
🤖 Generated with Claude Code