Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Rust crate bytes to v1.8.0 #31

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 17, 2024

This PR contains the following updates:

Package Type Update Change
bytes dependencies minor 1.6.0 -> 1.8.0

Release Notes

tokio-rs/bytes (bytes)

v1.8.0

Compare Source

  • Guarantee address in split_off/split_to for empty slices (#​740)

v1.7.2

Compare Source

Fixed
  • Fix default impl of Buf::{get_int, get_int_le} (#​732)
Documented
  • Fix double spaces in comments and doc comments (#​731)
Internal changes
  • Ensure BytesMut::advance reduces capacity (#​728)

v1.7.1

Compare Source

This release reverts the following change due to a regression:

  • Reuse capacity when possible in <BytesMut as Buf>::advance impl (#​698)

The revert can be found at #​726.

v1.7.0

Compare Source

Added
  • Add conversion from Bytes to BytesMut (#​695, #​710)
  • Add reclaim method without additional allocation (#​686)
Documented
  • Clarify how BytesMut::zeroed works (#​714)
  • Clarify the behavior of Buf::chunk (#​717)
Changed
  • Change length condition of BytesMut::truncate
  • Reuse capacity when possible in <BytesMut as Buf>::advance impl (#​698)
  • Improve must_use suggestion of BytesMut::split (#​699)
Internal changes
  • Use ManuallyDrop instead of mem::forget (#​678)
  • Don't set len in BytesMut::reserve (#​682)
  • Optimize Bytes::copy_to_bytes (#​688)
  • Refactor BytesMut::truncate (#​694)
  • Refactor BytesMut::resize (#​696)
  • Reorder assertion in Bytes::split_to, Bytes::split_off (#​689, #​693)
  • Use offset_from in more places (#​705)
  • Correct the wrong usage of IntoIter (#​707)

v1.6.1

Compare Source

This release fixes a bug where Bytes::is_unique returns incorrect values when
the Bytes originates from a shared BytesMut. (#​718)


Configuration

📅 Schedule: Branch creation - "* 0-4 * * 3" (UTC), 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title Update Rust crate bytes to v1.6.1 Update Rust crate bytes to v1.7.0 Jul 31, 2024
@renovate renovate bot force-pushed the renovate/bytes-1.x-lockfile branch from f76494b to 6ca23a8 Compare July 31, 2024 13:13
@renovate renovate bot changed the title Update Rust crate bytes to v1.7.0 Update Rust crate bytes to v1.7.1 Aug 1, 2024
@renovate renovate bot force-pushed the renovate/bytes-1.x-lockfile branch from 6ca23a8 to 0b08a98 Compare August 1, 2024 22:40
@renovate renovate bot changed the title Update Rust crate bytes to v1.7.1 Update Rust crate bytes to v1.7.2 Sep 18, 2024
@renovate renovate bot force-pushed the renovate/bytes-1.x-lockfile branch from 0b08a98 to 5a7f663 Compare September 18, 2024 08:33
@renovate renovate bot force-pushed the renovate/bytes-1.x-lockfile branch from 5a7f663 to ee9f70b Compare October 21, 2024 22:21
@renovate renovate bot changed the title Update Rust crate bytes to v1.7.2 Update Rust crate bytes to v1.8.0 Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants