feat(features): make default verification independent of HTTP and Tokio - #213
Merged
Merged
Conversation
Signed-off-by: Wolf Vollprecht <w.vollprecht@gmail.com>
wolfv
force-pushed
the
pre1/offline-http
branch
from
September 5, 2026 19:16
65c5be0 to
888b3a6
Compare
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.
Small follow-up to #212: feature gates and dependency declarations, not a transport abstraction.
Validation: workspace all-feature tests, strict Clippy, Rust 1.86, docs, isolated features, native-TLS checks and no-default-feature Rekor/TSA/verifier tests passed. Default sigstore-verify and sigstore-bundle, plus offline Rekor/TSA builds, have no reqwest/hyper/Tokio normal dependencies.