Update Docker image to Rust 1.85.0 #89
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This makes cargo-deny runnable against projects with `edition = "2024"`, as only the latest Rust 1.85 understands the new edition without nightly feature flags.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This makes cargo-deny runnable against projects with
edition = "2024", as only the latest Rust 1.85 understands the new edition without nightly feature flags.Checklist
Description of Changes
Bumping the Docker image for the action to Rust 1.85.0 as base image.
Currently I'm in the process of updating several projects to Rust Edition 2024 and noticed that the
cargo-deny-actionfails due to not understanding the new edition yet (well it's not cargo-deny itself, but cargo from the base image).Related Issues
None.