@neocompose/cli 0.58.2 → 0.59.0

package/CHANGELOG.md

@@ -1,5 +1,19 @@
 # Changelog
 
+## [0.59.0] - 2026-09-24
+
+- **Behavior change:** Push prepares the commit on your machine and the server applies it as sent. The server checks the project head, each change's base, authorization, and row shapes, but no longer recompiles NeoScript, materializes values, or validates the project again. On a bulk push of 60 classes and a 150-entry list, server preparation takes 4.2 s instead of 22.8 s and the push takes 72.7 s instead of 86.9 s.
+- **Behavior change:** A push is rejected when another commit lands between upload and server preparation. Run `neo pull`, then push again. Before, the server prepared the push again against the new head.
+- **Behavior change:** `--accept-bump` only accepts a version bump. It no longer lets a push land on a moved project head.
+- The server rejects a CLI that compiles a different NeoScript revision, and tells you to upgrade. CLI versions before 0.59.0 can no longer push.
+- A push over the server's body limit (32 MB, or 18 MB compressed) fails with its size and the limit. Before, it used a slower route that prepared the push on the server.
+
+## [0.58.3] - 2026-09-24
+
+- Joined snapshot pages carry stored JSON. Document readers decode it after the query returns, reducing query work and allowing large numeric payloads to fit in fewer requests.
+
+- Document reads plan independent ranges before fetching payloads, with parallelism scaled to project size and deployment capacity. Pull and other document readers trade some additional reads for shorter waits; each payload page uses the available Convex limits and stays on the same published revision.
+
 ## [0.58.2] - 2026-09-24
 
 - Pull downloads up to eight managed image or audio files concurrently. Matching local bytes are still reused.

package/README.md

@@ -385,12 +385,13 @@ desired result, or use `neo resolve --mine|--theirs` as a whole-side
 convenience. There is no force-CAS bypass. Accept a required compatibility
 bump only after reviewing it with `neo push --accept-bump`.
 
-One push recompiles changed NeoScript and schema-affected callers at the
-trusted server boundary and atomically commits semantic record changes,
-localized main-locale edits, and staged files under CAS. Normal push sends the
-semantic diff plus a deterministic source hash; `neo push --dry-run` performs
-the complete source-to-record rehearsal. Client AST, compiled IR, placement
-stamps, and derived links are not trusted.
+One push prepares its commit locally: it recompiles changed NeoScript and
+schema-affected callers, materializes values, and validates the whole graph
+against the pulled head. The server checks that head, each change's CAS base,
+authorization, and row shapes, then atomically commits semantic record changes,
+localized main-locale edits, and staged files. It accepts preparation only from
+a CLI on its own NeoScript compiler revision. `neo push --dry-run` runs the
+same preparation plus the complete source-to-record rehearsal.
 
 Create classes, stored values, file declarations, and dialogues by editing their tracked `.neo` or `.neoflow` source directly. Add managed binaries under `Files/Images/` or `Files/AudioClips/`; `neo push` discovers and stages them with the source transaction. The CLI intentionally has no parallel scaffold or low-level content-write commands.