[jnsdls]

Summary

Pins @rocicorp/zero 1.11.3 (from 1.10.0) and ports what changed in the server SDK between them.

 query builder
-  AST as built, normalized only when zero-cache hashes it
+  AST normalized at every step: related sorted by alias, where flattened + sorted
+  values ordered null < bool < number < string < array; static params comparable
+  empty and/or kept (always true / always false)
 z2s
+  LIKE patterns bound as text (non-string patterns match as their string)
+  char(n) compared as ::bpchar; bare `character` column named bpchar
-  $n::text::text  ->  $n::text
 mutate
+  mutator return value -> result.data, written to zero_0.mutations
+  tx.retry_on(predicate): re-run in a fresh tx, at most 5 runs per push
+  tx unusable once its transaction has ended
+  adapters take isolation_level=
 ZQLDatabase.run
+  bare statement when the connection supports it, no BEGIN/COMMIT
 query endpoint
+  transform requests parsed in strip mode (unknown fields ignored)
 compat proof
+  valita 0.5.5 (`dist/index.js`), scope remapped to 1.11.3 line numbers

Not ported: upstream's LogSink (Python logs through stdlib logging), and query interning, which only saves work.

Upstream now interns built queries, and a few type-violating inputs share a key: a flip of 'yes' with true, and any orderBy direction other than 'asc' with 'desc'. That made upstream's output depend on earlier programs. The harness now builds each program from a fresh schema, and docs/compat.md records it as a known difference.

Evidence

• Before (pin bumped, port unchanged): pytest: 53 failed, 661 passed (AST normalization, query bodies, SQL tier).
  After: pytest: 782 passed, zero_server at 100%; python -m tests.compat: 54 upstream modules and every port module fully exercised differentially.

• New differential tests:

  • Mutate: return values, every retry_on outcome, using a tx after it ended, isolation level per adapter, run with and without a bare connection.
  • SQL tier: char(3) and bpchar columns, compared and matched with LIKE.
  • Pinned builder programs: each new sort rule.

• Not run locally: e2e (port 55432 was held by an unrelated container). CI runs it.

• Wall-clock bench, Python side vs main:

  Case	main	This PR	Change
  build.simple	3.6 µs	4.0 µs	about 13% slower
  build.complex	20.1 µs	23.3 µs	about 16% slower
  query cases			7–16% slower
  z2s			unchanged

  The cost is the per-step normalization upstream added. TS got faster at rebuilding the same query thanks to interning, so expect CodSpeed to flag build/query. Porting interning is the follow-up that wins this back.

Merge Danger

Door: two-way

Blast Radius: wire

Every query AST sent to zero-cache changes shape: key order, sorted conditions and relationships, and empty and/or now kept. This now matches what a 1.11.3 TypeScript server sends. A deployment still on zero-cache 1.10 would see different query hashes, which re-runs its queries.

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​rocicorp/​zero@​1.10.0 ⏵ 1.11.3	-7		+1

View full report

[codspeed]

Merging this PR will degrade performance by 3.99%

1 warning, 1 note

⚠️ Base and head ran on different runner types

Some benchmarks with significant performance changes were compared across different runner types, so the changes might not come from the code. Run base and head on the same runner type, or use CodSpeed Macro Runners for more stable results.

Learn more about Macro Runners

Open the report in CodSpeed to investigate

ℹ️ 3 benchmarks have no flamegraph

The flamegraph wasn't generated: most of the time was spent in runtime internals, which would leave nothing useful to analyze.

See affected benchmarks

⚡ 4 improved benchmarks
❌ 10 (👁 10) regressed benchmarks
✅ 32 untouched benchmarks

Performance Changes

	Benchmark	BASE	HEAD	Efficiency
⚡	build.simple	131.3 µs	77 µs	+70.52%
⚡	map.complex	265.9 µs	159.2 µs	+67.01%
⚡	map.simple	107.9 µs	69 µs	+56.4%
⚡	build.complex	454 µs	341.6 µs	+32.87%
👁	parse.push.m1000	45.4 ms	51.4 ms	-11.57%
👁	query_json.complex.b1	1.3 ms	1.5 ms	-10.31%
👁	query_json.complex.b100	61.4 ms	84.8 ms	-27.56%
👁	query_json.simple.b1	747.3 µs	866.9 µs	-13.8%
👁	query_json.simple.b100	14 ms	19.5 ms	-28.01%
👁	query.complex.b1	1.1 ms	1.3 ms	-10.84%
👁	query.complex.b100	42.9 ms	70.2 ms	-38.92%
👁	query.simple.b100	10.9 ms	16.6 ms	-34.43%
👁	test_cpu[build.complex]	678.4 µs	772.1 µs	-12.14%
👁	test_cpu[build.simple]	175.2 µs	205.2 µs	-14.6%

Tip

Curious why performance improved? Comment @codspeedbot explain why performance improved on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing feat/zero-1.11.3 (81709d4) with main (a6ad73e)}