Bump reqwest from 0.11.27 to 0.12.12 - #250
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
Bumps [reqwest](https://github.com/seanmonstar/reqwest) from 0.11.27 to 0.12.12. - [Release notes](https://github.com/seanmonstar/reqwest/releases) - [Changelog](https://github.com/seanmonstar/reqwest/blob/master/CHANGELOG.md) - [Commits](seanmonstar/reqwest@v0.11.27...v0.12.12) --- updated-dependencies: - dependency-name: reqwest dependency-version: 0.12.12 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
reqwest 0.11.27 → 0.12.12 review
Verdict: safe to merge — no code changes required.
Usage audit
reqwest is used only through its stable high-level API across crates/common (api/client.rs, function.rs, papi.rs, assets.rs, mod.rs) and crates/ev-enclave (api/enclave.rs, enclave_assets.rs, mod.rs, deploy/mod.rs, attest/mod.rs, plus the #[from] reqwest::Error error enums):
Client::new()/Client::builder().timeout(..).build()RequestBuilderverbs +.header/.json/.body/.bearer_auth/.basic_auth/.sendResponse::{status, json, text, bytes},StatusCode,ErrorBody::wrap_stream(..)andBody::from(tokio::fs::File)reqwest::header::{USER_AGENT, ACCEPT}re-exports
None of these signatures changed between 0.11 and 0.12.
Changelog review (0.11.27 → 0.12.12)
- The single 0.12.0 breaking change is the internal upgrade to hyper / http / http-body v1. This project never touches
hyper/httptypes directly, so it's transparent. - Default TLS stays
native-tlsin 0.12 — the switch to rustls-as-default is v0.13.0, which is not part of this PR. Runtime certificate-verification behaviour is unchanged. - The
jsonandstreamfeatures (both enabled in the manifests) still exist in 0.12.
Lockfile notes
- native-tls is retained (
hyper-tls+tokio-native-tlsremain reqwest deps), so the default connector is unchanged. hyper-rustls/rustls 0.23appear only via Cargo feature-unification fromsentry; they are not the default connector for this crate's clients.- ev-enclave's direct
tokio-rustls 0.24(used by the attestation TLS verifier inattest/mod.rs) is unaffected and still present in the lock.
Verification
cargo build— pass (only pre-existing, unrelated warnings)cargo test -p ev-cli -p ev-enclave -p common --no-run— pass (all test binaries compile)cargo clippy— pass (warnings only, pre-existing)
No source edits were needed; the change compiles and is behaviourally equivalent for how this repo uses reqwest.
Note: dependabot labels this a "semver-minor" update, but for a 0.x crate 0.11→0.12 is effectively a major bump; the checks above confirm compatibility regardless.
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
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.
Bumps reqwest from 0.11.27 to 0.12.12.
Release notes
Sourced from reqwest's releases.
... (truncated)
Changelog
Sourced from reqwest's changelog.
... (truncated)
Commits
8b8fdd2v0.12.121ef8703(wasm) fix: remove tower as dependency for wasm32-unknown-unknown (#2510)224f0b8v0.12.11beea332fix decoding extra empty frame (#2508)177cc7fcleanup: typo fix409cff3v0.12.10ea48da7docs: fix a few spelling issues (#2478)3ce98b5fix: propagate Body::size_hint when wrapping bodies (#2503)44ca5eeremove Clone from connect::Unnameable for now (#2502)2a7c1b6feat: allow pluggable tower layers in connector service stack (#2496)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)