Skip to content

Version Packages #306

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Version Packages #306

wants to merge 1 commit into from
+341 −90

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jul 21, 2025 •
edited
Loading

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

@powersync/[email protected]

Minor Changes

  • d56eeb9: Delay switching over to new sync rules until we have a consistent checkpoint.
  • d4db4e2: MySQL:
    • Added schema change handling
    • Except for some edge cases, the following schema changes are now handled automatically:
      • Creation, renaming, dropping and truncation of tables.
      • Creation and dropping of unique indexes and primary keys.
      • Adding, modifying, dropping and renaming of table columns.
    • If a schema change cannot handled automatically, a warning with details will be logged.
    • Mismatches in table schema from the Zongji binlog listener are now handled more gracefully.
    • Replication of wildcard tables is now supported.
    • Improved logging for binlog event processing.

Patch Changes

@powersync/[email protected]

Minor Changes

  • d56eeb9: Delay switching over to new sync rules until we have a consistent checkpoint.
  • d4db4e2: MySQL:
    • Added schema change handling
    • Except for some edge cases, the following schema changes are now handled automatically:
      • Creation, renaming, dropping and truncation of tables.
      • Creation and dropping of unique indexes and primary keys.
      • Adding, modifying, dropping and renaming of table columns.
    • If a schema change cannot handled automatically, a warning with details will be logged.
    • Mismatches in table schema from the Zongji binlog listener are now handled more gracefully.
    • Replication of wildcard tables is now supported.
    • Improved logging for binlog event processing.

Patch Changes

@powersync/[email protected]

Minor Changes

  • d56eeb9: Delay switching over to new sync rules until we have a consistent checkpoint.
  • d4db4e2: MySQL:
    • Added schema change handling
    • Except for some edge cases, the following schema changes are now handled automatically:
      • Creation, renaming, dropping and truncation of tables.
      • Creation and dropping of unique indexes and primary keys.
      • Adding, modifying, dropping and renaming of table columns.
    • If a schema change cannot handled automatically, a warning with details will be logged.
    • Mismatches in table schema from the Zongji binlog listener are now handled more gracefully.
    • Replication of wildcard tables is now supported.
    • Improved logging for binlog event processing.

Patch Changes

@powersync/[email protected]

Minor Changes

  • 2378e36: Drop support for legacy Supabase keys via app.settings.jwt_secret.
  • 2378e36: Add automatic support for Supabase JWT Signing Keys.
  • d56eeb9: Delay switching over to new sync rules until we have a consistent checkpoint.
  • d4db4e2: MySQL:
    • Added schema change handling
    • Except for some edge cases, the following schema changes are now handled automatically:
      • Creation, renaming, dropping and truncation of tables.
      • Creation and dropping of unique indexes and primary keys.
      • Adding, modifying, dropping and renaming of table columns.
    • If a schema change cannot handled automatically, a warning with details will be logged.
    • Mismatches in table schema from the Zongji binlog listener are now handled more gracefully.
    • Replication of wildcard tables is now supported.
    • Improved logging for binlog event processing.

Patch Changes

@powersync/[email protected]

Minor Changes

  • d56eeb9: Delay switching over to new sync rules until we have a consistent checkpoint.
  • d4db4e2: MySQL:
    • Added schema change handling
    • Except for some edge cases, the following schema changes are now handled automatically:
      • Creation, renaming, dropping and truncation of tables.
      • Creation and dropping of unique indexes and primary keys.
      • Adding, modifying, dropping and renaming of table columns.
    • If a schema change cannot handled automatically, a warning with details will be logged.
    • Mismatches in table schema from the Zongji binlog listener are now handled more gracefully.
    • Replication of wildcard tables is now supported.
    • Improved logging for binlog event processing.

Patch Changes

@powersync/[email protected]

Minor Changes

  • 2378e36: Drop support for legacy Supabase keys via app.settings.jwt_secret.
  • 4ebc3bf: Report lack of commits or keepalives as issues in the diagnostics api.
  • 2378e36: Add automatic support for Supabase JWT Signing Keys.
  • d56eeb9: Delay switching over to new sync rules until we have a consistent checkpoint.
  • d4db4e2: MySQL:
    • Added schema change handling
    • Except for some edge cases, the following schema changes are now handled automatically:
      • Creation, renaming, dropping and truncation of tables.
      • Creation and dropping of unique indexes and primary keys.
      • Adding, modifying, dropping and renaming of table columns.
    • If a schema change cannot handled automatically, a warning with details will be logged.
    • Mismatches in table schema from the Zongji binlog listener are now handled more gracefully.
    • Replication of wildcard tables is now supported.
    • Improved logging for binlog event processing.

Patch Changes

@powersync/[email protected]

Minor Changes

  • d56eeb9: Delay switching over to new sync rules until we have a consistent checkpoint.
  • d4db4e2: MySQL:
    • Added schema change handling
    • Except for some edge cases, the following schema changes are now handled automatically:
      • Creation, renaming, dropping and truncation of tables.
      • Creation and dropping of unique indexes and primary keys.
      • Adding, modifying, dropping and renaming of table columns.
    • If a schema change cannot handled automatically, a warning with details will be logged.
    • Mismatches in table schema from the Zongji binlog listener are now handled more gracefully.
    • Replication of wildcard tables is now supported.
    • Improved logging for binlog event processing.

Patch Changes

@powersync/[email protected]

Minor Changes

  • d4db4e2: MySQL:
    • Added schema change handling
    • Except for some edge cases, the following schema changes are now handled automatically:
      • Creation, renaming, dropping and truncation of tables.
      • Creation and dropping of unique indexes and primary keys.
      • Adding, modifying, dropping and renaming of table columns.
    • If a schema change cannot handled automatically, a warning with details will be logged.
    • Mismatches in table schema from the Zongji binlog listener are now handled more gracefully.
    • Replication of wildcard tables is now supported.
    • Improved logging for binlog event processing.

@powersync/[email protected]

Patch Changes

@powersync/[email protected]

Patch Changes

@powersync/[email protected]

Patch Changes

@powersync/[email protected]

Patch Changes

@powersync/[email protected]

Patch Changes

  • a882b94: Change application_name on postgres connections from 'PowerSync' to 'powersync/{version}'.

@powersync/[email protected]

Patch Changes

@powersync/[email protected]

Patch Changes

  • 1aafdaf: Report HTTP method in RouteNotFound error

@powersync/[email protected]

@powersync/[email protected]

Minor Changes

  • 2378e36: Drop support for legacy Supabase keys via app.settings.jwt_secret.
  • 4ebc3bf: Report lack of commits or keepalives as issues in the diagnostics api.
  • 2378e36: Add automatic support for Supabase JWT Signing Keys.

Patch Changes

[email protected]

Patch Changes

@github-actions github-actions bot force-pushed the changeset-release/main branch 5 times, most recently from 847b386 to 16ea5f1 Compare July 29, 2025 06:46
@github-actions github-actions bot force-pushed the changeset-release/main branch from 16ea5f1 to 4e1fd5b Compare July 29, 2025 14:16
@github-actions github-actions bot force-pushed the changeset-release/main branch from 4e1fd5b to bb57d7c Compare July 30, 2025 09:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants