ci: bump sigstore action to v3.5.0 - #93
Merged
Merged
Conversation
sigstore/gh-action-sigstore-python@v3.0.0 installs sigstore-python ~= 3.0, whose embedded Sigstore TUF root predates the production root rotation, so signing fails with "root was signed by 0/3 keys". v3.5.0 pins sigstore 4.5.0 and tuf 7.0.0, which trust the current root. Also set skip-existing on the PyPI publish step: without it, re-running the workflow after a failure in a later job dies on the already-uploaded version instead of getting to the step that actually failed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
leandropineda
approved these changes
Aug 27, 2026
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
2 participants
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.
Problem
The
github-releasejob of Build and Publish fails at Sign the dists with Sigstore (run 33093439102):sigstore/gh-action-sigstore-python@v3.0.0installssigstore ~= 3.0, whose embedded Sigstore TUF root predates the production root rotation, so it cannot verify the current root metadata. This is not transient — every run fails identically until the pin moves.Fallout:
3.2.2published to PyPI, but the Create GitHub Release and Upload artifact signatures steps were skipped, so nov3.2.2release exists.Changes
sigstore/gh-action-sigstore-pythontov3.5.0(pinssigstore==4.5.0,tuf==7.0.0— current root).skip-existing: trueto the PyPI publish step. Without it, re-running the workflow after a failure in a later job dies on the already-uploaded version instead of reaching the step that actually failed.Notes
The
v3.2.2release still has to be created by hand — this fix only applies from the next version bump onward.🤖 Generated with Claude Code