Repository navigation
chore(deps): update @rocicorp/zero to 1.12.0 - #94
Merged
Merged
Conversation
arv
marked this pull request as ready for review
November 12, 2026 15:16
Contributor
There was a problem hiding this comment.
🔵 Needs a closer look
Approval is deferred because the documented checks used the canary rather than the released 1.12.0 lockfile, leaving the updated native/runtime dependency stack unverified.
No open issues 🎉
1 file not reviewed
pnpm-lock.yaml: Generated file
What changed in this PR
Updates the repository and demo applications from @rocicorp/zero 1.11.5 to the released 1.12.0, with a regenerated dependency lockfile.
Changes:
- Pins the root package and all demos to
@rocicorp/zero1.12.0. - Regenerates
pnpm-lock.yamlwith Zero 1.12.0 and its refreshed transitive dependencies. - Retains the existing peer dependency range of
^1.7.0.
| File | Description |
|---|---|
| pnpm-lock.yaml | Regenerates dependency resolution for Zero 1.12.0 and its updated transitive dependency graph. |
| package.json | Updates the root development dependency to @rocicorp/zero 1.12.0. |
| demo/solid/package.json | Updates the Solid demo dependency to @rocicorp/zero 1.12.0. |
| demo/shared/package.json | Updates the shared demo dependency to @rocicorp/zero 1.12.0. |
| demo/react/package.json | Updates the React demo dependency to @rocicorp/zero 1.12.0. |
| demo/chat/package.json | Updates the chat demo dependency to @rocicorp/zero 1.12.0. |
Review effort: Lite
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.
Updates the
@rocicorp/zerodev dependency (root and demos) to1.12.0and regenerates the lockfile. The peer range (^1.7.0) is unchanged.This is part of the Zero 1.12 release smoke test. The pin was moved from the canary to the released
1.12.0and the lockfile regenerated on 2026-11-12. It stays a draft until the checks have been rerun against 1.12.0; the results below are from the canary.Checks run locally with pnpm 11.1.3:
format --check, lint, check-types,test(11 files, 158 tests), build and the React demo's Playwright suite (48 tests, against a zero-cache started from this canary) pass.The demos still pass
userID: 'anon'for logged-out clients (demo/*/main.tsx), and this canary's client warns that this is deprecated and that the option should be omitted for logged-out clients. The demos keep working because their zero-cache doesn't verify JWTs, but dropping the fallback would silence the warning; that can go in this PR or a follow-up.