Omit serde/serde_json from lockfiles not using cargo_metadata #79
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
Pull Request Test Coverage Report for Build 12592025062Details
💛 - Coveralls |
auto-merge was automatically disabled
January 3, 2025 02:57
Head branch was pushed to by a user without write access
dtolnay
added a commit
to dtolnay/cargo-llvm-lines
that referenced
this pull request
Jan 5, 2025
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 will work just as well for forcing a good minimal version when clap-cargo's "cargo_metadata" feature is enabled, but it keeps
serdeandserde_jsonanditoaandmemchrandryuandserde_deriveout of downstream Cargo.lock that wouldn't otherwise need them.