@zerotal/arch 1.14.1 → 1.14.2
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/docs/changelog.md +33 -0
- package/package.json +3 -3
package/docs/changelog.md
CHANGED
|
@@ -27,6 +27,39 @@ the section for every version you cross and apply its migration notes, not only
|
|
|
27
27
|
majors. [Releases and versioning](/docs/support-policy#releases-and-versioning) explains
|
|
28
28
|
when that carve-out ends.
|
|
29
29
|
|
|
30
|
+
## 1.14.2 — 2026-09-01
|
|
31
|
+
|
|
32
|
+
**`bun run dev` was broken in every app scaffolded since 1.13.0.** Take this one.
|
|
33
|
+
|
|
34
|
+
Found by starting the adoption release the obvious way — scaffolding a fresh app and
|
|
35
|
+
walking the first-run path as a newcomer would, rather than reasoning about it.
|
|
36
|
+
|
|
37
|
+
### Fixed
|
|
38
|
+
|
|
39
|
+
- **The scaffold templates shipped a retired command.** Every template's `package.json`
|
|
40
|
+
carried `"dev": "bun zt.ts serve --dev"`, and `serve --dev` was retired in
|
|
41
|
+
[1.13.0](#1130--2026-08-31) — deliberately failing loudly rather than silently starting a
|
|
42
|
+
plain server with no watcher. So the first command a new user runs exited 1 and told them
|
|
43
|
+
to use something else.
|
|
44
|
+
|
|
45
|
+
Retiring an alias meant updating the runner, the documentation and the `zt upgrade`
|
|
46
|
+
codemod. It did not occur to me to update the thing that _writes new apps_, which is the
|
|
47
|
+
one place a retired form is guaranteed to keep appearing.
|
|
48
|
+
|
|
49
|
+
A test now checks the scaffolder against the codemod's own list of retired forms, so what
|
|
50
|
+
generates apps cannot fall behind what migrates them. It is driven by the codemod rather
|
|
51
|
+
than a second list, because two lists disagree.
|
|
52
|
+
|
|
53
|
+
- **`zt upgrade` did not rewrite `zt.ts serve --dev` either.** The codemod anchored on `zt`
|
|
54
|
+
followed by whitespace, matching `zt serve --dev` and missing `bun zt.ts serve --dev` —
|
|
55
|
+
the form in every scaffolded `package.json`. So an app running `zt upgrade` to migrate off
|
|
56
|
+
the alias was told there was nothing to do, on the file that needed it most.
|
|
57
|
+
|
|
58
|
+
Worth naming as its own failure: the first version of the new scaffolder test passed with
|
|
59
|
+
the bug deliberately planted, because it was driven by that same pattern. A gate is only
|
|
60
|
+
worth what it catches, and the way to know is to break the thing on purpose and watch it
|
|
61
|
+
fail.
|
|
62
|
+
|
|
30
63
|
## 1.14.1 — 2026-09-01
|
|
31
64
|
|
|
32
65
|
Clearing the deferred list. Three of the four are fixed; the other two were sized and moved
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@zerotal/arch",
|
|
3
|
-
"version": "1.14.
|
|
3
|
+
"version": "1.14.2",
|
|
4
4
|
"license": "MIT",
|
|
5
5
|
"maturity": "stable",
|
|
6
6
|
"private": false,
|
|
@@ -35,11 +35,11 @@
|
|
|
35
35
|
"typecheck": "tsc --noEmit"
|
|
36
36
|
},
|
|
37
37
|
"dependencies": {
|
|
38
|
-
"@zerotal/core": "1.14.
|
|
38
|
+
"@zerotal/core": "1.14.2"
|
|
39
39
|
},
|
|
40
40
|
"devDependencies": {
|
|
41
41
|
"typescript": "^5.8.0",
|
|
42
|
-
"@zerotal/orm": "1.14.
|
|
42
|
+
"@zerotal/orm": "1.14.2"
|
|
43
43
|
},
|
|
44
44
|
"description": "The Zerotal agent surface — an MCP server that hands coding agents the framework's machine-readable truth: exact API signatures, live routes and schema, version-matched docs, and `zt doctor`.",
|
|
45
45
|
"keywords": [
|