Repository navigation
chore: version packages - #264
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
11 times, most recently
from
November 20, 2026 22:07
16e3672 to
6656032
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 20, 2026 23:53
6656032 to
14d9f55
Compare
This branch has not been deployed
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.
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.1
Patch Changes
mallocis slow at the client's many small allocations: with jemalloc,Zero::newon 8,097 stored rows takes 25 ms instead of 34 ms, and a poke of 1,000 rows on SQLite 4.9 ms instead of 6.1 ms, with the same memory. mimalloc is about as fast but holds a quarter more memory for 100,000 rows.Zero::from_preparedandZero::newtake less of the app's thread to load a stored replica. On a Mac,from_preparedtakes 3.5 ms instead of 5.4 ms for a replica of 8,000 rows, and 2.0 ms instead of 2.6 ms for 2,000;Zero::newtakes 22.8 ms instead of 23.7 ms for 8,000. On Linux,from_preparedtakes 9.9 ms instead of 13.1 ms for 8,000 rows. The replica's map is built a level at a time from the stored rows, which come in key order, and the query sources load straight from it instead of from an add made for every row.Zero::from_preparedtakes less of the app's thread. On a Mac, it takes 2.1 ms instead of 3.8 ms for a replica of 8,000 rows, and 1.6 ms instead of 2.2 ms for 2,000; on Linux, 6.2 ms instead of 9.6 ms for 8,000.Zero::preparenow also sorts each table's rows for the query sources on its own thread, so the app's thread only puts them into the sources and hydrates the first views.zero-swift@0.10.1
Patch Changes
LiveQueryof many rows (and@ZeroQuery) updates faster: the rows it reads again copy the unchanged rows around them in runs instead of one at a time. On a Mac, an optimistic update with a live query of 1,000 rows takes 31 µs instead of 51 µs.VirtualListscrolls with less work on the Mac's main thread: it tells SwiftUI its size (what it's offered, as before) instead of SwiftUI asking Auto Layout for it, over every row's views, each time the stack around the list laid out, which it did for each snapshot. In the TestHost's issue list on a Mac, the main thread's work per frame while scrolling falls by 15–30%. The list's size is the same in every layout.