Version Packages

[jumski]

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

pgflow@0.17.0

Minor Changes

• 01147fe: Persist physical queue identity on steps and tasks. A queued task's message identity is now (queue_name, message_id), not message_id alone, preparing pgflow for private per-step queues while keeping one-flow/one-queue behavior.

  pgflow.steps and pgflow.step_tasks gain a canonical lowercase queue_name (snapshot at task creation), (queue_name, message_id) is unique per queue, and two flows can no longer share a normalized default queue. Breaking: pgflow.start_tasks() now requires the queue_name argument - the queue's canonical identity, lower(flow_slug) today - and the released three-argument form and the NULL default are gone, and startTasks() on IPgflowClient/PgflowSqlClient requires the queue argument as well. pgflow's own workers poll and claim through that canonical name; custom callers must pass it explicitly. There is no mixed-version rolling upgrade: stop and drain workers, pause producers and definition/maintenance/recovery writers, apply the transactional migration through Supabase's migration runner against the production database (--linked or --db-url, not the local default), replace the optional prune_data_older_than() helper, then deploy matching packages and workers together, restoring the exact worker enabled states recorded before the window (see the 0.17.0 upgrade guide). Message ids are exact decimal strings at the JavaScript boundary. Existing mixed-case queue names keep working through their original pgmq spelling - PGMQ's public message API normalizes names, so no message or queue migration is needed.

Patch Changes

• Updated dependencies [01147fe]
  • @pgflow/core@0.17.0

@pgflow/client@0.17.0

Minor Changes

• 01147fe: Persist physical queue identity on steps and tasks. A queued task's message identity is now (queue_name, message_id), not message_id alone, preparing pgflow for private per-step queues while keeping one-flow/one-queue behavior.

  pgflow.steps and pgflow.step_tasks gain a canonical lowercase queue_name (snapshot at task creation), (queue_name, message_id) is unique per queue, and two flows can no longer share a normalized default queue. Breaking: pgflow.start_tasks() now requires the queue_name argument - the queue's canonical identity, lower(flow_slug) today - and the released three-argument form and the NULL default are gone, and startTasks() on IPgflowClient/PgflowSqlClient requires the queue argument as well. pgflow's own workers poll and claim through that canonical name; custom callers must pass it explicitly. There is no mixed-version rolling upgrade: stop and drain workers, pause producers and definition/maintenance/recovery writers, apply the transactional migration through Supabase's migration runner against the production database (--linked or --db-url, not the local default), replace the optional prune_data_older_than() helper, then deploy matching packages and workers together, restoring the exact worker enabled states recorded before the window (see the 0.17.0 upgrade guide). Message ids are exact decimal strings at the JavaScript boundary. Existing mixed-case queue names keep working through their original pgmq spelling - PGMQ's public message API normalizes names, so no message or queue migration is needed.

Patch Changes

• Updated dependencies [01147fe]
  • @pgflow/core@0.17.0
  • @pgflow/dsl@0.17.0

@pgflow/core@0.17.0

Minor Changes

• 01147fe: Persist physical queue identity on steps and tasks. A queued task's message identity is now (queue_name, message_id), not message_id alone, preparing pgflow for private per-step queues while keeping one-flow/one-queue behavior.

  pgflow.steps and pgflow.step_tasks gain a canonical lowercase queue_name (snapshot at task creation), (queue_name, message_id) is unique per queue, and two flows can no longer share a normalized default queue. Breaking: pgflow.start_tasks() now requires the queue_name argument - the queue's canonical identity, lower(flow_slug) today - and the released three-argument form and the NULL default are gone, and startTasks() on IPgflowClient/PgflowSqlClient requires the queue argument as well. pgflow's own workers poll and claim through that canonical name; custom callers must pass it explicitly. There is no mixed-version rolling upgrade: stop and drain workers, pause producers and definition/maintenance/recovery writers, apply the transactional migration through Supabase's migration runner against the production database (--linked or --db-url, not the local default), replace the optional prune_data_older_than() helper, then deploy matching packages and workers together, restoring the exact worker enabled states recorded before the window (see the 0.17.0 upgrade guide). Message ids are exact decimal strings at the JavaScript boundary. Existing mixed-case queue names keep working through their original pgmq spelling - PGMQ's public message API normalizes names, so no message or queue migration is needed.

Patch Changes

• Updated dependencies [01147fe]
  • @pgflow/dsl@0.17.0

@pgflow/dsl@0.17.0

Minor Changes

• 01147fe: Persist physical queue identity on steps and tasks. A queued task's message identity is now (queue_name, message_id), not message_id alone, preparing pgflow for private per-step queues while keeping one-flow/one-queue behavior.

  pgflow.steps and pgflow.step_tasks gain a canonical lowercase queue_name (snapshot at task creation), (queue_name, message_id) is unique per queue, and two flows can no longer share a normalized default queue. Breaking: pgflow.start_tasks() now requires the queue_name argument - the queue's canonical identity, lower(flow_slug) today - and the released three-argument form and the NULL default are gone, and startTasks() on IPgflowClient/PgflowSqlClient requires the queue argument as well. pgflow's own workers poll and claim through that canonical name; custom callers must pass it explicitly. There is no mixed-version rolling upgrade: stop and drain workers, pause producers and definition/maintenance/recovery writers, apply the transactional migration through Supabase's migration runner against the production database (--linked or --db-url, not the local default), replace the optional prune_data_older_than() helper, then deploy matching packages and workers together, restoring the exact worker enabled states recorded before the window (see the 0.17.0 upgrade guide). Message ids are exact decimal strings at the JavaScript boundary. Existing mixed-case queue names keep working through their original pgmq spelling - PGMQ's public message API normalizes names, so no message or queue migration is needed.

@pgflow/edge-worker@0.17.0

Minor Changes

• 01147fe: Persist physical queue identity on steps and tasks. A queued task's message identity is now (queue_name, message_id), not message_id alone, preparing pgflow for private per-step queues while keeping one-flow/one-queue behavior.

  pgflow.steps and pgflow.step_tasks gain a canonical lowercase queue_name (snapshot at task creation), (queue_name, message_id) is unique per queue, and two flows can no longer share a normalized default queue. Breaking: pgflow.start_tasks() now requires the queue_name argument - the queue's canonical identity, lower(flow_slug) today - and the released three-argument form and the NULL default are gone, and startTasks() on IPgflowClient/PgflowSqlClient requires the queue argument as well. pgflow's own workers poll and claim through that canonical name; custom callers must pass it explicitly. There is no mixed-version rolling upgrade: stop and drain workers, pause producers and definition/maintenance/recovery writers, apply the transactional migration through Supabase's migration runner against the production database (--linked or --db-url, not the local default), replace the optional prune_data_older_than() helper, then deploy matching packages and workers together, restoring the exact worker enabled states recorded before the window (see the 0.17.0 upgrade guide). Message ids are exact decimal strings at the JavaScript boundary. Existing mixed-case queue names keep working through their original pgmq spelling - PGMQ's public message API normalizes names, so no message or queue migration is needed.

Patch Changes

• Updated dependencies [01147fe]
  • @pgflow/core@0.17.0
  • @pgflow/dsl@0.17.0

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 87e72f7

Command	Status	Duration	Result
nx run-many -t build --projects=dsl,core,cli	✅ Succeeded	6s	View ↗

💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗

---

☁️ Nx Cloud last updated this comment at 2026-09-14 14:23:34 UTC