fix(release): skip attestation on private repo, bump to 0.3.1 - #10
Merged
Conversation
The v0.3.0 tag's release run failed at the attestation step --
GitHub's attestation API rejects it for a user-owned private repository
("Feature not available for user-owned private repositories"), which
could only be discovered against a real tag push. The job never reached
"Create GitHub Release", so v0.3.0 has no published release.
release.yml now guards the attestation step on
`!github.event.repository.private`, so it skips cleanly now and starts
running automatically once this repository goes public -- no workflow
change needed then. The archive and its checksum are unaffected.
SECURITY.md documents the current gap. Version bumped to 0.3.1; this
release supersedes the never-published v0.3.0 tag.
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
v0.3.0tag's release run failed at the "Generate build provenance attestation" step: GitHub's attestation API rejects attestation for a user-owned private repository. The job never reached "Create GitHub Release", sov0.3.0has no published release -- this PR/release supersedes it..github/workflows/release.ymlnow guards that step on!github.event.repository.private, so it skips cleanly now and will start running automatically once the repository goes public.SECURITY.mddocuments the current gap.Test plan
python3 -m pytest tests/unit tests/integration -q-- 541 passedpython3 scripts/sync_version.py --checkAfter merge: tag
v0.3.1onmasterand push the tag.🤖 Generated with Claude Code