Repository navigation
fix(deps): update sigstore-verify to 0.10.0 - #10677
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Central YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (2)
📝 WalkthroughWalkthroughBumps ChangesSigstore-verify Dependency Upgrade
Estimated code review effort: 2 (Simple) | ~10 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Motivation: sinelaw/fresh#2528 |
Greptile SummaryThis PR updates
Confidence Score: 5/5Safe to merge — fixes a live breakage (TSA cert rotation) with minimal, well-scoped API adaptations and no behavioural changes beyond the dependency upgrade. All three code changes are direct, mechanical API adaptations driven by removed/renamed symbols in the new library version. The No files require special attention. Important Files Changed
Reviews (3): Last reviewed commit: "Merge branch 'main' into fix-sigstore-ve..." | Re-trigger Greptile |
Renovate's bump to 0.9.0 (jdx#10640) only edited the manifest and left mise-sigstore failing to compile against the crate's breaking API changes. This goes to 0.10.0 — the first release whose embedded GitHub trusted root includes GitHub's late-June 2026 TSA certificate rotation — and adapts the calling code: - SigningScheme::uses_sha256() was removed (0.9.0); the remaining supports_prehashed() guard is equivalent here since the only prehashed-capable scheme mise emits is EcdsaP256Sha256. - verify_signature_prehashed() now takes &[u8] instead of &Sha256Hash; pass artifact_hash.as_bytes(). - Artifact::from_digest() now takes &[u8]; use the From<&Sha256Hash> impl. - TufConfig::custom() dropped its root argument (0.10.0, jdx#136); the root moves to the with_root() builder. Cargo.lock swaps the tough-based TUF stack for the in-house sigstore-tuf crate. The GitHub trusted root stays embedded; switching it to a TUF fetch so rotations are picked up automatically is a worthwhile follow-up. Without this, `mise install github:<owner>/<repo>@<tag>` fails with "TSA timestamp verification failed: no certificate matches issuer and serial number" for any release timestamped after the cert rotation. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
a0466ce to
d1eb6a0
Compare
Updates
sigstore-verify0.8.0 → 0.10.0 and adapts the calling code.GitHub rotated its Sigstore TSA certificate in late June 2026. mise verifies
GitHub attestations against the trusted root embedded in
sigstore-verify, and0.8.0's snapshot predates the new cert, so releases timestamped after the
rotation fail:
0.10.0 is the first release whose embedded GitHub root contains the rotated cert.
0.9.0 (proposed in #10640) does not, and also fails to compile.
API changes adapted:
SigningScheme::uses_sha256()removed → usesupports_prehashed()alone(equivalent; the only prehashed scheme mise emits is
EcdsaP256Sha256).verify_signature_prehashed()takes&[u8]not&Sha256Hash→artifact_hash.as_bytes().Artifact::from_digest()takes&[u8]→Artifact::from(&digest).TufConfig::custom()dropped its root arg →.with_root(...)builder.Cargo.lock swaps the
toughTUF stack for the in-housesigstore-tufcrate.The GitHub root stays embedded. 0.10.0 also adds
TufConfig::github(), whichenables fetching it over GitHub's TUF URL so future rotations are picked up
automatically — left to a follow-up PR.
Summary by CodeRabbit