Bump hyper from 1.3.1 to 1.5.1 #427
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [hyper](https://github.com/hyperium/hyper) from 1.3.1 to 1.5.1. - [Release notes](https://github.com/hyperium/hyper/releases) - [Changelog](https://github.com/hyperium/hyper/blob/master/CHANGELOG.md) - [Commits](hyperium/hyper@v1.3.1...v1.5.1) --- updated-dependencies: - dependency-name: hyper dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
DryRun Security SummaryThe provided code changes update the Expand for full summarySummary: The provided code changes are updates to the From an application security perspective, these changes are generally benign and are likely to improve the overall security and stability of the project. Updating dependencies to their latest versions is a common practice to ensure that the project benefits from the latest bug fixes, security patches, and performance improvements. However, it's important to review the release notes and changelogs of the updated dependencies to understand the specific changes and any potential security implications. Additionally, it's a good practice to keep all project dependencies up-to-date, as older versions may have known vulnerabilities that could potentially be exploited. Files Changed:
Code AnalysisWe ran |
|
Superseded by #431. |
Bumps hyper from 1.3.1 to 1.5.1.
Release notes
Sourced from hyper's releases.
... (truncated)
Changelog
Sourced from hyper's changelog.
... (truncated)
Commits
3b7375av1.5.165026b2chore(dependencies): remove libc crate from dependencies (#3377)4a20147fix(http2): pass proper value to h2 max_local_error_reset_streams4694f38chore(ci): pin hashbrown in MSRV job (#3783)13b0594fix(http2): improve graceful shutdown during handshake (#3729)906f8dbdocs(lib): do not inline http rexports720d2dbdocs(lib): fix up misleading example about unstable features17fddd3test(client): unflake client try_send_request unit testc68d424v1.5.03900a23perf(http1): improve parsing of sequentially partial messagesDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)