Files
Anthony ShewandGitHub ebf49ac9b8 feat: Run the Rust workspace tests through nextest via command override (#13316)
PR 3 of the task `command` override series — the dogfood that motivated
the entire design.

> Unblocked: `2.10.5-canary.4` is published and knows the flag and
field; the pins in this PR reference it exactly.

## Why

The question that started all of this was "run `cargo nextest run`
instead of `cargo test`, without teaching turbo about nextest." This is
that, in 15 lines of configuration:

```jsonc
"turborepo-crates#test": {
  "command": ["cargo", "nextest", "run", "--workspace",
              "--exclude", "turborepo-lsp", "--exclude", "turborepo-schema-gen",
              "--exclude", "turborepo-napi", "--no-fail-fast"]
}
```

Turbo knows nothing about nextest. The excludes mirror today's CI
invocations exactly, and `.config/nextest.toml` is already a hashed
workspace input (cargo's `hash_input_globs`), so nextest config edits
invalidate cached test results.

## What

- `futureFlags.experimentalTaskCommand` enabled
- `turborepo-crates#test` command override (scoped — level 2 — replacing
the verb table's `cargo test --workspace`)
- Vercel canary pins bumped (`2.10.5-canary.4`, the real published
version)

## Verification

Locally with a branch-built turbo: `turbo run test
--filter=turborepo-crates --dry=json` resolves the command to the
literal argv and hashes it. This also unblocks the parked
CI-simplification step 4 (`turbo run test --filter=turborepo-crates` in
the rust CI jobs, replacing the raw nextest invocations).
2026-07-09 11:55:46 -06:00

4 lines
149 B
JSON

{
"installCommand": "pnpm install --filter=docs... && pnpm --workspace-root add --save-dev [email protected] --config.minimum-release-age=0"
}