@theholocron/cli 4.11.0 → 4.12.1

package/README.md

@@ -148,6 +148,14 @@ sub-job whose tool isn't installed, or that has no local equivalent
 a task with no sub-jobs the `job` slot is the first passthrough arg
 (`holocron run build src/`).
 
+**CI runs the identical command.** The reusable `typecheck` / `test` / `audit`
+workflows call the `holocron` composite action
+(`theholocron/.github/.github/actions/holocron@main`), whose body is
+`holocron run <task> [job]`. So `holocron run test` locally and the `Test` CI
+job execute the same thing — at a turbo root both are
+`turbo run test -- --coverage` (the registry's org-default flags flow through
+turbo's `--`).
+
 ### `holocron ci`
 
 ```bash

package/dist/cli.mjs

@@ -3451,7 +3451,6 @@ function createConfig$3() {
 //#endregion
 //#region src/templates/configs/editorconfig-checker/editorconfig-checker.json
 var editorconfig_checker_default = {
-	Version: "v3.7.0",
 	Verbose: false,
 	Format: "",
 	Debug: false,
@@ -3477,6 +3476,17 @@ var editorconfig_checker_default = {
 };
 //#endregion
 //#region src/templates/configs/editorconfig-checker/create-config.ts
+/**
+* The generated `.editorconfig-checker.json`.
+*
+* Deliberately carries no `"Version"` key: editorconfig-checker treats it as a
+* hard gate and exits non-zero the moment the running binary's version differs
+* — which it does the instant a contributor's local install (Homebrew tracks
+* latest) drifts from the version super-linter bundles in CI, breaking
+* `holocron run lint` / the pre-push hook for everyone (#618). The config
+* options here (`Exclude`, `Disable`) are stable across releases, so pinning
+* buys nothing.
+*/
 function createConfig$2() {
 	return JSON.stringify(editorconfig_checker_default, null, 2) + "\n";
 }