6.5.3

### Deps
- `h1-client` now uses `dashmap` at version `5.x >`, fixing an unsoundness issue.

6.5.2

### Deps
- Now only uses `dashmap` for `h1-client`.

6.5.1

Same as 6.5.0 with one change:

`Config::max_connections_per_host()` is now properly named `Config::set_max_connections_per_host()`.

### Added
- `Config` has been stabilized and is now available by default!
- `wasm_client` support for `Config` (only timeouts).
- `Config::max_connections_per_host` (Supported on `h1_client` and `curl_client`.)

### Deprecated
- `H1Client::with_max_connections()` was been superseded by `Config::max_connections_per_host`.

6.5.0

- `Config` has been stabilized and is now available by default!
- `wasm_client` support for `Config` (only timeouts).
- `Config::max_connections_per_host` (Supported on `h1_client` and `curl_client`.)

- `H1Client::with_max_connections()` was been superseded by `Config::max_connections_per_host`.

6.4.1

### Docs
- Added `"unstable-config"` to the docs builds.

6.4.0

### Added
- Added a new `unstable-config` feature, which exposes runtime configuration via a new `Config` struct.

6.4.0

### Added
- Added a new `unstable-config` feature, which exposes runtime configuration via a new `Config` struct.

6.3.5

### Fixed
- Multiple headers of the same name are now present with any client backend and not just `h1_client`.
- Connection when multiple IPs are present for a hostname not function with the `h1_client` backend.

6.3.4

### Fixed
- `h1_client` connection pools now properly check if connections are still alive before recycling them.
     - Like, actually properly this time.
     - There is a test now to ensure closed connections don't cause errors.

6.3.3

### Fixed
- `h1_client` connection pools now properly check if connections are still alive before recycling them.