Skip to content

Commit 591ab44

Browse files
authored
Deprecate fetch_mode_no_cors and prepare for release (#230)
* Chore: Fix clippy lint * Fix: Deprecate fetch_mode_no_cors as it's being removed upstream * Chore: Bump versions for release
1 parent af885fd commit 591ab44

File tree

6 files changed

+13
-5
lines changed

6 files changed

+13
-5
lines changed

reqwest-middleware/CHANGELOG.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
66

77
## [Unreleased]
88

9+
## [0.4.2] - 2025-04-08
10+
11+
### Added
12+
- Deprecated `fetch_mode_no_cors` as it's been deprecated in reqwest.
13+
914
## [0.4.1] - 2025-02-24
1015

1116
- Fixed wasm32 by disabling incompatible parts. On that target, `ClientWithMiddleware` is no longer

reqwest-middleware/Cargo.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
[package]
22
name = "reqwest-middleware"
3-
version = "0.4.1"
3+
version = "0.4.2"
44
authors = ["Rodrigo Gryzinski <rodrigo.gryzinski@truelayer.com>"]
55
edition = "2018"
66
description = "Wrapper around reqwest to allow for client middleware chains."

reqwest-middleware/src/client.rs

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -527,6 +527,7 @@ impl RequestBuilder {
527527
/// The [request mode][mdn] will be set to 'no-cors'.
528528
///
529529
/// [mdn]: https://developer.mozilla.org/en-US/docs/Web/API/Request/mode
530+
#[deprecated(note = "Deprecated Upstream")]
530531
pub fn fetch_mode_no_cors(self) -> Self {
531532
RequestBuilder {
532533
inner: self.inner.fetch_mode_no_cors(),

reqwest-retry/src/retryable_strategy.rs

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,10 +7,10 @@ use reqwest_middleware::Error;
77
/// A [`RetryableStrategy`] has a single `handler` functions.
88
/// The result of calling the request could be:
99
/// - [`reqwest::Response`] In case the request has been sent and received correctly
10-
/// This could however still mean that the server responded with a erroneous response.
11-
/// For example a HTTP statuscode of 500
10+
/// This could however still mean that the server responded with a erroneous response.
11+
/// For example a HTTP statuscode of 500
1212
/// - [`reqwest_middleware::Error`] In this case the request actually failed.
13-
/// This could, for example, be caused by a timeout on the connection.
13+
/// This could, for example, be caused by a timeout on the connection.
1414
///
1515
/// Example:
1616
///

reqwest-tracing/CHANGELOG.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
77

88
## [Unreleased]
99

10+
## [0.5.7] - 2025-04-08
11+
1012
### Added
1113
- Added support for OpenTelemetry `0.29` ([#228](https://github.com/TrueLayer/reqwest-middleware/pull/228))
1214

reqwest-tracing/Cargo.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
[package]
22
name = "reqwest-tracing"
3-
version = "0.5.6"
3+
version = "0.5.7"
44
authors = ["Rodrigo Gryzinski <rodrigo.gryzinski@truelayer.com>"]
55
edition = "2018"
66
description = "Opentracing middleware for reqwest."

0 commit comments

Comments
 (0)