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

edition2024 errors since Rust 1.85 release #411

Closed
thedjinn opened this issue Feb 24, 2025 · 8 comments
Closed

edition2024 errors since Rust 1.85 release #411

thedjinn opened this issue Feb 24, 2025 · 8 comments

Comments

@thedjinn
Copy link

I have a project that is using the Rust 2021 edition. After Rust 1.85 was released cargo-outdated stopped working and produced the error I provided below. Note that I ran this on both Rust 1.84 and 1.85 and this did not change the outcome. It suggests that cargo-outdated is not compatible with crates on crates.io that use the new edition.

error: failed to download `munge_macro v0.4.2`

Caused by:
  unable to get packages from source

Caused by:
  failed to parse manifest at `/Users/redacted/.cargo/registry/src/index.crates.io-6f17d22bba15001f/munge_macro-0.4.2/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).
  Consider trying a more recent nightly release.
  See https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#edition-2024 for more information about the status of this feature.
@davidhewitt
Copy link
Collaborator

davidhewitt commented Feb 24, 2025

Sounds like we would need to bump our cargo dependency version (we use it as a library). A PR to help do this would be very welcome.

@thedjinn
Copy link
Author

Was going to look into this today, but another kind person beat me to it. This should address the issue: #410

Wenzel added a commit to Wenzel/tsffs that referenced this issue Mar 1, 2025
Wenzel added a commit to Wenzel/tsffs that referenced this issue Mar 1, 2025
@chuckliu1979
Copy link

any plan for new release to fix this ? i saw the fix already merged

@thedjinn
Copy link
Author

thedjinn commented Mar 3, 2025

If you need it before an official release is made you can always install the latest version from Git:

$ cargo install --locked --git https://github.com/kbknapp/cargo-outdated

I'm closing this issue because the merge for #410 solved the problem on my end. Thanks to all who were involved.

@thedjinn thedjinn closed this as completed Mar 3, 2025
Wenzel added a commit to Wenzel/tsffs that referenced this issue Mar 3, 2025
Wenzel added a commit to Wenzel/tsffs that referenced this issue Mar 4, 2025
@robjtede
Copy link

robjtede commented Mar 6, 2025

sorry for the bump @davidhewitt but pretty please can we get a cargo publish on this

@davidhewitt
Copy link
Collaborator

Yes, this is high on my list of things to do. I think likely is next week, sorry for the delay.

@kpcyrd
Copy link
Contributor

kpcyrd commented Mar 11, 2025

This is now fixed in Arch Linux' cargo-outdated-0.16.0-2-x86_64.pkg.tar.zst by patching the dependency tree downstream.

@davidhewitt
Copy link
Collaborator

Release now exists on GitHub and @kbknapp will hopefully push to crates.io shortly. 👍

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

No branches or pull requests

5 participants