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 futures to v0.3.31 #49

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 31, 2023

This PR contains the following updates:

Package Type Update Change
futures (source) dependencies patch 0.3.27 -> 0.3.31

Release Notes

rust-lang/futures-rs (futures)

v0.3.31

Compare Source

  • Fix use after free of task in FuturesUnordered when dropped future panics (#​2886)
  • Fix soundness bug in task::waker_ref (#​2830)
    This is a breaking change but allowed because it is soundness bug fix.
  • Fix bugs in AsyncBufRead::read_line and AsyncBufReadExt::lines (#​2884)
  • Fix parsing issue in select!/select_biased! (#​2832)
    This is technically a breaking change as it will now reject a very odd undocumented syntax that was previously accidentally accepted.
  • Work around issue due to upstream Waker::will_wake change (#​2865)
  • Add stream::Iter::{get_ref,get_mut,into_inner} (#​2875)
  • Add future::AlwaysReady (#​2825)
  • Relax trait bound on non-constructor methods of io::{BufReader,BufWriter} (#​2848)

v0.3.30

Compare Source

Note: This release of futures-util has been yanked due to a bug fixed in 0.3.31 and a compile failure with futures-task 0.3.31 and later.

  • Add {BiLock,SplitStream,SplitSink,ReadHalf,WriteHalf}::is_pair_of (#​2797)
  • Fix panic in FuturesUnordered::clear (#​2809)
  • Fix panic in AsyncBufReadExt::fill_buf (#​2801, #​2812)
  • Improve support for targets without atomic CAS (#​2811)
  • Remove build scripts (#​2811)

v0.3.29

Compare Source

Note: This release of futures-util has been yanked due to a bug fixed in 0.3.31 and a compile failure with futures-task 0.3.31 and later.

  • Add TryStreamExt::try_ready_chunks (#​2757)
  • Add TryStreamExt::{try_all,try_any} (#​2783)
  • Add UnboundedSender::{len,is_empty} (#​2750)
  • Fix Sync impl of FuturesUnordered (#​2788)
  • Fix infinite loop caused by invalid UTF-8 bytes (#​2785)
  • Fix build error with -Z minimal-versions (#​2761)

v0.3.28

Compare Source

Note: This release of futures-util has been yanked due to a bug fixed in 0.3.31 and a compile failure with futures-task 0.3.31 and later.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 futures to 0.3.28 Update Rust crate futures to 0.3.29 Oct 26, 2023
@renovate renovate bot force-pushed the renovate/rust-futures-monorepo branch from 61c8847 to d386458 Compare October 26, 2023 17:09
@renovate renovate bot changed the title Update Rust crate futures to 0.3.29 Update Rust crate futures to 0.3.30 Dec 24, 2023
@renovate renovate bot force-pushed the renovate/rust-futures-monorepo branch from d386458 to 1427af3 Compare December 24, 2023 16:46
@renovate renovate bot changed the title Update Rust crate futures to 0.3.30 Update Rust crate futures to v0.3.30 May 5, 2024
@renovate renovate bot force-pushed the renovate/rust-futures-monorepo branch from 1427af3 to 7f46a45 Compare October 5, 2024 12:31
@renovate renovate bot changed the title Update Rust crate futures to v0.3.30 Update Rust crate futures to v0.3.31 Oct 5, 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