Skip to content

Workaround for Cargo error: feature edition2024 is required; caused by bluez-async v0.8.1 migration to Rust 2024 edition #440

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

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

Conversation

NuLL3rr0r
Copy link
Contributor

When building:

  Downloaded bluez-async v0.8.1
error: failed to parse manifest at `/home/mamadou/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bluez-async-0.8.1/Cargo.toml`

Caused by:
  feature `edition2024` is required

  The package requires the Cargo feature called `edition2024`, but that feature is not stabilized in this version of Cargo (1.83.0 (5ffbef321 2024-10-29)).
  Consider trying a newer version of Cargo (this may require the nightly release).
  See https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#edition-2024 for more information about the status of this feature.

Locking bluez-async to v0.8.0 works around the issue.

…uez-async v0.8.1 migration to rust 2024 edition
@NuLL3rr0r NuLL3rr0r changed the title Workaround for Cargo error: feature edition2024 is required; caused by bluez-async v0.8.1 migration to rust 2024 edition Workaround for Cargo error: feature edition2024 is required; caused by bluez-async v0.8.1 migration to Rust 2024 edition Jul 2, 2025
@NuLL3rr0r
Copy link
Contributor Author

Though, I have to mention it builds fine against a newer Rust, but in projects stuck with older Rust versions this causes a build failure.

@qwandor
Copy link
Collaborator

qwandor commented Jul 2, 2025

I don't think this workaround belongs in btleplug, you can keep using an old version via your Cargo.lock file.

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.

2 participants