fix(ci): install cargo-nextest via taiki-e/install-action - #113
Merged
Conversation
moonrepo/setup-rust falls back to `cargo install cargo-nextest` (without --locked) when its binstall fetch fails, which nextest rejects at compile time via the locked-tripwire guard. Use taiki-e/install-action, which fetches prebuilt binaries directly and does not hit this fallback path.
github-actions
Bot
added
needs-review
bug-ops
enabled auto-merge (squash)
August 12, 2026 21:50
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
1 participant
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
testandcoveragejobs installedcargo-nextest(andcargo-llvm-cov) viamoonrepo/setup-rust'sbins:input, which uses cargo-binstall and silently falls back tocargo install <tool>(without--locked) when the binstall fetch fails.locked-tripwirebuild guard rejects unlocked source installs at compile time, so any transient binstall network failure (as seen on windows-latest in run 31642553967) turns into a hard CI failure instead of a retry.taiki-e/install-action, already used elsewhere in this workflow (cargo-deny,cross), which fetches prebuilt binaries directly and does not hit this fallback path.Test plan
testmatrix (ubuntu/macos/windows) andcoveragejob