Bump axum from 0.7.9 to 0.8.9 - #6
Open
dependabot[bot] wants to merge 3 commits into
Open
Conversation
dependabot
Bot
added
dependencies
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
flock | 7a7f5af | Aug 02 2026, 06:35 PM |
dependabot
Bot
force-pushed
the
dependabot/cargo/axum-0.8.9
branch
from
August 2, 2026 18:03
8676994 to
1ffa786
Compare
Bumps [axum](https://github.com/tokio-rs/axum) from 0.7.9 to 0.8.9. - [Release notes](https://github.com/tokio-rs/axum/releases) - [Changelog](https://github.com/tokio-rs/axum/blob/main/CHANGELOG.md) - [Commits](tokio-rs/axum@axum-v0.7.9...axum-v0.8.9) --- updated-dependencies: - dependency-name: axum dependency-version: 0.8.9 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/cargo/axum-0.8.9
branch
from
August 2, 2026 18:20
1ffa786 to
05c3529
Compare
axum 0.8 retyped `Message::Text` from `String` to `Utf8Bytes` (and `Message::Binary` to `Bytes`) so a send no longer has to copy the payload. `Utf8Bytes: From<String>` covers the one call site here, and the snapshot was already being cloned for `last_sent`, so nothing extra is allocated. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The axum 0.8 bump only failed to compile on `Message::Text` (fixed in the
previous commit), but it carried a second breaking change that compiles
perfectly and panics at runtime: path captures moved from `:id` to `{id}`,
and `Router::route` rejects the old form when it builds the router.
All eight of flock's captures used it, including two — /api/devices/{id}
and /api/groups/{tag}/{tab} — on wrapped `.route(` calls that a
single-line grep misses. Nothing in the existing 23 tests constructs the
router, so CI would have gone green on a binary that panicked on startup.
Hence the smoke test: it builds the real router via `app()`, which is the
only thing that exercises route registration. Verified it earns its place
by reverting one capture and watching it fail with the axum panic.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps axum from 0.7.9 to 0.8.9.
Release notes
Sourced from axum's releases.
... (truncated)
Commits
c59208crevert axum-core changelog changes99068f5Revert "FixIntoResponsefor tuples overriding error response codes (#3603)"23d7098Revert "axum-core 0.5.6"e8a39adaxum-macros 0.5.16e9a249axum-extra 0.12.60ec9041axum 0.8.9c3fcebbaxum-core 0.5.6a8790fcupdate release notes26ba7bbdocs: consolidate state management docs in crate root (#3683)9fc59efUpdate to tokio-tungstenite 0.29 (#3689)