Skip to content

Version Packages (beta)#2859

Merged
karthikscale3 merged 1 commit into
mainfrom
changeset-release/main
Jul 10, 2026
Merged

Version Packages (beta)#2859
karthikscale3 merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 9, 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.

⚠️⚠️⚠️⚠️⚠️⚠️

main is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on main.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@workflow/core@5.0.0-beta.30

Minor Changes

  • #2850 f28150c Thanks @karthikscale3! - Report step progress alongside step-to-step overhead latency telemetry.

  • #2872 36c63af Thanks @mitul-s! - Record the source run on replays: recreateRunFromExisting now stamps replayedFromRunId into the new run's executionContext (and start accepts a matching option) so tooling can surface a run as a replay and link back to its origin.

Patch Changes

  • #2790 145835b Thanks @NathanColosimo! - Centralize workflow event type classifiers and event-data payload field helpers.

  • #2687 9958424 Thanks @Osamaali313! - Fix extractStreamIds overflowing the stack on circular references. The hydrated observability data it walks comes from devalue, which preserves circular and repeated references, so a step result containing a cycle would crash run inspection (wf inspect and the web dashboard) with a RangeError. The traversal now tracks visited containers and skips cycles.

  • #2848 6603628 Thanks @VaguelySerious! - Fix duplicate inline step execution when a hook or wait wakes a run while the step is still running (A hook_received while a step attempt is in flight re-dispatches the step; both attempts run concurrently in-process #2780). The lazy step_started now records the owning queue message ID, and wake replays schedule a delayed backstop for in-flight inline steps instead of immediately re-dispatching them. Disable with WORKFLOW_INLINE_OWNERSHIP=0.

  • #2874 48fcc4e Thanks @karthikscale3! - Add a namespace option to start(), recreateRunFromExisting(), reenqueueRun(), and wakeUpRun() for targeting deployments with namespaced queue topics, and make healthCheck() respect its timeout when the stream read hangs.

  • #2857 2c6ee61 Thanks @karthikscale3! - Add stream latency to OTEL spans

  • Updated dependencies [f28150c, 84df8f3, 4dce2ae, 145835b, 6603628, 2c6ee61]:

    • @workflow/world@5.0.0-beta.18
    • @workflow/world-vercel@5.0.0-beta.26
    • @workflow/world-local@5.0.0-beta.26
    • @workflow/errors@5.0.0-beta.10

@workflow/world@5.0.0-beta.18

Minor Changes

Patch Changes

@workflow/world-vercel@5.0.0-beta.26

Minor Changes

Patch Changes

@workflow/astro@5.0.0-beta.30

Patch Changes

  • Updated dependencies [df7e71d, 25b1509]:
    • @workflow/builders@5.0.0-beta.30
    • @workflow/rollup@5.0.0-beta.30
    • @workflow/vite@5.0.0-beta.30

@workflow/builders@5.0.0-beta.30

Patch Changes

  • #2853 df7e71d Thanks @NathanColosimo! - Use the Windows-safe generated-file writer for step registration output.

  • #1947 25b1509 Thanks @VaguelySerious! - Externalize the optional @opentelemetry/api peer in the Rollup/Vite framework builds (SvelteKit, Nitro, Nuxt, Astro, Vite) only when it isn't installed, so a build no longer fails with "failed to resolve import '@opentelemetry/api'". When the peer is present it is bundled/resolved as before, so tracing keeps working — including in self-contained outputs like Nitro's .output/server.

  • Updated dependencies [f28150c, 84df8f3, 4dce2ae, 145835b, 9958424, 6603628, 48fcc4e, 36c63af, 2c6ee61]:

    • @workflow/core@5.0.0-beta.30
    • @workflow/world-vercel@5.0.0-beta.26
    • @workflow/world-local@5.0.0-beta.26
    • @workflow/errors@5.0.0-beta.10

@workflow/cli@5.0.0-beta.30

Patch Changes

@workflow/nest@5.0.0-beta.30

Patch Changes

  • Updated dependencies [df7e71d, 25b1509]:
    • @workflow/builders@5.0.0-beta.30

@workflow/next@5.0.0-beta.30

Patch Changes

@workflow/nitro@5.0.0-beta.30

Patch Changes

@workflow/nuxt@5.0.0-beta.30

Patch Changes

  • Updated dependencies [df7e71d, 25b1509]:
    • @workflow/builders@5.0.0-beta.30
    • @workflow/nitro@5.0.0-beta.30

@workflow/rollup@5.0.0-beta.30

Patch Changes

  • #1947 25b1509 Thanks @VaguelySerious! - Externalize the optional @opentelemetry/api peer in the Rollup/Vite framework builds (SvelteKit, Nitro, Nuxt, Astro, Vite) only when it isn't installed, so a build no longer fails with "failed to resolve import '@opentelemetry/api'". When the peer is present it is bundled/resolved as before, so tracing keeps working — including in self-contained outputs like Nitro's .output/server.

  • Updated dependencies [df7e71d, 25b1509]:

    • @workflow/builders@5.0.0-beta.30

@workflow/sveltekit@5.0.0-beta.30

Patch Changes

  • Updated dependencies [df7e71d, 25b1509]:
    • @workflow/builders@5.0.0-beta.30
    • @workflow/rollup@5.0.0-beta.30
    • @workflow/vite@5.0.0-beta.30

@workflow/vite@5.0.0-beta.30

Patch Changes

  • Updated dependencies [df7e71d, 25b1509]:
    • @workflow/builders@5.0.0-beta.30

@workflow/vitest@5.0.0-beta.30

Patch Changes

@workflow/web@5.0.0-beta.30

Patch Changes

@workflow/web-shared@5.0.0-beta.30

Patch Changes

workflow@5.0.0-beta.30

Patch Changes

  • Updated dependencies [f28150c, 145835b, 9958424, 6603628, 48fcc4e, 25b1509, 36c63af, 2c6ee61]:
    • @workflow/core@5.0.0-beta.30
    • @workflow/cli@5.0.0-beta.30
    • @workflow/rollup@5.0.0-beta.30
    • @workflow/astro@5.0.0-beta.30
    • @workflow/nest@5.0.0-beta.30
    • @workflow/next@5.0.0-beta.30
    • @workflow/nitro@5.0.0-beta.30
    • @workflow/nuxt@5.0.0-beta.30
    • @workflow/sveltekit@5.0.0-beta.30
    • @workflow/typescript-plugin@5.0.0-beta.5
    • @workflow/errors@5.0.0-beta.10

@workflow/world-local@5.0.0-beta.26

Patch Changes

@workflow/world-postgres@5.0.0-beta.24

Patch Changes

@workflow/world-testing@5.0.0-beta.30

Patch Changes

@github-actions github-actions Bot requested review from a team and ijjk as code owners July 9, 2026 16:26
@vercel

vercel Bot commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
example-nextjs-workflow-turbopack Ready Ready Preview, Comment Jul 10, 2026 9:56pm
example-nextjs-workflow-webpack Ready Ready Preview, Comment Jul 10, 2026 9:56pm
example-workflow Ready Ready Preview, Comment Jul 10, 2026 9:56pm
workbench-astro-workflow Ready Ready Preview, Comment Jul 10, 2026 9:56pm
workbench-express-workflow Ready Ready Preview, Comment Jul 10, 2026 9:56pm
workbench-fastify-workflow Ready Ready Preview, Comment Jul 10, 2026 9:56pm
workbench-hono-workflow Ready Ready Preview, Comment Jul 10, 2026 9:56pm
workbench-nitro-workflow Ready Ready Preview, Comment Jul 10, 2026 9:56pm
workbench-nuxt-workflow Ready Ready Preview, Comment Jul 10, 2026 9:56pm
workbench-sveltekit-workflow Ready Ready Preview, Comment Jul 10, 2026 9:56pm
workbench-tanstack-start-workflow Ready Ready Preview, Comment Jul 10, 2026 9:56pm
workbench-vite-workflow Ready Ready Preview, Comment Jul 10, 2026 9:56pm
workflow-docs Ready Ready Preview, Comment, Open in v0 Jul 10, 2026 9:56pm
workflow-swc-playground Ready Ready Preview, Comment Jul 10, 2026 9:56pm
workflow-tarballs Ready Ready Preview, Comment Jul 10, 2026 9:56pm
workflow-web Ready Ready Preview, Comment Jul 10, 2026 9:56pm

@github-actions github-actions Bot closed this Jul 9, 2026
@github-actions github-actions Bot force-pushed the changeset-release/main branch from 792b3d3 to f28150c Compare July 9, 2026 18:38
@github-actions github-actions Bot reopened this Jul 9, 2026
@github-actions github-actions Bot closed this Jul 9, 2026
@github-actions github-actions Bot force-pushed the changeset-release/main branch from 73c4bbe to df7e71d Compare July 9, 2026 22:58
@github-actions github-actions Bot reopened this Jul 9, 2026
@github-actions

github-actions Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor Author

📊 Workflow Benchmarks

commit 8b91d0f · Fri, 10 Jul 2026 22:12:23 GMT · run logs

Backend: vercel · app: nextjs-turbopack

Metric Scenario Avg (ms) P75 (ms) P90 (ms) P99 (ms) Samples
TTFS stream 1363 (+29%) 1740 🔴 1764 🔴 2217 🔴 30
TTFS hook + stream 1611 (+25%) 1894 🔴 2000 🔴 2283 🔴 30
STSO 1020 steps (1-20) 286 (+8.1%) 325 🔴 478 🔴 602 🔴 19
STSO 1020 steps (101-120) 385 (-2.8%) 418 🔴 467 🔴 493 🔴 19
STSO 1020 steps (1001-1020) 842 (-13%) 859 🔴 995 🔴 1110 🔴 19
WO stream 1363 (+29%) 1740 1764 2217 30
WO hook + stream 1611 (+25%) 1894 2000 2283 30
SL stream 4832 (+3.0%) 5622 🔴 5741 🔴 5816 🔴 30
SL hook + stream 5009 (+2.8%) 5574 🔴 5712 🔴 5836 🔴 30
📜 Previous results (1)

8edd05c

Fri, 10 Jul 2026 20:20:28 GMT · run logs

vercel / nextjs-turbopack

Metric Scenario Avg (ms) P75 (ms) P90 (ms) P99 (ms) Samples
TTFS stream 1271 (+9.4%) 1741 🔴 1971 🔴 2400 🔴 30
TTFS hook + stream 1589 (+26%) 1964 🔴 2029 🔴 2176 🔴 30
STSO 1020 steps (1-20) 288 (+14%) 335 🔴 429 🔴 459 🔴 19
STSO 1020 steps (101-120) 464 (-5.0%) 479 🔴 621 🔴 885 🔴 19
STSO 1020 steps (1001-1020) 901 (+4.3%) 935 🔴 1117 🔴 1142 🔴 19
WO stream 1271 (+9.4%) 1741 1971 2400 30
WO hook + stream 1589 (+26%) 1964 2029 2176 30
SL stream 4645 (-6.1%) 5755 🔴 5945 🔴 6107 🔴 30
SL hook + stream 4958 (+0.7%) 5492 🔴 5688 🔴 5910 🔴 30

Avg deltas compare against the most recent benchmark run on main at the time of this run.

Metrics — TTFS: time to first step body execution · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (time outside step bodies, client start → last step body exit) · SL: stream latency (first chunk write → visible to the reader)

Scenarios — stream: one step that streams chunks back to the client; no hooks, so the run stays in turbo mode · hook + stream: registers a hook before the same streaming step, which exits turbo mode · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges

🟢/🔴 mark percentiles within/above target. Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · STSO (1-20) 20/30/60 · STSO (101-120) 30/45/90 · STSO (1001-1020) 40/60/120

TTFS/WO compare client vs deployment clocks and SL compares the step runner’s clock vs the client’s (NTP-synced in CI). WO ends at the last step body exit, the closest observable proxy for the final step-completion request.

@github-actions

github-actions Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor Author

🧪 E2E Test Results

All tests passed

Summary

Passed Failed Skipped Total
✅ ▲ Vercel Production 1453 0 230 1683
✅ 💻 Local Development 1483 0 200 1683
✅ 📦 Local Production 1617 0 219 1836
✅ 🐘 Local Postgres 1617 0 219 1836
✅ 🪟 Windows 153 0 0 153
✅ 📋 Other 894 0 177 1071
Total 7217 0 1045 8262

Details by Category

✅ ▲ Vercel Production
App Passed Failed Skipped
✅ astro 126 0 27
✅ example 126 0 27
✅ express 126 0 27
✅ fastify 126 0 27
✅ hono 126 0 27
✅ nextjs-turbopack 150 0 3
✅ nextjs-webpack 150 0 3
✅ nitro 126 0 27
✅ nuxt 126 0 27
✅ sveltekit 145 0 8
✅ vite 126 0 27
✅ 💻 Local Development
App Passed Failed Skipped
✅ astro-stable 128 0 25
✅ express-stable 128 0 25
✅ fastify-stable 128 0 25
✅ hono-stable 128 0 25
✅ nextjs-turbopack-canary 134 0 19
✅ nextjs-turbopack-stable 153 0 0
✅ nextjs-webpack-stable 153 0 0
✅ nitro-stable 128 0 25
✅ nuxt-stable 128 0 25
✅ sveltekit-stable 147 0 6
✅ vite-stable 128 0 25
✅ 📦 Local Production
App Passed Failed Skipped
✅ astro-stable 128 0 25
✅ express-stable 128 0 25
✅ fastify-stable 128 0 25
✅ hono-stable 128 0 25
✅ nextjs-turbopack-canary 134 0 19
✅ nextjs-turbopack-stable 153 0 0
✅ nextjs-webpack-canary 134 0 19
✅ nextjs-webpack-stable 153 0 0
✅ nitro-stable 128 0 25
✅ nuxt-stable 128 0 25
✅ sveltekit-stable 147 0 6
✅ vite-stable 128 0 25
✅ 🐘 Local Postgres
App Passed Failed Skipped
✅ astro-stable 128 0 25
✅ express-stable 128 0 25
✅ fastify-stable 128 0 25
✅ hono-stable 128 0 25
✅ nextjs-turbopack-canary 134 0 19
✅ nextjs-turbopack-stable 153 0 0
✅ nextjs-webpack-canary 134 0 19
✅ nextjs-webpack-stable 153 0 0
✅ nitro-stable 128 0 25
✅ nuxt-stable 128 0 25
✅ sveltekit-stable 147 0 6
✅ vite-stable 128 0 25
✅ 🪟 Windows
App Passed Failed Skipped
✅ nextjs-turbopack 153 0 0
✅ 📋 Other
App Passed Failed Skipped
✅ e2e-local-dev-nest-stable 128 0 25
✅ e2e-local-dev-tanstack-start- 128 0 25
✅ e2e-local-postgres-nest-stable 128 0 25
✅ e2e-local-postgres-tanstack-start- 128 0 25
✅ e2e-local-prod-nest-stable 128 0 25
✅ e2e-local-prod-tanstack-start- 128 0 25
✅ e2e-vercel-prod-tanstack-start 126 0 27

📋 View full workflow run


Some E2E test jobs failed:

  • Vercel Prod: success
  • Local Dev: failure
  • Local Prod: success
  • Local Postgres: success
  • Windows: success

Check the workflow run for details.

@github-actions

Copy link
Copy Markdown
Contributor Author

No backport to stable for 5de1b7a (AI decision).

This is a Changesets-generated "Version Packages (beta)" release-plumbing commit that only bumps package versions, updates CHANGELOG.md files, and prunes .changeset/pre.json. It contains no functional code changes and produces beta prereleases specific to the main pre-release channel, so it should not be backported to stable.

To override, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

5de1b7a100ed340221d5fae9f955e845c719e018

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