@theokit/sdk-tools 0.27.2 → 0.27.3
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/CHANGELOG.md +12 -0
- package/dist/index.cjs.map +1 -1
- package/dist/index.d.cts +11 -0
- package/dist/index.d.ts +11 -0
- package/dist/index.js.map +1 -1
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,17 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.27.3
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- 09f3d05: Record that the vitest JSON-report contract `run_vitest` depends on was measured across majors 2, 3 and 4, rather than assumed.
|
|
8
|
+
|
|
9
|
+
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.
|
|
10
|
+
|
|
11
|
+
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.
|
|
12
|
+
|
|
13
|
+
Documentation only — no behaviour changes. The docblock now states what was checked, and that the observation expires when vitest 5 ships.
|
|
14
|
+
|
|
3
15
|
## 0.27.2
|
|
4
16
|
|
|
5
17
|
### Patch Changes
|