Bump hyper from 1.3.1 to 1.6.0

[dependabot]

Bumps hyper from 1.3.1 to 1.6.0.

Release notes

Sourced from hyper's releases.

v1.6.0

Features

• ext: add ext::on_informational() callback extension (#3818) (8ce1fcfa, closes #2565)
• server: add http1::Builder::ignore_invalid_headers(bool) option (#3824) (3817a79b)

Bug Fixes

• server:
  • start http1 header read timeout when conn is idle (#3828) (10b09ffc, closes #3780, #3781)
  • change max_local_error_reset_streams function to &mut self (#3820) (e981a91e)

Breaking Changes

• http2::Builder::max_local_error_reset_streams() now takes &mut self and returns &mut Self. In practice, this shouldn't break almost anyone. It was the wrong receiver and return types. (e981a91e)

New Contributors

• @​finnbear made their first contribution in hyperium/hyper#3820

Thanks

• @​GlenDC
• @​tottoto
• @​seanmonstar

Full Changelog: hyperium/hyper@v1.5.2...v1.6.0

v1.5.2

Bug Fixes

• http1:
  • fix intermitent panic parsing partial headers (#3812) (a131111f, closes #3811)
  • skip debug assertion of content length for HEAD responses (#3795) (eaf2267c, closes #3794)

Features

• ffi: (unstable) add cargo-c support (#3787) (7f4a6826, closes #3786)

New Contributors

• @​23doors made their first contribution in hyperium/hyper#3795
• @​ionionascu made their first contribution in hyperium/hyper#3799
• @​linyihai made their first contribution in hyperium/hyper#3800
• @​suzp1984 made their first contribution in hyperium/hyper#3807

Thanks

• @​seanmonstar

Full Changelog: hyperium/hyper@v1.5.1...v1.5.2

... (truncated)

Changelog

Sourced from hyper's changelog.

v1.6.0 (2025-01-28)

Bug Fixes

• server:
  • start http1 header read timeout when conn is idle (#3828) (10b09ffc, closes #3780, #3781)
  • change max_local_error_reset_streams function to &mut self (#3820) (e981a91e)

Features

• ext: add ext::on_informational() callback extension (#3818) (8ce1fcfa, closes #2565)
• server: add http1::Builder::ignore_invalid_headers(bool) option (#3824) (3817a79b)

Breaking Changes

• http2::Builder::max_local_error_reset_streams() now takes &mut self and returns &mut Self. In practice, this shouldn't break almost anyone. It was the wrong receiver and return types. (e981a91e)

v1.5.2 (2024-12-16)

Bug Fixes

• http1:
  • fix intermitent panic parsing partial headers (#3812) (a131111f, closes #3811)
  • skip debug assertion of content length for HEAD responses (#3795) (eaf2267c, closes #3794)

Features

• ffi: add cargo-c support (#3787) (7f4a6826, closes #3786)

v1.5.1 (2024-11-19)

Bug Fixes

• http2:
  • pass proper value to h2 max_local_error_reset_streams (4a20147a)
  • improve graceful shutdown during handshake (#3729) (13b05943)

v1.5.0 (2024-10-15)

... (truncated)

Commits

• 621d8e4 v1.6.0
• 83f4588 chore(LICENSE): update copyright year
• 10b09ff fix(server): start http1 header read timeout when conn is idle (#3828)
• 8ce1fcf feat(ext): add ext::on_informational() callback extension (#3818)
• de28b0e chore(ci): use msrv aware dependency resolver (#3831)
• 5baf537 chore(ci): use yq to get rust-version in manifest (#3829)
• 3817a79 feat(server): add http1::Builder::ignore_invalid_headers(bool) option (#3824)
• e981a91 fix(server): change max_local_error_reset_streams function to &mut self (...
• 30f2961 v1.5.2
• a131111 fix(http1): fix intermitent panic parsing partial headers (#3812)
• 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 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)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[dryrunsecurity]

DryRun Security Summary

The code changes involve updating the Hyper dependency from version 1.2.0 to 1.6.0 in both Cargo.toml and Cargo.lock files, which is generally positive for security but requires reviewing release notes to ensure no new vulnerabilities are introduced.

Expand for full summary

Summary:

The provided code changes include updates to the Cargo.toml and Cargo.lock files, which are the configuration and lock files for the Rust package manager, Cargo. The key change is the update of the hyper dependency from version 1.2.0 to 1.6.0. This is generally a positive change from an application security perspective, as newer versions of libraries often include security fixes and improvements.

However, it's important to review the release notes or change logs for the new version of a dependency to understand what has changed and whether there are any potential security implications. Additionally, the Cargo.toml file includes several other dependencies, such as axum, metrics, and tracing, which should also be reviewed for any security-related updates. Keeping all dependencies up-to-date is a crucial security practice, but it's essential to ensure that the updates do not introduce any new vulnerabilities or breaking changes that could impact the application's security.

Files Changed:

1. Cargo.toml:

   • The key change is the update of the hyper dependency from version 1.2.0 to 1.6.0.
   • This is generally a positive change, as it likely includes security fixes and improvements.
   • However, the release notes or change logs for the new version of hyper should be reviewed to ensure that the update does not introduce any new vulnerabilities or breaking changes.
   • The file also includes several other dependencies, such as axum, metrics, and tracing, which should also be reviewed for any security-related updates.

2. Cargo.lock:

   • This file updates the hyper dependency from version 1.3.1 to version 1.6.0 across multiple crates.
   • Updating to the latest version of hyper helps ensure the application is using the most secure and stable version of the library.
   • Overall, this change appears to be a routine dependency update that should help improve the security and stability of the application.

Code Analysis

We ran 9 analyzers against 2 files and 0 analyzers had findings. 9 analyzers had no findings.

View PR in the DryRun Dashboard.