chore(CI): temporarily pin cargo-nextest to v0.9.61
#300
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
hawkw
changed the title
cargo-nextest to v0.9.61
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.
v0.9.63 of
cargo-nextestintroduced a regression (guppy-rs/guppy#157 (comment)) that breaks Nextest when a workspace includes a package with binary dependencies. This broke our CI builds.This PR temporarily pins the
cargo-nextestversion on CI to v0.9.61 (as v0.9.62 was yanked). Hopefully when this is fixed upstream, we can resume using the latest version.