Skip to content

Version Packages - #687

Merged
jumski merged 1 commit into
mainfrom
changeset-release/main
Oct 1, 2026
Merged

jumski merged 1 commit into
mainfrom
changeset-release/main

Conversation

@jumski

@jumski jumski commented Sep 19, 2026 •

Copy link
Copy Markdown
Contributor

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.1

Patch Changes

  • e3262ad: Report anonymous fresh, update, or no-op install completion telemetry with the pgflow version and a bucketed migration count. CI, tests, DO_NOT_TRACK, and PGFLOW_TELEMETRY_DISABLED disable the event.
  • Updated dependencies [4f7f279]
  • Updated dependencies [7cb6808]
    • @pgflow/core@0.17.1

@pgflow/client@0.17.1

Patch Changes

  • Updated dependencies [4f7f279]
  • Updated dependencies [7cb6808]
    • @pgflow/core@0.17.1
    • @pgflow/dsl@0.17.1

@pgflow/core@0.17.1

Patch Changes

  • 4f7f279: Add anonymous, opt-out telemetry. A daily pg_cron job aggregates yesterday's pgflow.* activity into coarse, identifier-free buckets (versions in use, run and worker counts, flow shapes, feature adoption, durations) and sends one small payload through pg_net to a Cloudflare Worker backed by Workers Analytics Engine. Workers stamp their package version at registration. Nothing identifying is ever sent; every payload is stored locally in pgflow_telemetry.sent_reports for audit; pgflow_telemetry.preview() shows any day's payload without sending; pgflow_telemetry.disable() opts out permanently (the cron job row is the switch) and local development databases never report.
  • 7cb6808: Fix force-skip consuming only the first queue's archived messages when active tasks span multiple private step queues, and stop assert_step_queue_available() from reporting an owned route as available when its PGMQ queue is missing.
    • @pgflow/dsl@0.17.1

@pgflow/edge-worker@0.17.1

Patch Changes

  • 4f7f279: Add anonymous, opt-out telemetry. A daily pg_cron job aggregates yesterday's pgflow.* activity into coarse, identifier-free buckets (versions in use, run and worker counts, flow shapes, feature adoption, durations) and sends one small payload through pg_net to a Cloudflare Worker backed by Workers Analytics Engine. Workers stamp their package version at registration. Nothing identifying is ever sent; every payload is stored locally in pgflow_telemetry.sent_reports for audit; pgflow_telemetry.preview() shows any day's payload without sending; pgflow_telemetry.disable() opts out permanently (the cron job row is the switch) and local development databases never report.
  • Updated dependencies [4f7f279]
  • Updated dependencies [7cb6808]
    • @pgflow/core@0.17.1
    • @pgflow/dsl@0.17.1

@pgflow/dsl@0.17.1

@nx-cloud

nx-cloud Bot commented Sep 19, 2026 •

Copy link
Copy Markdown

View your CI Pipeline Execution ↗ for commit dad1630

Command Status Duration Result
nx run client:e2e ✅ Succeeded 4m 23s View ↗
nx run core:pgtap ✅ Succeeded 3m 6s View ↗
nx run edge-worker:e2e:portable-runtimes ✅ Succeeded 2m 23s View ↗
nx affected -t verify-exports --base=origin/mai... ✅ Succeeded 3s View ↗
nx affected -t build --configuration=production... ✅ Succeeded 2s View ↗
nx affected -t lint typecheck test --parallel -... ✅ Succeeded 1m 32s View ↗
nx run edge-worker:test:integration ✅ Succeeded 1m 47s View ↗
nx run edge-worker:e2e ✅ Succeeded 2m 13s View ↗
Additional runs (2) ✅ Succeeded ... View ↗

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


☁️ Nx Cloud last updated this comment at 2026-10-01 17:46:34 UTC

@jumski
jumski force-pushed the changeset-release/main branch 2 times, most recently from 1c0b85e to dad1630 Compare September 23, 2026 11:04
jumski added a commit that referenced this pull request Oct 1, 2026
The portable-runtime e2e job timed out on four changeset-release/main CI
runs (PR #687 and predecessors) with only 'Timeout after 60000ms waiting
for test_seq to increment by 200'. The same suite passes locally on both
the base commit and the exact release diff, so the runner-side evidence
lives in the supabase functions serve log — which run-e2e.sh keeps in a
mktemp file that GitHub Actions never prints.

Print the server log to stderr from run_with_functions_server when the
monitored command fails, so the next CI failure carries worker errors
(isolate CPU-limit shutdowns, forced sql close) instead of a bare timeout.
Successful suites stay silent to avoid megabytes of noise.

Extend the functions-server self-test: failing suite dumps the log,
passing suite produces no stderr, exit statuses unchanged.

Co-authored-by: Agent <agent@pgflow.dev>
@jumski
jumski force-pushed the changeset-release/main branch from dad1630 to 83dec53 Compare October 1, 2026 17:38
@jumski
jumski merged commit 1f8edde into main Oct 1, 2026
15 checks passed
@github-actions

github-actions Bot commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

🚀 Production Deployment: Website

✅ Successfully deployed to production!

🔗 Production URL: https://pgflow.dev

📝 Details:

  • Commit: 1f8edde03d7cc6bc7985f6f74af70adf04024dca
  • View Logs

Deployed at: 2026-10-01T19:47:49+02:00

This branch was successfully deployed

1 active deployment
preview — 83dec53d Deployed Oct 1, 2026 by jumski via deploy-website #3412
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant