Prepare update#396
Merged
Merged
Conversation
benitav
reviewed
Apr 9, 2026
benitav
reviewed
Apr 9, 2026
rkistner
approved these changes
Apr 9, 2026
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
3 participants
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 prepares version 2.0.0 (currently as a
-wiprelease) of thepowersyncpackage and0.7.0ofpowersync_attachments_helper. I've considered making this a minor release since it shouldn't be breaking for almost all users, but making this a major update is the correct thing to do to follow semver rules. Apart from breaking changes affecting open factories and merged packages, users would also have to update theirsqlite3.wasmandpowersync_db.worker.js.I've added a changelog entry by copying relevant sections from the
sqlite_asyncpackage and the other PRs on thedevbranch.