@bensandee/tooling 0.65.0 → 0.66.0

package/dist/docker-check/index.mjs

@@ -1,2 +1,2 @@
-import { a as composeArgs, c as composePs, d as lintComposeFiles, i as getContainerHealth, l as composeUp, n as runDockerCheck, o as composeDown, r as checkHttpHealth, s as composeLogs, t as deriveProjectName, u as createRealExecutor } from "../project-name-CnyTIy5a.mjs";
+import { a as composeArgs, c as composePs, d as lintComposeFiles, i as getContainerHealth, l as composeUp, n as runDockerCheck, o as composeDown, r as checkHttpHealth, s as composeLogs, t as deriveProjectName, u as createRealExecutor } from "../project-name-CNaAmafB.mjs";
 export { checkHttpHealth, composeArgs, composeDown, composeLogs, composePs, composeUp, createRealExecutor, deriveProjectName, getContainerHealth, lintComposeFiles, runDockerCheck };

package/dist/{project-name-CnyTIy5a.mjs → project-name-CNaAmafB.mjs}

@@ -29,6 +29,32 @@ function debugExec(config, label, result) {
 	debugOut(lines.join("\n"));
 }
 //#endregion
+//#region src/docker-check/compose-yaml.ts
+/**
+* Parse a Docker Compose file as plain data.
+*
+* Compose defines its own merge tags — `!reset` and `!override` — which control how
+* values combine across layered `-f` files, and they may tag a scalar, a map or a
+* sequence (`ipam: !reset null`, `ports: !override [...]`). `yaml` doesn't know them,
+* and for an unknown tag it does not throw: it calls `process.emitWarning()` with code
+* `TAG_RESOLVE_FAILED` and then falls back to the default schema. That warning reached
+* every `bst repo:sync --check` and `bst docker:check` run in any repo whose overlay
+* used a merge tag — noise in every CI log, from a file bst went looking for itself.
+*
+* `logLevel: "silent"` suppresses those non-fatal warnings. It does not weaken parsing:
+* genuine syntax errors still throw, and a tagged value still resolves to its underlying
+* data. Callers here only read compose as data (service names, images, ports,
+* healthchecks, the top-level `name:`) and never re-serialize it, so the tag semantics
+* are irrelevant to them — which is why silencing beats registering the tags, whose
+* scalar/map/seq forms would need a six-entry matrix to model correctly.
+*
+* Do not drop the option; `test/docker-check/detect.test.ts` and `compose-lint.test.ts`
+* pin it by asserting no process warning is emitted.
+*/
+function parseComposeYaml(content) {
+	return parse(content, { logLevel: "silent" });
+}
+//#endregion
 //#region src/docker-check/compose-lint.ts
 const ComposeFileShape = z.looseObject({ name: z.unknown().optional() });
 /**
@@ -160,7 +186,7 @@ function readTopLevelName(absPath) {
 	}
 	let yamlValue;
 	try {
-		yamlValue = parse(raw);
+		yamlValue = parseComposeYaml(raw);
 	} catch (_error) {
 		return;
 	}
@@ -583,4 +609,4 @@ function sanitize(name) {
 	return name.replace(/^@[^/]+\//, "").toLowerCase().replace(/[^a-z0-9_-]+/g, "-").replace(/^-+|-+$/g, "") || "repo";
 }
 //#endregion
-export { composeArgs as a, composePs as c, lintComposeFiles as d, debug as f, redact as h, getContainerHealth as i, composeUp as l, isEnvVerbose as m, runDockerCheck as n, composeDown as o, debugExec as p, checkHttpHealth as r, composeLogs as s, deriveProjectName as t, createRealExecutor as u };
+export { composeArgs as a, composePs as c, lintComposeFiles as d, parseComposeYaml as f, redact as g, isEnvVerbose as h, getContainerHealth as i, composeUp as l, debugExec as m, runDockerCheck as n, composeDown as o, debug as p, checkHttpHealth as r, composeLogs as s, deriveProjectName as t, createRealExecutor as u };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bensandee/tooling",
-  "version": "0.65.0",
+  "version": "0.66.0",
   "description": "CLI tool to bootstrap and maintain standardized TypeScript project tooling",
   "license": "MIT",
   "repository": {
@@ -56,7 +56,7 @@
     "prettier": "3.8.4",
     "release-it": "20.2.0",
     "tsdown": "0.22.3",
-    "@bensandee/claude-hooks": "0.9.0"
+    "@bensandee/claude-hooks": "0.10.0"
   },
   "scripts": {
     "build": "tsdown",