unstale

cargo / futures

futures

What changed in futures 0.3, from its official release notes, upgrade guides and advisories. Sources checked 2026-11-12.

1 breaking2 security3 deprecations5 new APIs and options1 performance2 behavior and defaults5 fixes and other

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

@unstale/cli 0.3.0 on npm

futures 0.319 changes

Breaking changes 1

  • The minimum supported Rust version for utility crates is now 1.71.

    0.3.32release notes

Security 2

  • Fixes an unsound Send implementation for Iter.

    0.3.33release notes

  • Fixes an unsound Send implementation for IterPinRef.

    0.3.33release notes

Deprecations 3

  • The pin_mut! macro is soft-deprecated in favor of std::pin::pin!.

    0.3.32release notes

  • The ready! macro is soft-deprecated in favor of std::task::ready!.

    0.3.32release notes

  • The mpsc receiver method try_next is deprecated.

    0.3.32release notes

New APIs and options 5

Performance 1

  • The release includes performance improvements.

    0.3.32release notes

Behavior and default changes 2

  • Mutex::new can now be called in a const context.

    0.3.32release notes

  • The shared functionality now supports no_std.

    0.3.32release notes

Fixes and other changes 5

  • Cloned wakers preserve their identity.

    0.3.34release notes

  • Fixes a stacked borrows violation in the compat01as03 implementation.

    0.3.33release notes

  • Fixes a memory leak in FuturesUnordered::IntoIter.

    0.3.33release notes

  • Fixes a soundness issue regarding exception safety in ReadLine.

    0.3.33release notes

  • sink::With now implements FusedStream.

    0.3.32release notes