Skip to content

chore: version packages - #256

Merged
tmm merged 1 commit into
mainfrom
changeset-release/main
Nov 19, 2026
Merged

tmm merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 19, 2026 •

Copy link
Copy Markdown

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

zero-rust@0.5.0

Minor Changes

  • 607f99d: Zero::prepare(schema, context, mutators, options) opens the client's SQLite store and reads its replica on a thread of its own, and Zero::from_prepared(prepared, scheduler, socket_factory) makes the client from it on the app's thread. Call prepare as early as the app knows its options, and from_prepared where the first frame needs the client: it waits for whatever is left, and the client and its views have their rows at once, as with Zero::new. At launch, Zero then takes 5.6 ms of the app's thread on a Mac for a replica of 8,000 rows instead of 17.8 ms, and 2.8 ms instead of 7.1 ms for 2,000. Loading the replica into the query sources and hydrating the first views stay on the app's thread. Zero::new and materialize don't change.

Patch Changes

  • edec2e7: Zero::new takes less time on a replica of thousands of rows: on a Mac, 19.0 ms instead of 23.0 ms for 8,000 rows, and 7.0 ms instead of 7.6 ms for 2,000. The replica goes into the query sources without a diff against an empty one, the first report of its queries and mutation results reads only those keys, and a diff of two whole copies of the replica walks them once instead of sorting their keys.

zero-swift@0.10.0

Minor Changes

  • 73d5f6b: Zero.prepare(schema:context:mutators:options:queries:) opens the client's store, reads its replica, and hydrates the queries the app's first frame shows, off the main actor, and Zero(prepared) takes the result over on the main actor. Call prepare as early as the app knows its options, such as in App.init, and make the client where the first frame needs it: it waits for whatever is left, and the views of the prepared queries have their rows at once, as with Zero.init. At launch, Zero then takes about 2 ms of the main thread on a Mac however large the replica is, instead of 10 ms for a replica of 2,000 rows and 25 ms for 8,000. Zero.init and materialize don't change.

Patch Changes

  • cd2855b: Opening a client takes less of the main thread before the app's first frame: a third less for a replica of about 2,000 rows (on a Mac, 10.9 ms instead of 15.6 ms; on the iOS Simulator, 20.4 ms instead of 26.2 ms), and 40% less for 8,000 rows. The replica goes into the query sources without a diff against an empty one, and the first report of its queries and mutation results reads only those keys. The URLSession is made by the first connect, the network monitor starts on its own queue, and the storage folder is excluded from backups in the background.

@github-actions
github-actions Bot force-pushed the changeset-release/main branch 2 times, most recently from 3cbcb3c to 29c5bc9 Compare November 19, 2026 20:33
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 29c5bc9 to c7b8e88 Compare November 19, 2026 21:05
@tmm
tmm merged commit a672f87 into main Nov 19, 2026
24 checks passed
@tmm
tmm deleted the changeset-release/main branch November 19, 2026 22:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant