@theokit/sdk-tools 0.27.1 → 0.27.3

package/CHANGELOG.md

@@ -1,5 +1,35 @@
 # Changelog
 
+## 0.27.3
+
+### Patch Changes
+
+- 09f3d05: Record that the vitest JSON-report contract `run_vitest` depends on was measured across majors 2, 3 and 4, rather than assumed.
+
+  The peer range is unbounded (`vitest >=2.0.0`) and the tool shells out to `npx --no-install vitest run --reporter=json`, reading four fields off the report's top level without validation. Nothing imports vitest, so no compiler notices a renamed field — the docblock warned about that risk and nobody had checked it.
+
+  Measured 2026-08-31: the same suite under 2.1.9, 3.2.7 and 4.1.11 emits `numTotalTests`, `numPassedTests`, `numFailedTests` and `success`, correctly, every time. Two majors above the declared floor are published and the promise holds.
+
+  Documentation only — no behaviour changes. The docblock now states what was checked, and that the observation expires when vitest 5 ships.
+
+## 0.27.2
+
+### Patch Changes
+
+- 1a4bbcf: The declared `@theokit/sdk` peer range stops promising a version the package does not compile against.
+
+  It declared `>=4.19.3` and fails at exactly that floor, with `error TS2552: Cannot find name`. npm
+  resolves the combination with no `ERESOLVE` and no peer warning, and the break surfaces in the build,
+  far from the range that caused it.
+
+  The real floor is `4.54.0`, measured by bisecting the 116 stable 4.x releases with a real build as the
+  oracle: `4.53.1` fails and `4.54.0` passes. They are adjacent in the published list, so this is the
+  exact version rather than an interval.
+
+  This package had been excluded from the sibling finding (usetheokit/theokit-sdk#423) for declaring a
+  narrower range than the other four. A narrower range can still be false — it is just false over a
+  smaller interval (usetheokit/theokit-sdk#425).
+
 ## 0.27.1
 
 ### Patch Changes