Repository navigation
ci: bump cargo-affected and cargo-nextest pins - #4196
Merged
Merged
Conversation
cargo-affected 0.4.0 -> 0.4.1, cargo-nextest 0.9.144 -> 0.9.145.
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.
Weekly CI pin bump for the two third-party tool pins that drifted this week.
=0.4.0→=0.4.1—affected.yaml, both call sites=0.9.144→=0.9.145—coverage.yaml,.github/actions/test-setup/action.yaml,.github/actions/tend-setup/action.yaml, and.codex/cloud.sh, which the weekly checklist keeps level withtest-setupToolchain compatibility against the pinned
1.97.0:cargo-affected0.4.1 declaresrust-version = 1.94,cargo-nextest0.9.145 declares1.91. Both build underbaptiste0928/cargo-install. The.codex/cloud.shtarball URL resolves at the new version —cargo-nextest-0.9.145-x86_64-unknown-linux-gnu.tar.gzis published on thecargo-nextest-0.9.145tag.The
worktrunkpin also drifted this week and is in its own PR — it is thewtthat driveswt hook pre-mergeon all three platforms, so a red matrix there shouldn't hold back these two.What the two releases change, against this repo's config
cargo-affected 0.4.1 carries two
runfixes, both landing on the advisoryaffectedlegs: a committed uncovered change is now reported as uncovered rather than as "no changes" (max-sixty/cargo-affected#92), andrunno longer hands nextest a phantom-only filterset (#81).cargo-nextest 0.9.145's headline changes are profile-inheritance fixes — overrides defined in intermediate profiles are now applied, and a profile without
default-filterinherits from its nearest ancestor rather than always fromprofile.default. Those are no-ops here:.config/nextest.tomldefines onlyprofile.default(plus itsjunitsub-table), sets nodefault-filter, and CI passes no--tool-config-file.The change that does reach this suite is nextest-rs/nextest#3553: on Apple platforms, where the standard library can't create pipes with
FD_CLOEXECatomically, a concurrently-spawned test could inherit a sibling's capture pipe and the sibling was then reported as having leaked handles after exit. Nextest now creates capture pipes itself. That is a macOS-leg flake source removed, not a behavior change the suite has to absorb.