Update axum monorepo

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
axum	dependencies	minor	=0.7.9 -> =0.8.1
axum-extra	dependencies	minor	=0.9.6 -> =0.10.0

---

Release Notes

tokio-rs/axum (axum)

v0.8.0: axum v0.8.0

Compare Source

since rc.1

• breaking: axum::extract::ws::Message now uses Bytes in place of Vec<u8>,
  and a new Utf8Bytes type in place of String, for its variants (#​3078)
• breaking: Remove OptionalFromRequestParts impl for Query (#​3088)
• changed: Upgraded tokio-tungstenite to 0.26 (#​3078)
• changed: Query/Form: Use serde_path_to_error to report fields that failed to parse (#​3081)

full changelog

Note: there are further relevant changes in axum-core's changelog

• breaking: Upgrade matchit to 0.8, changing the path parameter syntax from /:single and /*many to /{single} and /{*many}; the old syntax produces a panic to avoid silent change in behavior (#​2645)
• breaking: Require Sync for all handlers and services added to Router and MethodRouter (#​2473)
• breaking: The tuple and tuple_struct Path extractor deserializers now check that the number of parameters matches the tuple length exactly (#​2931)
• breaking: Move Host extractor to axum-extra (#​2956)
• breaking: Remove WebSocket::close. Users should explicitly send close messages themselves. (#​2974)
• breaking: Make serve generic over the listener and IO types (#​2941)
• breaking: Remove Serve::tcp_nodelay and WithGracefulShutdown::tcp_nodelay.
  See serve::ListenerExt for an API that let you set arbitrary TCP stream properties. (#​2941)
• breaking: Option<Path<T>> no longer swallows all error conditions,
  instead rejecting the request in many cases; see its documentation for details (#​2475)
• breaking: axum::extract::ws::Message now uses Bytes in place of Vec<u8>,
  and a new Utf8Bytes type in place of String, for its variants (#​3078)
• fixed: Skip SSE incompatible chars of serde_json::RawValue in Event::json_data (#​2992)
• fixed: Don't panic when array type is used for path segment (#​3039)
• fixed: Avoid setting content-length before middleware.
  This allows middleware to add bodies to requests without needing to manually set content-length (#​2897)
• change: Update minimum rust version to 1.75 (#​2943)
• changed: Upgraded tokio-tungstenite to 0.26 (#​3078)
• changed: Query/Form: Use serde_path_to_error to report fields that failed to parse (#​3081)
• added: Add method_not_allowed_fallback to set a fallback when a path matches but there is no handler for the given HTTP method (#​2903)
• added: Add NoContent as a self-described shortcut for StatusCode::NO_CONTENT (#​2978)
• added: Add support for WebSockets over HTTP/2. They can be enabled by changing get(ws_endpoint) handlers to any(ws_endpoint) (#​2894)
• added: Add MethodFilter::CONNECT, routing::connect[_service] and MethodRouter::connect[_service] (#​2961)
• added: Extend FailedToDeserializePathParams::kind enum with (ErrorKind::DeserializeError). This new variant captures both key, value, and message from named path parameters parse errors, instead of only deserialization error message in ErrorKind::Message. (#​2720)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package [email protected] --precise 0.8.1
    Updating crates.io index
error: failed to select a version for the requirement `axum = "^0.7"`
candidate versions found which didn't match: 0.8.1
location searched: crates.io index
required by package `utoipa-axum v0.1.3`
    ... which satisfies dependency `utoipa-axum = "=0.1.3"` (locked to 0.1.3) of package `crates_io v0.0.0 (/tmp/renovate/repos/github/rust-lang/crates.io)`

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path crates/crates_io_session/Cargo.toml --package [email protected] --precise 0.8.1
    Updating crates.io index
error: failed to select a version for the requirement `axum = "^0.7"`
candidate versions found which didn't match: 0.8.1
location searched: crates.io index
required by package `utoipa-axum v0.1.3`
    ... which satisfies dependency `utoipa-axum = "=0.1.3"` (locked to 0.1.3) of package `crates_io v0.0.0 (/tmp/renovate/repos/github/rust-lang/crates.io)`

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[eth3lbert]

LGTM 👍 thank you!
And it's good to see that the error parse field from the query/form will be included in the error message after this update. 🎉

---

The following two places are comments that we might also want to change, but missed in this PR:

• crates.io/src/models/team.rs

  Line 114 in 07db90a

  // GET orgs/:org/teams

• crates.io/src/models/team.rs

  Line 218 in 07db90a

  // GET /organizations/:org_id/team/:team_id/memberships/:username

[Turbo87]

those comments are for paths on the GitHub API side, which is why I didn't touch them :)

[eth3lbert]

Ah, great! I have no further concerns then.