PowerSync Rust SDK: v0.1.0

We are pleased to announce the release of version 0.1.0 of the PowerSync Rust client SDK. With this release, the SDK is in beta. Install it from crates.io with cargo add powersync.

See the full changelog below.

Have any questions or feedback? Chat with us and the PowerSync community on Discord.

Changelog

v0.1.0 - 2026-09-28

• [BREAKING] PowerSyncEnvironment::custom now needs a way to spawn async tasks. Replace tokio_timer() with tokio(), or async_io_timer() with async_io(executor). The executor argument must be an Arc<async_executor::Executor<'static>>. connect() now spawns the sync tasks, so you no longer call async_tasks().spawn_with() before you connect. (PR #40)

• [ADDED] PowerSyncDatabase::request_checkpoint() requests a checkpoint and lets you wait until all source data created before it has synced. Opt in with SyncOptions::with_checkpoint_mode(CheckpointMode::Requests(..)). See Sync Catch-Up. (PR #41, PR #43)

• [ADDED] PowerSyncDatabase::disconnect_and_clear() disconnects and removes PowerSync data from the database. (PR #45)

• [IMPROVED] The SDK now sets the cache size and busy timeout on all connections, not only on the writer. (PR #33)

• [IMPROVED] The SDK now uses version 0.5.3 of the PowerSync core extension. (PR #44)

• [FIXED] A failed COMMIT, for example because of a deferred foreign key constraint, left the connection inside the transaction. Later writes then failed with Connection already in transaction. Thanks @julianallchin! (PR #27)

• [FIXED] The sync client held the writer while it waited for fetch_credentials(), so a slow credentials provider blocked local writes. Thanks @birdmanmandbir! (PR #31)

• [FIXED] The sync status briefly reported a connection before the sync request succeeded, also when the request failed. (PR #32)

• [FIXED] A write checkpoint that you passed when you completed the last CRUD transaction was never applied. (PR #36)