From 2dea5a69c3af951243124a90d7ef29c9e75cb1ba Mon Sep 17 00:00:00 2001 From: Benita Volkmann Date: Tue, 22 Sep 2026 16:47:08 +0200 Subject: [PATCH] Link to the sync rules LTS plan --- sync/rules/migrate-to-sync-streams.mdx | 4 +--- sync/rules/overview.mdx | 4 +--- 2 files changed, 2 insertions(+), 6 deletions(-) diff --git a/sync/rules/migrate-to-sync-streams.mdx b/sync/rules/migrate-to-sync-streams.mdx index e4a56342..d11dc572 100644 --- a/sync/rules/migrate-to-sync-streams.mdx +++ b/sync/rules/migrate-to-sync-streams.mdx @@ -18,9 +18,7 @@ If your Sync Config has a `bucket_definitions:` section, you use Sync Rules and ## Why Migrate? -{/* TODO: Link to the Sync Rules deprecation announcement once it is published. */} - -Sync Rules are deprecated, and PowerSync is phasing them out in favor of Sync Streams. Beyond matching Sync Rules, Sync Streams add: +Sync Rules are deprecated, and PowerSync is phasing them out in favor of Sync Streams. See [our plan for phasing out Sync Rules](https://releases.powersync.com/announcements/our-plan-for-phasing-out-sync-rules) for the full timeline. Beyond matching Sync Rules, Sync Streams add: - **More expressive queries:** Stream queries support JOINs, [CTEs](/sync/streams/ctes), subqueries, and [multiple queries per stream](/sync/streams/queries#multiple-queries-per-stream), with syntax closer to plain SQL. You write one query instead of separate `parameters:` and `data:` blocks. - **On-demand syncing:** Define a stream once, then subscribe from your app one or more times with different parameters. Each subscription has its own lifecycle, so two screens or browser tabs can subscribe to the same stream independently. With Sync Rules, Client Parameters approximate this. You have to aggregate the parameter values yourself across screens and tabs, and remove them when they are no longer needed. diff --git a/sync/rules/overview.mdx b/sync/rules/overview.mdx index edeb3c6a..a279b27e 100644 --- a/sync/rules/overview.mdx +++ b/sync/rules/overview.mdx @@ -6,12 +6,10 @@ description: "Understand legacy Sync Rules for controlling which data syncs to e Sync Rules are PowerSync's original system for partial sync, using YAML bucket definitions. -{/* TODO: Link to the Sync Rules deprecation announcement on releases.powersync.com once it is published. */} - **Sync Rules are deprecated** -PowerSync is phasing out Sync Rules in favor of [Sync Streams](/sync/streams/overview), which support everything Sync Rules do and add on-demand syncing, JOINs, CTEs, and subqueries. Nothing changes for your instance today: Sync Rules keep working and stay supported while you migrate. New Sync Config features are added to Sync Streams only. +PowerSync is phasing out Sync Rules in favor of [Sync Streams](/sync/streams/overview), which support everything Sync Rules do and add on-demand syncing, JOINs, CTEs, and subqueries. Nothing changes for your instance today: Sync Rules keep working and stay supported while you migrate. New Sync Config features are added to Sync Streams only. See [our plan for phasing out Sync Rules](https://releases.powersync.com/announcements/our-plan-for-phasing-out-sync-rules) for the full timeline. To migrate, click **Migrate to Sync Streams** in the PowerSync Dashboard, or run `powersync migrate sync-rules` in the CLI to convert your current config. Migrating does not change what your app syncs. See [Migrate to Sync Streams](/sync/rules/migrate-to-sync-streams).