Repository navigation
feat: support @rocicorp/zero 1.11.4 - #59
Merged
Merged
Conversation
1.11.4 changes only zero-cache (CVR AST parse error handling, change-streamer drain). No server-SDK source moved, so this is a pin bump: ZERO_VERSION, harness and e2e npm pins and lockfiles, the e2e zero-cache image, README, and each ported module's docstring moved to zero/v1.11.4 (be94346). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Moves the pinned Zero version from 1.11.3 to 1.11.4 (published Nov 4). Between the two tags, upstream source changed only in
packages/zero-cache:cvr-store.tsnow throws a warn-levelInvalidClientASTErrorfor an unparseable stored AST, and the change-streamer got drain handling. No file in the ported server-SDK scope (zero-server,zero-protocol,zql,z2s,shared) changed, so there is nothing new to port.Vendored transitive dependencies are unchanged in the lockfile:
@badrap/valita0.5.5,@databases/escape-identifier1.0.3, and@databases/validate-unicode1.0.0. The bench ratios in the README (stamped at ec0768a against 1.11.3) and the phase history indocs/plan.mdare left alone.Evidence
Nothing on screen changes. All of these ran locally against 1.11.4:
ruff check,ruff format --check,ty check: cleanpytest: 795 passed, 100% coverage, includingtests/wire/test_bench_fixtures.py, so the benchmark fixtures don't need regeneratingpython -m tests.compat: 54 upstream modules, and every port module, fully exercised differentiallye2e/run.pyagainst therocicorp/zero:1.11.4image: upstream rows identicalReviewed with sol-loop: 1 round with gpt-6.1-sol. Sol verdict: approved
Merge Danger
Door: two-way
Reverting the pin restores 1.11.3.
Blast Radius: minimal
The compatibility claim now names 1.11.4. Python runtime code is unchanged.
🤖 Generated with Claude Code
Open in [code]smith · Need help on this PR? Tag
@codesmith-botwith what you need.