@kya-os/checkpoint-wasm-runtime 1.4.1 → 1.4.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/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,59 @@
|
|
|
1
1
|
# @kya-os/checkpoint-wasm-runtime
|
|
2
2
|
|
|
3
|
+
## 1.4.2 — 2026-05-18
|
|
4
|
+
|
|
5
|
+
**Recovery release. Do NOT use 1.4.1 — it was published with a broken
|
|
6
|
+
tarball that ships only `wasm/kya-os-engine-bundler/*` and is missing
|
|
7
|
+
`wasm/kya-os-engine/*` (nodejs target) + `wasm/kya-os-engine-web/*`
|
|
8
|
+
(web target) entirely. Consumers using the `./engine`,
|
|
9
|
+
`./engine/node`, `./orchestrator`, or `./orchestrator/node` subpaths
|
|
10
|
+
crash on import with `ERR_MODULE_NOT_FOUND` (or
|
|
11
|
+
`FUNCTION_INVOCATION_FAILED` on Vercel).**
|
|
12
|
+
|
|
13
|
+
### What 1.4.1 should have shipped
|
|
14
|
+
|
|
15
|
+
1.4.1 was a patch release bundling two fixes on top of 1.4.0:
|
|
16
|
+
|
|
17
|
+
- **#2659** — split anthropic vendor pattern into 3 per-bot entries
|
|
18
|
+
(`anthropic_claude_user`, `anthropic_claudebot`,
|
|
19
|
+
`anthropic_claude_web`). Updates the Tier-3 ruleset hash.
|
|
20
|
+
- **#2663** — `httpStatusForBlockReason` + `blockResponseBody`
|
|
21
|
+
switches gained `Tier3UAMatch` and `AgentAttribution` cases (were
|
|
22
|
+
falling through to `undefined` status → Express default 500
|
|
23
|
+
error page). Adds the matching variants to the TS `BlockReason`
|
|
24
|
+
union (with snake_case `pattern_id` / `pattern_kind` matching the
|
|
25
|
+
Rust serde wire format).
|
|
26
|
+
|
|
27
|
+
### Root cause of the broken 1.4.1 tarball
|
|
28
|
+
|
|
29
|
+
`prepublishOnly` chains `copy-engine-wasm` (nodejs target) +
|
|
30
|
+
`copy-engine-wasm-web` (web target) + `copy-engine-wasm-bundler`
|
|
31
|
+
(bundler target). Each script `cp`s from `rust/crates/kya-os-engine/
|
|
32
|
+
pkg{,-web,-bundler}/` into `packages/checkpoint-wasm-runtime/wasm/`.
|
|
33
|
+
The publish was invoked from a fresh `git reset --hard origin/main`
|
|
34
|
+
state with **only `wasm-pack build --target bundler`** run before
|
|
35
|
+
publish — `pkg/` (nodejs) and `pkg-web/` (web) were empty. The cp
|
|
36
|
+
commands silently produced empty target dirs (`wasm/kya-os-engine/`
|
|
37
|
+
|
|
38
|
+
- `wasm/kya-os-engine-web/`) populated only with the git-committed
|
|
39
|
+
`README.md` placeholders, and the tarball shipped that state.
|
|
40
|
+
|
|
41
|
+
### What 1.4.2 ships
|
|
42
|
+
|
|
43
|
+
Identical TS + Rust changes to 1.4.1 (no code regression) but with
|
|
44
|
+
the full wasm artifact set (`wasm/kya-os-engine/`,
|
|
45
|
+
`wasm/kya-os-engine-web/`, `wasm/kya-os-engine-bundler/`) verified
|
|
46
|
+
present before publish.
|
|
47
|
+
|
|
48
|
+
### Hardening (separate dylan-todo to follow)
|
|
49
|
+
|
|
50
|
+
`prepublishOnly` should fail-fast when any of the three artifact
|
|
51
|
+
dirs is missing rather than producing an empty-but-existing dir.
|
|
52
|
+
Filing as `Engine-WASM-Publish-Sanity-Gate-1` so the next regen
|
|
53
|
+
can't ship the same shape of partial tarball silently.
|
|
54
|
+
|
|
55
|
+
---
|
|
56
|
+
|
|
3
57
|
## 1.4.0 — 2026-05-18
|
|
4
58
|
|
|
5
59
|
**Minor release** consolidating SDK-Next.js-Integration-Audit-1
|
package/package.json
CHANGED
|
Binary file
|