From ee3e627efb2992f3c1405a979006fc4b9f571c28 Mon Sep 17 00:00:00 2001 From: gensokyo-dev Date: Sat, 14 Nov 2026 09:08:42 +0000 Subject: [PATCH] docs(ci): describe CI lanes without counts that drift The testing guides stated lane and shard counts in prose. The counts drifted when the workflow changed: "all eight fast built shards" survived the move to twelve, "Eight Linux real-system lanes" now covers twelve workflow calls, and the SQLite guide named a Node 24.15.0 lane that the matrix no longer runs. Describe each set by its selector and point at the workflow that owns the exact versions, so later workflow changes cannot make the text wrong. Fixes #7616 Fixes #7617 Co-Authored-By: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com> Co-Authored-By: Claude Opus 5.5 --- docs/development/testing.md | 4 ++-- docs/guides/data/sqlite-databases.md | 7 ++++--- docs/testing-lanes.md | 2 +- 3 files changed, 7 insertions(+), 6 deletions(-) diff --git a/docs/development/testing.md b/docs/development/testing.md index e7ead9ae85..d165518f79 100644 --- a/docs/development/testing.md +++ b/docs/development/testing.md @@ -1130,8 +1130,8 @@ memory usage, or billing. Step names identify samples, not complete transfer costs. Its queue, execution, and failures are independent of the required gate and publication. CPU time and peak process-family memory are not measured by this API. -The build job saves portable Turbo outputs across runs. Eight Linux real-system -lanes reuse its current-run artifact; standalone dispatches restore the cross-run cache. The shared action +The build job saves portable Turbo outputs across runs. Linux real-system lanes +that pass `build_cache_artifact` reuse its current-run artifact; standalone dispatches restore the cross-run cache. The shared action derives its key from `test:prepare --dry=json` task hashes, runner OS and architecture, `.npmrc`, `.nvmrc`, and the lockfile; test-only changes can reuse compiled outputs. Every build and verification command still runs, so Turbo checks task inputs and diff --git a/docs/guides/data/sqlite-databases.md b/docs/guides/data/sqlite-databases.md index 184b7a56a5..dfdb311e47 100644 --- a/docs/guides/data/sqlite-databases.md +++ b/docs/guides/data/sqlite-databases.md @@ -216,9 +216,10 @@ tests automatically. `npm run test:sqlite:run` runs the same cases when the compiled runtime and generated test artifacts are already current. The reusable SQLite CI workflow consumes the shared build artifact and tests -the latest Node 22.x unavailable-runtime diagnostics, the minimum supported -24.15.0 release, and the latest 24.x and 26.x releases. The repository-pinned -runtime also runs the full suite. CI's required gate waits for every selected +Node 22.x unavailable-runtime diagnostics, the repository-pinned 24.x release, +and the latest 24.x and 26.x releases; `.github/workflows/sqlite-runtime.yml` +owns the exact versions. The repository-pinned runtime also runs the full +suite. CI's required gate waits for every selected SQLite matrix job; a failed, cancelled, skipped or missing selected lane blocks the gate. Workflow changes themselves select the build and compatibility lane. diff --git a/docs/testing-lanes.md b/docs/testing-lanes.md index 6cc436529a..f02c0ea894 100644 --- a/docs/testing-lanes.md +++ b/docs/testing-lanes.md @@ -739,7 +739,7 @@ push: changes from failed or cancelled intermediate runs remain in scope. Missing, untrusted, or non-ancestor history selects the fast Linux x64 baseline: portable checks and the Linux runtime lane. The lookup is bounded to the last 100 successful push runs; lookup failures broaden selection. -Every code change still selects the source group and all eight fast built shards, without coverage +Every code change still selects the source group and every fast built shard, without coverage instrumentation in this fast tier. Ordinary PR matrices cancel remaining shards after the first failure; passing PRs execute the complete suite. Main, `ci:full`, scheduled, manual, and release qualification retain every shard's