What's changing: The PowerSync service test-client gains a --env <path> flag across its generate-token, fetch-operations, and concurrent-connections commands. Passing --env loads a .env file before parsing powersync.yaml, enabling configs that use !env PS_* YAML tags to be resolved without pre-exporting shell environment variables.
Why this matters for docs: CLI workflow change — the existing test-client documentation shows the generate-token command without the --env option; users whose configs use !env tags (a common pattern for keeping secrets out of YAML) need this flag and currently cannot discover it from the docs.
Likely affected pages/sections:
- Development Tokens (self-hosted) (
/configuration/auth/development-tokens) and the shared snippet snippets/dev-token-self-hosted-steps.mdx — the test-client tab currently shows node dist/bin.js generate-token --config path/to/service.yaml --sub test-user; add a note or extended example showing --env path/to/.env for configs that use !env tags
- Usage & Billing FAQ (
/resources/usage-and-billing/usage-and-billing-faq) — the fetch-operations example (node dist/bin.js fetch-operations --raw --token ... --endpoint ...) could note that --env is also supported when the config uses environment variable tags
Source PR: powersync-ja/powersync-service#650. Note: at the time of filing this issue the PR is merged 2026-05-26. Publish updates only after the PR is merged and the change shipped in a release.
Filed automatically by a scheduled process running on Claude Code (claude-sonnet-4-6). A human should verify the scope and timing before publishing any changes.
What's changing: The PowerSync service
test-clientgains a--env <path>flag across itsgenerate-token,fetch-operations, andconcurrent-connectionscommands. Passing--envloads a.envfile before parsingpowersync.yaml, enabling configs that use!env PS_*YAML tags to be resolved without pre-exporting shell environment variables.Why this matters for docs: CLI workflow change — the existing test-client documentation shows the
generate-tokencommand without the--envoption; users whose configs use!envtags (a common pattern for keeping secrets out of YAML) need this flag and currently cannot discover it from the docs.Likely affected pages/sections:
/configuration/auth/development-tokens) and the shared snippetsnippets/dev-token-self-hosted-steps.mdx— the test-client tab currently showsnode dist/bin.js generate-token --config path/to/service.yaml --sub test-user; add a note or extended example showing--env path/to/.envfor configs that use!envtags/resources/usage-and-billing/usage-and-billing-faq) — thefetch-operationsexample (node dist/bin.js fetch-operations --raw --token ... --endpoint ...) could note that--envis also supported when the config uses environment variable tagsSource PR: powersync-ja/powersync-service#650. Note: at the time of filing this issue the PR is merged 2026-05-26. Publish updates only after the PR is merged and the change shipped in a release.
Filed automatically by a scheduled process running on Claude Code (claude-sonnet-4-6). A human should verify the scope and timing before publishing any changes.