build(deps): bump bytes from 1.11.0 to 1.11.1 in /lmp-core in the cargo group across 1 directory#1
Conversation
Bumps the cargo group with 1 update in the /lmp-core directory: [bytes](https://github.com/tokio-rs/bytes). Updates `bytes` from 1.11.0 to 1.11.1 - [Release notes](https://github.com/tokio-rs/bytes/releases) - [Changelog](https://github.com/tokio-rs/bytes/blob/master/CHANGELOG.md) - [Commits](tokio-rs/bytes@v1.11.0...v1.11.1) --- updated-dependencies: - dependency-name: bytes dependency-version: 1.11.1 dependency-type: direct:production dependency-group: cargo ... 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
Comment |
![ai-coding-guardrails[bot]](https://avatars.githubusercontent.com/in/1202546?s=60&v=4){kind=small}
There was a problem hiding this comment.
I've got 1 comment for you to consider
The PR title and description are not accurate. Here are my suggestions:
Proposed title: build(deps): bump bytes from 1.5 to 1.11.1 in /lmp-core
Proposed description:
Bumps bytes from 1.5 to 1.11.1 in the /lmp-core directory.
This is a significant version update that includes multiple releases and importantly fixes an integer overflow vulnerability in BytesMut::reserve in version 1.11.1.
Updates bytes from 1.5 to 1.11.1
Release notes
Sourced from bytes's releases.
Bytes v1.11.1
1.11.1 (February 3rd, 2026)
- Fix integer overflow in
BytesMut::reserve
List of skipped files due to configuration
Think our bots are missing some context? Add custom requirements or guardrails in our management console
Bumps the cargo group with 1 update in the /lmp-core directory: bytes.
Updates
bytesfrom 1.11.0 to 1.11.1Release notes
Sourced from bytes's releases.
Changelog
Sourced from bytes's changelog.
Commits
417dccdRelease bytes v1.11.1 (#820)d0293b0Merge commit from forkDependabot 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 <dependency name> major versionwill 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 versionwill 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 conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.