zerotal 1.4.0 → 1.5.0

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.
Files changed (3) hide show
  1. package/CHANGELOG.md +27 -0
  2. package/README.md +1 -1
  3. package/package.json +12 -12
package/CHANGELOG.md CHANGED
@@ -8,6 +8,33 @@ follows the Zerotal monorepo's unified versioning.
8
8
 
9
9
  ## [Unreleased]
10
10
 
11
+ ## [1.4.0] — 2026-08-10
12
+
13
+ ### Changed
14
+
15
+ - Version bump in step with the monorepo. The subpath surface re-exports
16
+ `@zerotal/core` and the stable packages, so the changes that matter are in
17
+ their changelogs — notably the ORM's encrypted columns and Flow's
18
+ `preserveScroll`/navigation-scroll fixes this release.
19
+
20
+ ## [1.3.0] — 2026-08-09
21
+
22
+ ### Changed
23
+
24
+ - Version bump in step with the monorepo. The mixin-composition rename
25
+ (`BaseModelWith(...)` → `Model.using(...)`, `ComponentWith(...)` →
26
+ `Component.using(...)`) lands through the re-exported packages; run
27
+ `bun run scripts/codemod-mixin-composition.ts` when upgrading from 1.1.x.
28
+
29
+ ## [1.1.0] — 2026-08-08
30
+
31
+ ### Changed
32
+
33
+ - Version bump in step with the monorepo, carrying the 1.1.0 fix wave from the
34
+ first field reports (radio-group bindings, json-cast round-tripping, insert
35
+ defaults, `Schema.alter`, `ctx.param()`, and the rest) through the
36
+ re-exported packages.
37
+
11
38
  ## [1.0.3] — 2026-08-07
12
39
 
13
40
  ### Changed
package/README.md CHANGED
@@ -31,7 +31,7 @@ Core's own subpaths are mirrored 1:1, so `zerotal` is a full drop-in for `@zerot
31
31
 
32
32
  There is no behaviour here and no version skew: the meta package pins the same monorepo version as every `@zerotal/*` package it re-exports. Installing a scoped package directly is always equivalent — this package exists so a new app needs exactly one dependency to start.
33
33
 
34
- Beta and experimental packages (`@zerotal/flow`, `@zerotal/flow-ui`, `@zerotal/admin`, `@zerotal/devtools`, ...) are not bundled; install them individually while they harden.
34
+ Beta packages (`@zerotal/media`, `@zerotal/tenancy`, ...) are not bundled; install them individually while they harden. `@zerotal/flow`, `@zerotal/flow-ui`, `@zerotal/admin`, `@zerotal/monitor` and `@zerotal/devtools` are stable but stay unbundled as well — a server-driven UI layer, a component library, an admin panel, an ops panel and a dev-only panel are choices an app makes, not defaults every dependency tree should carry.
35
35
 
36
36
  Scaffolding a new app? Use `bun create zerotal my-app` instead — it wires an application skeleton, not just dependencies.
37
37
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "zerotal",
3
- "version": "1.4.0",
3
+ "version": "1.5.0",
4
4
  "license": "MIT",
5
5
  "maturity": "stable",
6
6
  "private": false,
@@ -59,17 +59,17 @@
59
59
  "typecheck": "tsc --noEmit"
60
60
  },
61
61
  "dependencies": {
62
- "@zerotal/auth": "1.4.0",
63
- "@zerotal/cache": "1.4.0",
64
- "@zerotal/client": "1.4.0",
65
- "@zerotal/core": "1.4.0",
66
- "@zerotal/media": "1.4.0",
67
- "@zerotal/orm": "1.4.0",
68
- "@zerotal/queue": "1.4.0",
69
- "@zerotal/scheduler": "1.4.0",
70
- "@zerotal/session": "1.4.0",
71
- "@zerotal/testing": "1.4.0",
72
- "@zerotal/validator": "1.4.0"
62
+ "@zerotal/auth": "1.5.0",
63
+ "@zerotal/cache": "1.5.0",
64
+ "@zerotal/client": "1.5.0",
65
+ "@zerotal/core": "1.5.0",
66
+ "@zerotal/media": "1.5.0",
67
+ "@zerotal/orm": "1.5.0",
68
+ "@zerotal/queue": "1.5.0",
69
+ "@zerotal/scheduler": "1.5.0",
70
+ "@zerotal/session": "1.5.0",
71
+ "@zerotal/testing": "1.5.0",
72
+ "@zerotal/validator": "1.5.0"
73
73
  },
74
74
  "devDependencies": {
75
75
  "typescript": "^5.8.0"