renovate[bot]
fb49c103d5
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [bytes](https://redirect.github.com/tokio-rs/bytes) | workspace.dependencies | minor | `1.10.1` → `1.11.1` | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. ### GitHub Vulnerability Alerts #### [GHSA-434x-w66g-qw3r](https://redirect.github.com/tokio-rs/bytes/security/advisories/GHSA-434x-w66g-qw3r) # Details In the unique reclaim path of `BytesMut::reserve`, the condition ```rs if v_capacity >= new_cap + offset ``` uses an unchecked addition. When `new_cap + offset` overflows `usize` in release builds, this condition may incorrectly pass, causing `self.cap` to be set to a value that exceeds the actual allocated capacity. Subsequent APIs such as `spare_capacity_mut()` then trust this corrupted `cap` value and may create out-of-bounds slices, leading to UB. This behavior is observable in release builds (integer overflow wraps), whereas debug builds panic due to overflow checks. ## PoC ```rs use bytes::*; fn main() { let mut a = BytesMut::from(&b"hello world"[..]); let mut b = a.split_off(5); // Ensure b becomes the unique owner of the backing storage drop(a); // Trigger overflow in new_cap + offset inside reserve b.reserve(usize::MAX - 6); // This call relies on the corrupted cap and may cause UB & HBO b.put_u8(b'h'); } ``` # Workarounds Users of `BytesMut::reserve` are only affected if integer overflow checks are configured to wrap. When integer overflow is configured to panic, this issue does not apply. --- ### Release Notes <details> <summary>tokio-rs/bytes (bytes)</summary> ### [`v1.11.1`](https://redirect.github.com/tokio-rs/bytes/blob/HEAD/CHANGELOG.md#1111-February-3rd-2026) [Compare Source](https://redirect.github.com/tokio-rs/bytes/compare/v1.11.0...v1.11.1) - Fix integer overflow in `BytesMut::reserve` ### [`v1.11.0`](https://redirect.github.com/tokio-rs/bytes/blob/HEAD/CHANGELOG.md#1110-November-14th-2025) [Compare Source](https://redirect.github.com/tokio-rs/bytes/compare/v1.10.1...v1.11.0) - Bump MSRV to 1.57 ([#​788](https://redirect.github.com/tokio-rs/bytes/issues/788)) ##### Fixed - fix: `BytesMut` only reuse if src has remaining ([#​803](https://redirect.github.com/tokio-rs/bytes/issues/803)) - Specialize `BytesMut::put::<Bytes>` ([#​793](https://redirect.github.com/tokio-rs/bytes/issues/793)) - Reserve capacity in `BytesMut::put` ([#​794](https://redirect.github.com/tokio-rs/bytes/issues/794)) - Change `BytesMut::remaining_mut` to use `isize::MAX` instead of `usize::MAX` ([#​795](https://redirect.github.com/tokio-rs/bytes/issues/795)) ##### Internal changes - Guarantee address in `slice()` for empty slices. ([#​780](https://redirect.github.com/tokio-rs/bytes/issues/780)) - Rename `Vtable::to_*` -> `Vtable::into_*` ([#​776](https://redirect.github.com/tokio-rs/bytes/issues/776)) - Fix latest clippy warnings ([#​787](https://redirect.github.com/tokio-rs/bytes/issues/787)) - Ignore `BytesMut::freeze` doctest on wasm ([#​790](https://redirect.github.com/tokio-rs/bytes/issues/790)) - Move `drop_fn` of `from_owner` into vtable ([#​801](https://redirect.github.com/tokio-rs/bytes/issues/801)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - "" in timezone America/New_York, Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- Release Notes: - N/A <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0Mi45NS4yIiwidXBkYXRlZEluVmVyIjoiNDIuOTUuMiIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS, Linux, and Windows you can download Zed directly or install Zed via your local package manager (macOS/Linux/Windows).
Other platforms are not yet available:
- Web (tracking issue)
Developing Zed
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
Licensing
License information for third party dependencies must be correctly provided for CI to pass.
We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:
- Is it showing a
no license specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.
Sponsorship
Zed is developed by Zed Industries, Inc., a for-profit company.
If you’d like to financially support the project, you can do so via GitHub Sponsors. Sponsorships go directly to Zed Industries and are used as general company revenue. There are no perks or entitlements associated with sponsorship.