Use v2 of the Cargo feature resolver and make CI work with it #1207
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
Tungstenite 0.17.1 has a higher MSRV, and there should be no reason to use it over 0.17.2.
|
Okay, looks like this can't be decoupled from #1205, closing. |
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.
Let's see whether this succeeds. Locally it seems to work. Split out from #1205.
The "Fix up Cargo.lock" step is only required as long as Cargo selects crc32fast 1.1.0, which I think has an invalid minimum version on its semver dependency (srijs/rust-crc32fast#27).