Re-export reqwest crate (#158)

* Re-export reqwest crate

In a large project, it's not unheard of for multiple mutually-incompatible versions of a major crate like `reqwest` to end up in the mix.  By re-exporting the version of `reqwest` used by `reqwest-middleware`, we can be sure we're referring to the *correct* `reqwest`, rather than some other, incompatible, `reqwest`.

* Update CHANGELOG.md

---------

Co-authored-by: Ethan Brierley <ethanboxx@gmail.com>
This commit is contained in:
Matt Palmer 2024-06-27 05:35:44 +10:00 committed by GitHub
parent 226562735c
commit 524e044fd7
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 2 additions and 0 deletions

View file

@ -8,6 +8,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
### Added
- Added support for `opentelemetry` version `0.23`.
- Added re-export of `reqwest`.
- `http2`, `rustls-tls`, and `charset` features, which simply enable those features in `reqwest`.
## [0.3.1]

View file

@ -58,3 +58,4 @@ pub use client::{ClientBuilder, ClientWithMiddleware, RequestBuilder};
pub use error::{Error, Result};
pub use middleware::{Middleware, Next};
pub use req_init::{Extension, RequestInitialiser};
pub use reqwest;