diff --git a/reqwest-middleware/CHANGELOG.md b/reqwest-middleware/CHANGELOG.md index 685f086..6779fcd 100644 --- a/reqwest-middleware/CHANGELOG.md +++ b/reqwest-middleware/CHANGELOG.md @@ -6,6 +6,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ## [Unreleased] +## [0.4.2] - 2025-04-08 + +### Added +- Deprecated `fetch_mode_no_cors` as it's been deprecated in reqwest. + ## [0.4.1] - 2025-02-24 - Fixed wasm32 by disabling incompatible parts. On that target, `ClientWithMiddleware` is no longer diff --git a/reqwest-middleware/Cargo.toml b/reqwest-middleware/Cargo.toml index bc3c547..1440017 100644 --- a/reqwest-middleware/Cargo.toml +++ b/reqwest-middleware/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "reqwest-middleware" -version = "0.4.1" +version = "0.4.2" authors = ["Rodrigo Gryzinski "] edition = "2018" description = "Wrapper around reqwest to allow for client middleware chains." diff --git a/reqwest-middleware/src/client.rs b/reqwest-middleware/src/client.rs index 7740536..c4bf50d 100644 --- a/reqwest-middleware/src/client.rs +++ b/reqwest-middleware/src/client.rs @@ -527,6 +527,7 @@ impl RequestBuilder { /// The [request mode][mdn] will be set to 'no-cors'. /// /// [mdn]: https://developer.mozilla.org/en-US/docs/Web/API/Request/mode + #[deprecated(note = "Deprecated Upstream")] pub fn fetch_mode_no_cors(self) -> Self { RequestBuilder { inner: self.inner.fetch_mode_no_cors(), diff --git a/reqwest-retry/src/retryable_strategy.rs b/reqwest-retry/src/retryable_strategy.rs index 55c5409..8a790c4 100644 --- a/reqwest-retry/src/retryable_strategy.rs +++ b/reqwest-retry/src/retryable_strategy.rs @@ -7,10 +7,10 @@ use reqwest_middleware::Error; /// A [`RetryableStrategy`] has a single `handler` functions. /// The result of calling the request could be: /// - [`reqwest::Response`] In case the request has been sent and received correctly -/// This could however still mean that the server responded with a erroneous response. -/// For example a HTTP statuscode of 500 +/// This could however still mean that the server responded with a erroneous response. +/// For example a HTTP statuscode of 500 /// - [`reqwest_middleware::Error`] In this case the request actually failed. -/// This could, for example, be caused by a timeout on the connection. +/// This could, for example, be caused by a timeout on the connection. /// /// Example: /// diff --git a/reqwest-tracing/CHANGELOG.md b/reqwest-tracing/CHANGELOG.md index 10ae9bb..88f0379 100644 --- a/reqwest-tracing/CHANGELOG.md +++ b/reqwest-tracing/CHANGELOG.md @@ -7,6 +7,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ## [Unreleased] +## [0.5.7] - 2025-04-08 + ### Added - Added support for OpenTelemetry `0.29` ([#228](https://github.com/TrueLayer/reqwest-middleware/pull/228)) diff --git a/reqwest-tracing/Cargo.toml b/reqwest-tracing/Cargo.toml index cab6bd0..69dd74c 100644 --- a/reqwest-tracing/Cargo.toml +++ b/reqwest-tracing/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "reqwest-tracing" -version = "0.5.6" +version = "0.5.7" authors = ["Rodrigo Gryzinski "] edition = "2018" description = "Opentracing middleware for reqwest."