Version Packages - #53
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
7 times, most recently
from
September 7, 2026 10:49
dc549d1 to
f3beee7
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 8, 2026 03:41
f3beee7 to
f6bac47
Compare
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 the packages will be published to npm 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
stratasync@2.5.0
Minor Changes
a350052: Add the
stratasyncCLI.npx stratasync init my-appscaffolds a runnable app: a Fastify + Postgres sync server inapi/and a React client inweb/, as npm workspaces, with@stratasync/*pinned to the CLI's own version.The template is built from the repo's
examples/at build time rather than kept as a second copy, so it is the app the repo already tests.initsupports--dry-run,--force,--output jsonand--no-input, writes data to stdout and hints to stderr, and refuses a non-empty directory unless forced.This is a new package name, so the first publish is manual: npm cannot register a trusted publisher for a package that does not exist yet.
Patch Changes
npm run db:pushexited 1 without creating any tables or printing an error, so the firstdev:apifailed on a missing table.@stratasync/client@2.5.0
Patch Changes
@stratasync/mobx@2.5.0
Patch Changes
@stratasync/next@2.5.0
Patch Changes
@stratasync/react@2.5.0
Patch Changes
@stratasync/storage-idb@2.5.0
Patch Changes
@stratasync/storage-local@2.5.0
Patch Changes
@stratasync/transport-graphql@2.5.0
Patch Changes
@stratasync/core@2.5.0
@stratasync/server@2.5.0
@stratasync/y-doc@2.5.0