build(deps): bump the axum group with 2 updates

[dependabot]

Bumps the axum group with 2 updates: axum and hyper.

Updates axum from 0.8.6 to 0.8.7

Release notes

Sourced from axum's releases.

axum v0.8.7

• Relax implicit Send / Sync bounds on RouterAsService, RouterIntoService (#3555)
• Make it easier to visually scan for default features (#3550)
• Fix some documentation typos

#3550: tokio-rs/axum#3550 #3555: tokio-rs/axum#3555

Commits

• 4404f27 Release axum v0.8.7 and axum-extra v0.12.2
• 8f1545a Fix typo in extractors guide (#3554)
• 4fc3faa Relax implicit Send / Sync bounds (#3555)
• a05920c Make it easier to visually scan for default features (#3550)
• 6d5e6d5 Use extensions directly in from_request_parts (#3542)
• fe607e6 Fixes wording typo (#3540)
• f9ce3e5 Release axum-extra 0.12.1
• 12e1cf9 Add back package.metadata.docs.rs for axum-extra
• 914a35a Release axum-extra 0.12.0
• e20e90d Upgrade axum-extra to prost v0.14 (#3517)
• Additional commits viewable in compare view

Updates hyper from 1.7.0 to 1.8.1

Release notes

Sourced from hyper's releases.

v1.8.1

Bug Fixes

• http1: fix consuming extra CPU from previous change (#3977) (4492f31e)

Full Changelog: hyperium/hyper@v1.8.0...v1.8.1

v1.8.0

Highlights

Features

• rt: add Timer::now() method to allow overriding the instant returned (#3965) (5509ebe6)

Bug Fixes

• http1: fix rare missed write wakeup on connections (#3952) (2377b893)
• http2: fix internals of HTTP/2 CONNECT upgrades (#3967) (58e0e7dc, closes #3966)

Breaking Changes

While technically breaking, it's assumed you will not need to do anything or be affected.

• The HTTP/2 client connection no longer allows an executor that can not spawn itself.

  This was an oversight originally. The client connection will now include spawning a future that keeps a copy of the executor to spawn other futures. Thus, if it is !Send, it needs to spawn !Send futures. The likelihood of executors that match the previously allowed behavior should be very remote.

  There is also technically a semver break in here, which is that the Http2ClientConnExec trait no longer dyn-compatible, because it now expects to be Clone. This should not break usage of the conn builder, because it already separately had E: Clone bounds. If someone were using dyn Http2ClientConnExec, that will break. However, there is no purpose for doing so, and it is not usable otherwise, since the trait only exists to propagate bounds into hyper. Thus, the breakage should not affect anyone. (58e0e7dc)

What's Changed

• chore(ci): update to actions/checkout@v5 by @​tottoto in hyperium/hyper#3935
• refactor(ffi): specify "C" ABI explicitly in ffi_fn! macro by @​1911860538 in hyperium/hyper#3937
• Update documented default values for http1::Builder by @​Will-Low in hyperium/hyper#3938
• fix(client): port tests to in-memory socket by @​cratelyn in hyperium/hyper#3947
• feat: allow overriding the instant returned from Timer by @​arielb1 in hyperium/hyper#3965
• fix(http1): poll_loop writes when ready by @​lthiery in hyperium/hyper#3952
• test(ready_stream): replace tracing with printlns by @​seanmonstar in hyperium/hyper#3973

... (truncated)

Changelog

Sourced from hyper's changelog.

v1.8.1 (2025-11-13)

Bug Fixes

• http1: fix consuming extra CPU from previous change (#3977) (4492f31e)

v1.8.0 (2025-11-11)

Bug Fixes

• http1: fix rare missed write wakeup on connections (#3952) (2377b893)
• http2: fix internals of HTTP/2 CONNECT upgrades (#3967) (58e0e7dc, closes #3966)

Features

• rt: add Timer::now() method to allow overriding the instant returned (#3965) (5509ebe6)

Breaking Changes

• The HTTP/2 client connection no longer allows an executor that can not spawn itself.

  This was an oversight originally. The client connection will now include spawning a future that keeps a copy of the executor to spawn other futures. Thus, if it is !Send, it needs to spawn !Send futures. The likelihood of executors that match the previously allowed behavior should be very remote.

  There is also technically a semver break in here, which is that the Http2ClientConnExec trait no longer dyn-compatible, because it now expects to be Clone. This should not break usage of the conn builder, because it already separately had E: Clone bounds. If someone were using dyn Http2ClientConnExec, that will break. However, there is no purpose for doing so, and it is not usable otherwise, since the trait only exists to propagate bounds into hyper. Thus, the breakage should not affect anyone. (58e0e7dc)

Commits

• 166c6ca v1.8.1
• 4492f31 fix(http1): fix consuming extra CPU from previous change (#3977)
• dbe6f25 v1.8.0
• 58e0e7d fix(http2): fix internals of HTTP/2 CONNECT upgrades (#3967)
• 0a37a8c test(ready_stream): replace tracing with printlns (#3973)
• 2377b89 fix(http1): fix rare missed write wakeup on connections (#3952)
• 5509ebe feat(rt): add Timer::now() method to allow overriding the instant returned ...
• f9f8f44 tests(client): port tests to in-memory socket (#3947)
• 5803a9c docs(server): update default values for http1::Builder (#3938)
• e1e1f2b refactor(ffi): specify "C" ABI explicitly in ffi_fn! macro (#3937)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Labels

The following labels could not be found: dependencies, rust. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.