Skip to content

Update rust-futures monorepo to 0.3.32#580

Open
nextest-bot wants to merge 1 commit into
mainfrom
renovate/rust-futures-monorepo
Open

Update rust-futures monorepo to 0.3.32#580
nextest-bot wants to merge 1 commit into
mainfrom
renovate/rust-futures-monorepo

Conversation

@nextest-bot

@nextest-bot nextest-bot commented Jun 26, 2026

Copy link
Copy Markdown
Collaborator

This PR contains the following updates:

Package Type Update Change Pending
futures (source) dev-dependencies patch 0.3.310.3.32 0.3.33
futures-util (source) dependencies patch 0.3.310.3.32 0.3.33

Release Notes

rust-lang/futures-rs (futures)

v0.3.32

Compare Source

  • Bump MSRV of utility crates to 1.71. (#​2989)
  • Soft-deprecate ready! macro in favor of std::task::ready! added in Rust 1.64 (#​2925)
  • Soft-deprecate pin_mut! macro in favor of std::pin::pin! added in Rust 1.68 (#​2929)
  • Add FuturesOrdered::clear (#​2927)
  • Add mpsc::*Receiver::recv (#​2947)
  • Add mpsc::*Receiver::try_recv and deprecate mpsc::*Receiver::::try_next (#​2944)
  • Implement FusedStream for sink::With (#​2948)
  • Add no_std support for shared (#​2868)
  • Make Mutex::new() const (#​2956)
  • Add #[clippy::has_significant_drop] to guards (#​2967)
  • Remove dependency to pin-utils (#​2929)
  • Remove dependency on num_cpus (#​2946)
  • Performance improvements (#​2983)
  • Documentation improvements (#​2925, #​2926, #​2940, #​2971)

Configuration

📅 Schedule: (in timezone America/Los_Angeles)

  • Branch creation
    • "after 8pm,before 6am"
  • Automerge
    • "after 8pm,before 6am"

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


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

This PR has been generated by Mend Renovate.

@nextest-bot nextest-bot added the dependencies Dependency-related updates label Jun 26, 2026
@nextest-bot
nextest-bot force-pushed the renovate/rust-futures-monorepo branch 5 times, most recently from a0c4122 to c90ae10 Compare July 1, 2026 08:58
@nextest-bot
nextest-bot force-pushed the renovate/rust-futures-monorepo branch 5 times, most recently from f8b5b2d to 3f000d7 Compare July 11, 2026 07:22
@nextest-bot
nextest-bot force-pushed the renovate/rust-futures-monorepo branch 3 times, most recently from b726b14 to 0dac168 Compare July 18, 2026 06:02
@nextest-bot
nextest-bot force-pushed the renovate/rust-futures-monorepo branch from 0dac168 to 63c2dcc Compare July 21, 2026 07:13
@nextest-bot

Copy link
Copy Markdown
Collaborator Author

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.toml
Artifact update for futures-util resolved to version 0.3.33, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 0.3.32
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: Cargo.toml
Artifact update for futures resolved to version 0.3.33, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 0.3.32
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/

@nextest-bot
nextest-bot force-pushed the renovate/rust-futures-monorepo branch 2 times, most recently from c93289f to 070162f Compare July 23, 2026 04:34
@nextest-bot
nextest-bot force-pushed the renovate/rust-futures-monorepo branch from 070162f to bea746a Compare July 24, 2026 06:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Dependency-related updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant