chore: release alkhttp 0.4.1

- version bump 0.4.0 -> 0.4.1 (patch: the MSRV raise is a metadata
  change that breaks no downstream able to build the crate before)
- README usage snippet 0.4 -> 0.4.1
- changelog: cut [0.4.1] with the alkcall 0.7.1 consumption + the
  rust-version 1.85 -> 1.88 floor raise under Changed

Verification: cargo publish --dry-run --allow-dirty (cargo test/clippy/
fmt green in the preceding deps commit)
This commit is contained in:
2026-09-10 03:05:45 +00:00
parent 660ccf3e76
commit e854947c86
4 changed files with 23 additions and 3 deletions
+20
View File
@@ -6,6 +6,26 @@ this crate adheres to [Semantic Versioning](https://semver.org/).
## [Unreleased]
## [0.4.1] — 2026-09-10
### Changed
- **`rust-version` floor raised 1.85 → 1.88** (patch bump, no API change).
The 1.85 claim was already false at the dependency level: the resolved
lockfile pulls `icu_*` 2.x (MSRV 1.86 via `jsonschema``idna`) and —
since alkcall 0.7.1 — alkcall itself declares 1.88, so 1.85 toolchains
cannot build the tree regardless of what Cargo.toml declared. Raising
the floor to 1.88 aligns with the ecosystem MSRV decision (noq QUIC
path; recorded for alktls in OQ-TLS-08) and breaks no downstream that
could build the crate before. Verified: 1.88 toolchain `cargo test
--locked` + clippy `--all-targets -D warnings` clean; one 1.88 clippy
lint fixed (`uninlined_format_args` in a `forward.rs` test).
- **`alkcall` dependency consumed at 0.7.1** (lockfile bump; the
`version = "0.7"` requirement already covered it). No code change
forced — alkcall 0.7.1's changes are its own MSRV-floor raise plus the
cf-006/cf-007 feature work already consumed in the 0.7.0 wave.
## [0.4.0] — 2026-09-07
### Changed
Generated
+1 -1
View File
@@ -48,7 +48,7 @@ dependencies = [
[[package]]
name = "alkhttp"
version = "0.4.0"
version = "0.4.1"
dependencies = [
"alkcall",
"arc-swap",
+1 -1
View File
@@ -1,6 +1,6 @@
[package]
name = "alkhttp"
version = "0.4.0"
version = "0.4.1"
edition = "2021"
rust-version = "1.88"
license = "MIT OR Apache-2.0"
+1 -1
View File
@@ -161,7 +161,7 @@ A lean single-side build takes `default-features = false` plus the side
it needs:
```toml
alkhttp = { version = "0.4", default-features = false, features = ["server"] }
alkhttp = { version = "0.4.1", default-features = false, features = ["server"] }
```
## Security posture