chore(deps): bump hyper from 1.7.0 to 1.8.1 #2466

Open
dependabot[bot] wants to merge 1 commit from refs/pull/2466/head into staging
dependabot[bot] commented 2025-11-24 02:33:42 +00:00 (Migrated from github.com)
Owner

Imported from GitHub pull request.

Original GitHub pull request: #1998
Original author: @dependabot[bot]
Original URL: https://github.com/carverauto/serviceradar/pull/1998
Original created: 2025-11-24T02:33:42Z
Original updated: 2025-12-29T02:16:38Z
Original head: carverauto/serviceradar:dependabot/cargo/hyper-1.8.1
Original base: staging

Bumps 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: https://github.com/hyperium/hyper/compare/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

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

... (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

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 compatibility score

You can trigger a rebase of this PR 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note

Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

Imported from GitHub pull request. Original GitHub pull request: #1998 Original author: @dependabot[bot] Original URL: https://github.com/carverauto/serviceradar/pull/1998 Original created: 2025-11-24T02:33:42Z Original updated: 2025-12-29T02:16:38Z Original head: carverauto/serviceradar:dependabot/cargo/hyper-1.8.1 Original base: staging --- Bumps [hyper](https://github.com/hyperium/hyper) from 1.7.0 to 1.8.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/hyperium/hyper/releases">hyper's releases</a>.</em></p> <blockquote> <h2>v1.8.1</h2> <h2>Bug Fixes</h2> <ul> <li><strong>http1:</strong> fix consuming extra CPU from previous change (<a href="https://redirect.github.com/hyperium/hyper/issues/3977">#3977</a>) (<a href="https://github.com/hyperium/hyper/commit/4492f31e9429c34166da5a069c00b65be20e4a02">4492f31e</a>)</li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/hyperium/hyper/compare/v1.8.0...v1.8.1">https://github.com/hyperium/hyper/compare/v1.8.0...v1.8.1</a></p> <h2>v1.8.0</h2> <h2>Highlights</h2> <h3>Features</h3> <ul> <li><strong>rt:</strong> add <code>Timer::now()</code> method to allow overriding the instant returned (<a href="https://redirect.github.com/hyperium/hyper/issues/3965">#3965</a>) (<a href="https://github.com/hyperium/hyper/commit/5509ebe6156e32d4f8986fafa25c2918a30005be">5509ebe6</a>)</li> </ul> <h3>Bug Fixes</h3> <ul> <li><strong>http1:</strong> fix rare missed write wakeup on connections (<a href="https://redirect.github.com/hyperium/hyper/issues/3952">#3952</a>) (<a href="https://github.com/hyperium/hyper/commit/2377b893f6e64ca9878e4f25d1472b96baa7e3ea">2377b893</a>)</li> <li><strong>http2:</strong> fix internals of HTTP/2 CONNECT upgrades (<a href="https://redirect.github.com/hyperium/hyper/issues/3967">#3967</a>) (<a href="https://github.com/hyperium/hyper/commit/58e0e7dc70612117ccdc40da395922f791cb273a">58e0e7dc</a>, closes <a href="https://redirect.github.com/hyperium/hyper/issues/3966">#3966</a>)</li> </ul> <h3>Breaking Changes</h3> <p>While technically breaking, it's assumed you will not need to do anything or be affected.</p> <ul> <li> <p>The HTTP/2 client connection no longer allows an executor that can not spawn itself.</p> <p>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 <code>!Send</code>, it needs to spawn <code>!Send</code> futures. The likelihood of executors that match the previously allowed behavior should be very remote.</p> <p>There is also technically a semver break in here, which is that the <code>Http2ClientConnExec</code> trait no longer dyn-compatible, because it now expects to be <code>Clone</code>. This should not break usage of the <code>conn</code> builder, because it already separately had <code>E: Clone</code> bounds. If someone were using <code>dyn Http2ClientConnExec</code>, 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. (<a href="https://github.com/hyperium/hyper/commit/58e0e7dc70612117ccdc40da395922f791cb273a">58e0e7dc</a>)</p> </li> </ul> <h2>What's Changed</h2> <ul> <li>chore(ci): update to actions/checkout@v5 by <a href="https://github.com/tottoto"><code>@​tottoto</code></a> in <a href="https://redirect.github.com/hyperium/hyper/pull/3935">hyperium/hyper#3935</a></li> <li>refactor(ffi): specify &quot;C&quot; ABI explicitly in ffi_fn! macro by <a href="https://github.com/1911860538"><code>@​1911860538</code></a> in <a href="https://redirect.github.com/hyperium/hyper/pull/3937">hyperium/hyper#3937</a></li> <li>Update documented default values for <code>http1::Builder</code> by <a href="https://github.com/Will-Low"><code>@​Will-Low</code></a> in <a href="https://redirect.github.com/hyperium/hyper/pull/3938">hyperium/hyper#3938</a></li> <li>fix(client): port tests to in-memory socket by <a href="https://github.com/cratelyn"><code>@​cratelyn</code></a> in <a href="https://redirect.github.com/hyperium/hyper/pull/3947">hyperium/hyper#3947</a></li> <li>feat: allow overriding the instant returned from Timer by <a href="https://github.com/arielb1"><code>@​arielb1</code></a> in <a href="https://redirect.github.com/hyperium/hyper/pull/3965">hyperium/hyper#3965</a></li> <li>fix(http1): poll_loop writes when ready by <a href="https://github.com/lthiery"><code>@​lthiery</code></a> in <a href="https://redirect.github.com/hyperium/hyper/pull/3952">hyperium/hyper#3952</a></li> <li>test(ready_stream): replace tracing with printlns by <a href="https://github.com/seanmonstar"><code>@​seanmonstar</code></a> in <a href="https://redirect.github.com/hyperium/hyper/pull/3973">hyperium/hyper#3973</a></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/hyperium/hyper/blob/master/CHANGELOG.md">hyper's changelog</a>.</em></p> <blockquote> <h3>v1.8.1 (2025-11-13)</h3> <h4>Bug Fixes</h4> <ul> <li><strong>http1:</strong> fix consuming extra CPU from previous change (<a href="https://redirect.github.com/hyperium/hyper/issues/3977">#3977</a>) (<a href="https://github.com/hyperium/hyper/commit/4492f31e9429c34166da5a069c00b65be20e4a02">4492f31e</a>)</li> </ul> <h2>v1.8.0 (2025-11-11)</h2> <h4>Bug Fixes</h4> <ul> <li><strong>http1:</strong> fix rare missed write wakeup on connections (<a href="https://redirect.github.com/hyperium/hyper/issues/3952">#3952</a>) (<a href="https://github.com/hyperium/hyper/commit/2377b893f6e64ca9878e4f25d1472b96baa7e3ea">2377b893</a>)</li> <li><strong>http2:</strong> fix internals of HTTP/2 CONNECT upgrades (<a href="https://redirect.github.com/hyperium/hyper/issues/3967">#3967</a>) (<a href="https://github.com/hyperium/hyper/commit/58e0e7dc70612117ccdc40da395922f791cb273a">58e0e7dc</a>, closes <a href="https://redirect.github.com/hyperium/hyper/issues/3966">#3966</a>)</li> </ul> <h4>Features</h4> <ul> <li><strong>rt:</strong> add <code>Timer::now()</code> method to allow overriding the instant returned (<a href="https://redirect.github.com/hyperium/hyper/issues/3965">#3965</a>) (<a href="https://github.com/hyperium/hyper/commit/5509ebe6156e32d4f8986fafa25c2918a30005be">5509ebe6</a>)</li> </ul> <h4>Breaking Changes</h4> <ul> <li> <p>The HTTP/2 client connection no longer allows an executor that can not spawn itself.</p> <p>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 <code>!Send</code>, it needs to spawn <code>!Send</code> futures. The likelihood of executors that match the previously allowed behavior should be very remote.</p> <p>There is also technically a semver break in here, which is that the <code>Http2ClientConnExec</code> trait no longer dyn-compatible, because it now expects to be <code>Clone</code>. This should not break usage of the <code>conn</code> builder, because it already separately had <code>E: Clone</code> bounds. If someone were using <code>dyn Http2ClientConnExec</code>, 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. (<a href="https://github.com/hyperium/hyper/commit/58e0e7dc70612117ccdc40da395922f791cb273a">58e0e7dc</a>)</p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/hyperium/hyper/commit/166c6cacc74b215674937e782b3ab2cbd8b69883"><code>166c6ca</code></a> v1.8.1</li> <li><a href="https://github.com/hyperium/hyper/commit/4492f31e9429c34166da5a069c00b65be20e4a02"><code>4492f31</code></a> fix(http1): fix consuming extra CPU from previous change (<a href="https://redirect.github.com/hyperium/hyper/issues/3977">#3977</a>)</li> <li><a href="https://github.com/hyperium/hyper/commit/dbe6f25ba2933b883bd8ea1eddc9662c9c816978"><code>dbe6f25</code></a> v1.8.0</li> <li><a href="https://github.com/hyperium/hyper/commit/58e0e7dc70612117ccdc40da395922f791cb273a"><code>58e0e7d</code></a> fix(http2): fix internals of HTTP/2 CONNECT upgrades (<a href="https://redirect.github.com/hyperium/hyper/issues/3967">#3967</a>)</li> <li><a href="https://github.com/hyperium/hyper/commit/0a37a8cd9dd4f2ee7e7e1080eff3cf3a657ec51c"><code>0a37a8c</code></a> test(ready_stream): replace tracing with printlns (<a href="https://redirect.github.com/hyperium/hyper/issues/3973">#3973</a>)</li> <li><a href="https://github.com/hyperium/hyper/commit/2377b893f6e64ca9878e4f25d1472b96baa7e3ea"><code>2377b89</code></a> fix(http1): fix rare missed write wakeup on connections (<a href="https://redirect.github.com/hyperium/hyper/issues/3952">#3952</a>)</li> <li><a href="https://github.com/hyperium/hyper/commit/5509ebe6156e32d4f8986fafa25c2918a30005be"><code>5509ebe</code></a> feat(rt): add <code>Timer::now()</code> method to allow overriding the instant returned ...</li> <li><a href="https://github.com/hyperium/hyper/commit/f9f8f44058745d23fa52abf51b96b61ee7665642"><code>f9f8f44</code></a> tests(client): port tests to in-memory socket (<a href="https://redirect.github.com/hyperium/hyper/issues/3947">#3947</a>)</li> <li><a href="https://github.com/hyperium/hyper/commit/5803a9c0592209269c4009de1f3dbc55b7c115e9"><code>5803a9c</code></a> docs(server): update default values for <code>http1::Builder</code> (<a href="https://redirect.github.com/hyperium/hyper/issues/3938">#3938</a>)</li> <li><a href="https://github.com/hyperium/hyper/commit/e1e1f2b46146ce766947b20117a9ab5eca9e8a3a"><code>e1e1f2b</code></a> refactor(ffi): specify &quot;C&quot; ABI explicitly in ffi_fn! macro (<a href="https://redirect.github.com/hyperium/hyper/issues/3937">#3937</a>)</li> <li>Additional commits viewable in <a href="https://github.com/hyperium/hyper/compare/v1.7.0...v1.8.1">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=hyper&package-manager=cargo&previous-version=1.7.0&new-version=1.8.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) You can trigger a rebase of this PR by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> > **Note** > Automatic rebases have been disabled on this pull request as it has been open for over 30 days.
This pull request is broken due to missing fork information.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin refs/pull/2466/head:refs/pull/2466/head
git switch refs/pull/2466/head

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch staging
git merge --no-ff refs/pull/2466/head
git switch refs/pull/2466/head
git rebase staging
git switch staging
git merge --ff-only refs/pull/2466/head
git switch refs/pull/2466/head
git rebase staging
git switch staging
git merge --no-ff refs/pull/2466/head
git switch staging
git merge --squash refs/pull/2466/head
git switch staging
git merge --ff-only refs/pull/2466/head
git switch staging
git merge refs/pull/2466/head
git push origin staging
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
carverauto/serviceradar!2466
No description provided.