[Drift] New optional sync_config.version_label field lets operators tag deployed sync config versions (powersync-service #756)

[benitav]

What's changing: PowerSync Service adds an optional version_label field to the sync_config section of the main config YAML. When set, the label is persisted alongside the deployed sync config and surfaced in log output and diagnostics, primarily to help automated deployment tooling (e.g. the PowerSync Cloud dashboard) distinguish between sync config versions when a single replication stream handles multiple configs. It can also be set manually, though nothing enforces that it stays updated or unique.

High priority — existing docs are now inaccurate or incomplete
None identified.

For reviewer consideration — worth documenting

• New optional sync_config.version_label config field. Self-Hosted Instance Configuration (configuration/powersync-service/self-hosted-instances.mdx → https://docs.powersync.com/configuration/powersync-service/self-hosted-instances), "Sync Streams" section, documents the sync_config: key's path and content options but does not mention version_label. Self-hosted operators using automated deployment tooling have no way to discover this option from docs.

Source PR: powersync-ja/powersync-service#756. Merged 2026-08-26.

Filed automatically by Claude Code (claude-sonnet-5). A human must verify the scope, prepare the docs PR, and publish it only once this update has been released.

[rkistner]

Would be good to add to the full config reference in #578, but I don't think we need more than that, since the primary purpose is for the cloud version.