reqwest-middleware breaking changes

• reqwest-retry-v0.5.0 \u2192 reqwest-tracing-v0.5.0breaking

  The keys emitted by the crate now match the stable Semantic Conventions for HTTP Spans.

• reqwest-retry-v0.5.0 \u2192 reqwest-tracing-v0.5.0breaking

  Upgraded `reqwest-middleware` to `0.3.0`.

• reqwest-retry-v0.5.0 \u2192 reqwest-tracing-v0.5.0breaking

  Removed support for `opentelemetry` 0.13 to 0.19

• reqwest-middleware-v0.5.0 \u2192 reqwest-retry-v0.9.0breaking

  Updated `retry-policies` (re-exported as `reqwest_retry::policies`) to 0.5.

• reqwest-middleware-v0.4.0 \u2192 reqwest-retry-v0.7.0breaking

  Errors are now reported as `RetryError` that adds the number of retries to the error chain if there were any. This changes the returned error types.

• reqwest-middleware-v0.3.0 \u2192 reqwest-retry-v0.5.0breaking

  Upgraded `reqwest-middleware` to `0.3.0`.

• reqwest-tracing-v0.5.3 \u2192 reqwest-middleware-v0.4.0breaking

  `request_middleware::Error` is now a transparent error enum and doesn't add its own context anymore.

• unknown \u2192 reqwest-middleware-v0.3.0breaking

  Upgraded `reqwest` to `0.12.0`

• unknown \u2192 reqwest-middleware-v0.3.0breaking

  Removed default-features `json` and `multipart` from `reqwest` dependency

• unknown \u2192 reqwest-middleware-v0.3.0breaking

  Added `json` and `multipart` features to `reqwest-middleware`

• unknown \u2192 reqwest-middleware-v0.3.0breaking

  Upgraded `matchit` to `0.8.0`

• unknown \u2192 reqwest-middleware-v0.3.0breaking

  You may need to update some matches that look like `/a/:some_var` to `/a/{some_var}`

Get this data programmatically \u2014 free, no authentication.