@antelopejs/tooling-configs 0.3.6 → 0.3.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/bin/sync.mjs +8 -4
- package/dist/bin/verify.mjs +686 -411
- package/dist/{map-CiFEGFRz.mjs → map-B23_WMGE.mjs} +91 -9
- package/package.json +2 -1
package/dist/bin/sync.mjs
CHANGED
|
@@ -8,7 +8,7 @@ import { a as gitFiles, c as repositoryRoot } from "../files-DJ0TeaTU.mjs";
|
|
|
8
8
|
import { i as recordedRelease, t as measureBaseline } from "../ratchet-Q-JXuZIX.mjs";
|
|
9
9
|
import { a as ciWorkflow, c as ciNodeCallers, l as ciRenovateSyncCallers, o as placeholderTestScript, p as renovateArtifacts, r as CI_PATH, s as MISSING_CHECKS_WORKFLOW, u as hasChecksWorkflow } from "../ci-workflow-37qJa9LX.mjs";
|
|
10
10
|
import { n as SUPPRESSIONS_FILE, r as adoptedBudget } from "../suppression-budget-C0SkPO5R.mjs";
|
|
11
|
-
import { t as DEFAULT_SHARED } from "../map-
|
|
11
|
+
import { t as DEFAULT_SHARED } from "../map-B23_WMGE.mjs";
|
|
12
12
|
import { chmodSync, existsSync, lstatSync, mkdirSync, readFileSync, readdirSync, readlinkSync, rmdirSync, statSync, symlinkSync, unlinkSync, writeFileSync } from "node:fs";
|
|
13
13
|
import { dirname, join, posix, resolve } from "node:path";
|
|
14
14
|
import { execFileSync } from "node:child_process";
|
|
@@ -1269,11 +1269,15 @@ ${BIN} plan --base origin/main
|
|
|
1269
1269
|
${BIN} journey <run> --plan
|
|
1270
1270
|
\`\`\`
|
|
1271
1271
|
|
|
1272
|
-
\`plan\` maps the diff to features and lists unmapped surfaces. \`journey <run> --plan\` runs every feature \`plan\` lists as \`run\` for the run's base, \`smoke\` first, in one call: it prints each feature's lines in turn, keeps going after a feature fails, and exits 1 when any journey did not pass.
|
|
1272
|
+
\`plan\` maps the diff to features and lists unmapped surfaces. \`journey <run> --plan\` runs every feature \`plan\` lists as \`run\` for the run's base, \`smoke\` first, in one call: it prints each feature's lines in turn, keeps going after a feature fails, and exits 1 when any journey did not pass. Run it once instead of one call per feature.
|
|
1273
|
+
|
|
1274
|
+
Features run one after another by default. When verify.config.ts declares no \`services\`, use \`--jobs 4\` when the machine is otherwise idle (load below the core count); otherwise run sequentially. \`--jobs\` runs up to that many features at once, each in a process of its own, capped at half the machine's cores; it finishes sooner but costs about twice the CPU time. The output, the evidence and the exit code are those of the sequential call, and a feature that lists a journey an earlier feature lists waits for it, so it still reuses that PASS. A feature whose process dies or leaves an uncaught error is named on stderr, and the others still run. On an interrupt, a feature's process that has not stopped 5 s later, or at a second interrupt, is killed with the apps it started; the call prints every feature that ended and names the rest in \`not run: <features>\`. \`--jobs\` above 1 is refused when verify.config.ts declares \`services\`, because each journey resets them as it starts, which would wipe the data of a journey running beside it. Without \`--jobs\`, a journey that leaves an uncaught error behind ends the call and the line \`not run: <features>\` names what to rerun.
|
|
1275
|
+
|
|
1276
|
+
To rerun after a fix, run one feature, or only the journeys you name, or several features by name, with \`--jobs\` too:
|
|
1273
1277
|
|
|
1274
1278
|
\`\`\`bash
|
|
1275
1279
|
${BIN} journey <run> <feature> [journey...]
|
|
1276
|
-
${BIN} journey <run> --features <feature>,<feature>
|
|
1280
|
+
${BIN} journey <run> --features <feature>,<feature> [--jobs 4]
|
|
1277
1281
|
\`\`\`
|
|
1278
1282
|
|
|
1279
1283
|
The pack ships these journeys for this kind; a feature file names them next to the repository's own:
|
|
@@ -1317,7 +1321,7 @@ ${BIN} map
|
|
|
1317
1321
|
4. **Docs.** Judge every page \`plan\` lists as \`docs\` against what the journeys showed: the \`docs:\` pages of the touched features, or of every feature when the full set runs. A stale page fails the verdict.
|
|
1318
1322
|
5. **Formal checks.** \`${BIN} formal <run>\` runs every formal check of \`verify.config.ts\` that covers the diff, or whose own \`files\` the diff changes, and records it under \`evidence/formal/<name>/\`. For each one it decides, without judgement, whether the diff changed what the covered code does. \`emit\` (the default) compares the structure of the covered files' JavaScript on the base and on HEAD: node kinds, names and literal values, leaving out types, comments, formatting, parentheses and \`export\` keywords. Each use of an imported binding stands for its origin (the resolved module and the imported name), so an import retargeted to another module or alias counts as changed; a function declaration refers to the top-level variables and classes of its own file by file and name, so moving it next to a different variable of the same name counts as changed. Exports are keyed by the origin they export, so a re-export or an \`export { f as run }\` retargeted to another binding counts as changed. Each file must keep its top-level statements and its side-effect imports in order; function declarations, which are hoisted, may move between covered files with their imports. So a type-only edit, a reformat or a moved function declaration counts as unchanged, while reordering statements or moving any other statement counts as changed. \`emit\` judges behaviour, not the public surface: exports are the api-diff's job. \`probe\` runs the check's \`behaviour.command\` with a worktree of each commit and compares what it prints. Then:
|
|
1319
1323
|
- a covered check that did not run, or exits non-zero (a tool error, or a check that no longer matches its record), fails the verdict;
|
|
1320
|
-
- when the covered behaviour did not change, the verdict reports recorded findings as known findings;
|
|
1324
|
+
- when the covered behaviour did not change, the verdict reports recorded findings as known findings, except a rule HEAD breaks that the base run did not, which fails the verdict whatever the diff touched, the check's own \`files\` included; when the base run itself exited non-zero, HEAD's findings cannot be compared and fail the verdict, and so does a result whose check's own \`files\` changed with no base run recorded. A check the diff adds is the exception: when the base could not run it, the base's \`verify.config.ts\` never names it, none of its files is a git rename of a base file, and the covered behaviour is unchanged, its recorded findings pass as the record it brings. List those findings in the PR body so a reviewer sees what the record accepts. A new check on a diff that also changes the covered code fails with \`new check with a covered-code change: land the check in its own PR first\`: land the check alone, then the code change. A moved or renamed check is a changed check;
|
|
1321
1325
|
- when the covered behaviour changed, or the diff changed the check's own \`files\`, \`formal\` also runs the check on the base (\`baseCommand\` when set). A rule the base broke counts as fixed only when HEAD reports it passing (\`passing\`); a rule the base broke that HEAD does not report at all fails the verdict. A change that leaves no violated rule passes;
|
|
1322
1326
|
- when the covered behaviour changed, recorded findings fail the verdict unless the base run exited 0 and broke each of them with the same counterexample length (the \`states\` named group of \`violation\`, after the rule's group, in decimal digits; a \`states\` group that is the first group or captures anything else gives no length), and HEAD fixed every other rule the base broke; then the verdict reports them as the same known findings as the base, with the fixed ones. A new rule, a changed length, or a length either run did not print fails.
|
|
1323
1327
|
|