release: v0.8.4 — Fulcio cert pin rotation hotfix#120
Merged
Conversation
Single-commit-content release: v0.8.3 tagged cleanly and shipped to crates.io, but the release.yml::Build & Release WASM Component job failed (so the GitHub Release object never created) because Sigstore rotated the fulcio.sigstore.dev leaf cert. PR #119 landed the new pin on main; this release re-cuts a tag where the code does contain the fix. Trace: skip Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Single-commit-content release that re-cuts the v0.8.3 release at a tag whose code does contain the Fulcio pin fix from PR #119. v0.8.3 itself shipped to crates.io but its GitHub Release object was never created because the WASM Component signing failed on the stale pin. This release fixes that.
Closes #117 (already closed by #119; mentioned here for traceability). See CHANGELOG.md for the full release notes.