Update Rust crate futures-util to 0.3.29 - abandoned #8
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/futures-util-0.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
0.3.21
->0.3.29
Release Notes
rust-lang/futures-rs (futures-util)
v0.3.29
Compare Source
TryStreamExt::try_ready_chunks
(#2757)TryStreamExt::{try_all,try_any}
(#2783)UnboundedSender::{len,is_empty}
(#2750)Sync
impl ofFuturesUnordered
(#2788)v0.3.28
Compare Source
FlattenUnordered
(#2726, #2728)v0.3.27
Compare Source
TryFlattenUnordered
(#2577, #2590, #2606, #2607)AbortHandle::is_aborted
(#2710)AbortRegistration::handle
(#2712)BiLock
strict-provenance compatible (#2716)v0.3.26
Compare Source
Either::as_pin_mut
andEither::as_pin_ref
(#2691)Shared::ptr_eq
andShared::ptr_hash
(#2691)FusedStream
forBuffered
(#2676)FusedStream
for all streams inReadyChunks
(#2693)FuturesOrdered::push_front
(#2664)Fut::Output: Clone
bounds from someShared
methods (#2662)T: Debug
bounds fromDebug
implementations ofmpsc
andoneshot
types (#2666, #2667)v0.3.25
Compare Source
join!
andtry_join!
macros (#2649)Clone
forsink::Drain
(#2650)v0.3.24
Compare Source
select_with_strategy
streams (#2635)v0.3.23
Compare Source
v0.3.22
Compare Source
Sync
impl ofBiLockGuard
(#2570)FuturesUnordered
(#2574)Shared
(#2576)Mutex::lock_owned
andMutex::try_lock_owned
(#2571)io::copy_buf_abortable
(#2507)Unpin
bound fromTryStreamExt::into_async_read
(#2599)run_until_stalled
handle self-waking futures (#2593)FuturesOrdered
intry_join_all
(#2556)LocalPool
waker (#2608)stream::Chunk
adapters size hints (#2611)push_front
andpush_back
toFuturesOrdered
(#2591)FuturesOrdered::push
in favor ofFuturesOrdered::push_back
(#2591)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.
This PR has been generated by Renovate Bot.
Update Rust crate futures-util to 0.3.23to Update Rust crate futures-util to 0.3.2473ae5888d5
to8fafb931f2
Update Rust crate futures-util to 0.3.24to Update Rust crate futures-util to 0.3.258fafb931f2
toab99268914
ab99268914
to0ea8651f76
Update Rust crate futures-util to 0.3.25to Update Rust crate futures-util to 0.3.26Update Rust crate futures-util to 0.3.26to Update Rust crate futures-util to 0.3.280ea8651f76
tod891b8fc18
Update Rust crate futures-util to 0.3.28to Update Rust crate futures-util to 0.3.29d891b8fc18
to21fead4ee0
Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.
Update Rust crate futures-util to 0.3.29to Update Rust crate futures-util to 0.3.29 - abandonedAutoclosing Skipped
This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.
Pull request closed