Clean up Cargo workspace warnings#51
Open
georgephillips wants to merge 2 commits intomainfrom
Open
Conversation
…d enhanced error logging. Updated BrowserWindow structure to include context ID and browser reference.
This file contains hidden or 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
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.
Summary
resolver = "2"on the workspace root to match the edition 2021 default and silence the resolver version warning.[profile.dev.package.similar]fromtoolproof/Cargo.tomlto the workspace rootCargo.toml, where Cargo actually reads profile configuration.Context
Running
cargo buildproduced two warnings on every build:resolver = "1"despite one or more workspace members being on edition 2021 which impliesresolver = "2"" -- The workspace root didn't specify a resolver, so Cargo defaulted to v1 despite the member crate using edition 2021.[profile.dev.package.similar]section in the member crate'sCargo.tomlwas silently ignored; profile overrides must live in the workspace root.