Skip to content

Version Packages (beta) - #3087

Merged
TooTallNate merged 1 commit into
mainfrom
changeset-release/main
Jul 29, 2026
Merged

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

Conversation

@github-actions

@github-actionsgithub-actionsBot commented Jul 24, 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/cli@5.0.0-beta.37

Major Changes

  • #306162d570e Thanks @NathanColosimo! - Remove the standalone step URL API and stale generated route artifacts while keeping step registrations inside the combined flow output.

Patch Changes

@workflow/core@5.0.0-beta.37

Major Changes

  • #31287959acc Thanks @NathanColosimo! - BREAKING CHANGE: Remove the deprecated experimental_setAttributes and ExperimentalSetAttributesOptions aliases; use setAttributes and SetAttributesOptions instead.

  • #31124ada27d Thanks @NathanColosimo! - Remove deprecated world-specific factory aliases in favor of createWorld.

  • #306162d570e Thanks @NathanColosimo! - Remove the retired step route runtime and make queue health checks target the combined flow handler.

  • #3045d813fb8 Thanks @NathanColosimo! - Deterministic sandbox hardening: crypto.subtle.digest in workflow functions now computes synchronously via node:crypto (byte-identical values, deterministic timing under replay); Atomics.waitAsync, async WebAssembly compilation, WeakRef, and FinalizationRegistry are no longer exposed (wall-clock timing and GC observation cannot be replayed).

Minor Changes

  • #30988a95d36 Thanks @TooTallNate! - Carry the owning run's public key in forwarded WritableStream descriptors, so a run writing into another run's stream seals frames with no run fetch and no key-API round trip.

  • #3146e8bc7d6 Thanks @TooTallNate! - Let observability tooling decrypt sealed (encp) payloads: key resolution now yields the run's full key capability, and hydrateDataWithKey dispatches on the envelope format.

  • #30947a65030 Thanks @TooTallNate! - Teach the serialization layer to read and write encp sealed envelopes via a PayloadKey union, so a cross-run writer can encrypt with only a public key. Existing symmetric call sites are unaffected.

  • #30960b1ca15 Thanks @TooTallNate! - resumeHook() now seals its payload to the target run's published public key when one is present, removing the cross-deployment run-key API round trip from hook resumption. Readers resolve the full key capability so they can open sealed payloads.

  • #3095b4ba79e Thanks @TooTallNate! - Derive each run's X25519 public key at start() and stamp it on the run, so cross-run writers can seal payloads to the run without fetching its symmetric key.

  • #30934ba223a Thanks @TooTallNate! - Add the encp sealed-box encryption primitive: X25519 keypairs derived from the existing per-run key material, letting cross-run writers encrypt with only a public key. Not yet wired into any write path.

  • #3099a86035f Thanks @TooTallNate! - The cross-deployment capability probe now returns the target run's public key, letting start() seal workflow arguments without a separate key-lookup request.

Patch Changes

  • #31118c12358 Thanks @NathanColosimo! - Clarify runtime invariants and compression behavior.

  • #3155b8bcded Thanks @TooTallNate! - Seal forwarded writes to streams taken with getWritable() in a workflow body, which previously fell back to fetching the owner's symmetric key because the workflow VM has no key material to publish on the handle.

  • #3125d24c91c Thanks @karthikscale3! - Hooks can carry an optional resumeContext; when present, resumeHook/resumeWebhook resume from it directly instead of fetching the full run, saving a round trip per resume. When the context also carries the run's encryptionPublicKey, the resume seals its payload (encp) directly to that key, so a default webhook resume needs neither a run read nor a run-key lookup. These two optimizations fall back independently: it fetches the full run when the context is absent, and uses symmetric encryption when no usable public key is available.

  • #3069fd05393 Thanks @TooTallNate! - Fix a false "exceeded max retries" run failure: the retry-ceiling guard counted duplicate step_started events written by invocations racing on the same pending batch as real attempts. The owned-recovery ceiling now counts only the owning message's own starts, and the background-step ceiling counts only bare (queue-delivered) starts.

  • #3088fc81f45 Thanks @karthikscale3! - Stream writes dispatch the first chunk of an idle stream immediately (flush window default 0 instead of 10ms). Fast producers keep full batching via in-flight accumulation; set streamFlushIntervalMs (World option) or WORKFLOW_STREAM_FLUSH_INTERVAL_MS (env, takes precedence) above 0 to opt into a windowed leading edge.

  • #3131d7553c4 Thanks @NathanColosimo! - Avoid rescanning already prewarmed replay payloads during inline replays.

  • #31105d17c60 Thanks @NathanColosimo! - Consolidate runtime event merging logic.

  • #31392941b1c Thanks @pranaygp! - Deliver step results, wait completions, hook payloads and aborts in strict event-log order relative to one another, preventing replay divergence (CORRUPTED_EVENT_LOG) when a step completion is adjacent in the log to a wait_completed, hook_received or abort that a concurrent branch is awaiting.

  • #3078b610c46 Thanks @karthikscale3! - Stream write batching now lives in the server writable itself (group commit), so raw ReadableStreams piped across workflow/step boundaries batch the same as getWritable() instead of sending one request per chunk.

  • Updated dependencies [8c12358, b4ba79e, a86035f, d24c91c, 313a074, fc81f45, 49276f2, 49276f2, 4ada27d, 62d570e, 62d570e, 62d570e, 49276f2]:

    • @workflow/world@5.0.0-beta.23
    • @workflow/world-vercel@5.0.0-beta.33
    • @workflow/world-local@5.0.0-beta.31
    • @workflow/utils@5.0.0-beta.7
    • @workflow/errors@5.0.0-beta.13

@workflow/utils@5.0.0-beta.7

Major Changes

  • #306162d570e Thanks @NathanColosimo! - Remove the standalone step URL API and stale generated route artifacts while keeping step registrations inside the combined flow output.

Patch Changes

  • #314449276f2 Thanks @VaguelySerious! - Select the Vercel World for builds that target Vercel without a deployment ID, such as vercel build followed by vercel deploy --prebuilt, and apply workflows.local.port whenever the Local World is the target.

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

Major Changes

Patch Changes

  • #3146e8bc7d6 Thanks @TooTallNate! - Let observability tooling decrypt sealed (encp) payloads: key resolution now yields the run's full key capability, and hydrateDataWithKey dispatches on the envelope format.

  • #3095b4ba79e Thanks @TooTallNate! - Hide the run's encryptionPublicKey in the attribute panel — internal encryption plumbing, not user-facing.

  • #3125d24c91c Thanks @karthikscale3! - Hooks can carry an optional resumeContext; when present, resumeHook/resumeWebhook resume from it directly instead of fetching the full run, saving a round trip per resume. When the context also carries the run's encryptionPublicKey, the resume seals its payload (encp) directly to that key, so a default webhook resume needs neither a run read nor a run-key lookup. These two optimizations fall back independently: it fetches the full run when the context is absent, and uses symmetric encryption when no usable public key is available.

  • #306045a56a3 Thanks @mitul-s! - Animate the new trace viewer's zoom controls consistently with span focus.

  • Updated dependencies [8c12358, 8a95d36, e8bc7d6, 7a65030, 0b1ca15, b4ba79e, b4ba79e, 4ba223a, a86035f, b8bcded, d24c91c, fd05393, fc81f45, 49276f2, d7553c4, 5d17c60, 7959acc, 4ada27d, 62d570e, 62d570e, 62d570e, 2941b1c, d813fb8, b610c46]:

    • @workflow/core@5.0.0-beta.37
    • @workflow/world@5.0.0-beta.23
    • @workflow/utils@5.0.0-beta.7

workflow@5.0.0-beta.37

Major Changes

  • #31287959acc Thanks @NathanColosimo! - BREAKING CHANGE: Remove the deprecated experimental_setAttributes and ExperimentalSetAttributesOptions aliases; use setAttributes and SetAttributesOptions instead.

  • #306162d570e Thanks @NathanColosimo! - Remove the retired step route runtime and make queue health checks target the combined flow handler.

  • #3045d813fb8 Thanks @NathanColosimo! - Deterministic sandbox hardening: crypto.subtle.digest in workflow functions now computes synchronously via node:crypto (byte-identical values, deterministic timing under replay); Atomics.waitAsync, async WebAssembly compilation, WeakRef, and FinalizationRegistry are no longer exposed (wall-clock timing and GC observation cannot be replayed).

Patch Changes

@workflow/world@5.0.0-beta.23

Major Changes

  • #306162d570e Thanks @NathanColosimo! - Remove legacy step queue topics and payloads now that queued steps use the workflow topic and combined flow handler.

Minor Changes

  • #3095b4ba79e Thanks @TooTallNate! - Persist and transport the new optional encryptionPublicKey field on workflow runs, carried on run_created (and run_started for resilient start).

  • #3099a86035f Thanks @TooTallNate! - The cross-deployment capability probe now returns the target run's public key, letting start() seal workflow arguments without a separate key-lookup request.

Patch Changes

  • #31118c12358 Thanks @NathanColosimo! - Clarify runtime invariants and compression behavior.

  • #3125d24c91c Thanks @karthikscale3! - Hooks can carry an optional resumeContext; when present, resumeHook/resumeWebhook resume from it directly instead of fetching the full run, saving a round trip per resume. When the context also carries the run's encryptionPublicKey, the resume seals its payload (encp) directly to that key, so a default webhook resume needs neither a run read nor a run-key lookup. These two optimizations fall back independently: it fetches the full run when the context is absent, and uses symmetric encryption when no usable public key is available.

  • #3088fc81f45 Thanks @karthikscale3! - Stream writes dispatch the first chunk of an idle stream immediately (flush window default 0 instead of 10ms). Fast producers keep full batching via in-flight accumulation; set streamFlushIntervalMs (World option) or WORKFLOW_STREAM_FLUSH_INTERVAL_MS (env, takes precedence) above 0 to opt into a windowed leading edge.

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

Major Changes

Minor Changes

  • #3095b4ba79e Thanks @TooTallNate! - Persist and transport the new optional encryptionPublicKey field on workflow runs, carried on run_created (and run_started for resilient start).

Patch Changes

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

Major Changes

  • #306162d570e Thanks @NathanColosimo! - Remove legacy step queue topics and payloads now that queued steps use the workflow topic and combined flow handler.

Minor Changes

  • #3095b4ba79e Thanks @TooTallNate! - Add an encryption_public_key column to workflow_runs (migration 0016) to store each run's X25519 public key.

Patch Changes

  • #3064cdb3db4 Thanks @joeyhotz! - On shutdown, abort stalled workflow and step HTTP deliveries after Graphile Worker's grace period so their Postgres job rows are unlocked through normal failure handling instead of waiting for stale-lock recovery; aborted deliveries still consume an attempt and retry only when budget remains. Add opt-in application-managed shutdown through applicationManagedShutdown or WORKFLOW_POSTGRES_APPLICATION_MANAGED_SHUTDOWN=1 so applications can await world.close() before closing their HTTP server and caller-owned pool.

  • #3125d24c91c Thanks @karthikscale3! - Hooks can carry an optional resumeContext; when present, resumeHook/resumeWebhook resume from it directly instead of fetching the full run, saving a round trip per resume. When the context also carries the run's encryptionPublicKey, the resume seals its payload (encp) directly to that key, so a default webhook resume needs neither a run read nor a run-key lookup. These two optimizations fall back independently: it fetches the full run when the context is absent, and uses symmetric encryption when no usable public key is available.

  • Updated dependencies [8c12358, b4ba79e, a86035f, d24c91c, fc81f45, 49276f2, 49276f2, 4ada27d, 62d570e, 62d570e, 62d570e]:

    • @workflow/world@5.0.0-beta.23
    • @workflow/world-local@5.0.0-beta.31
    • @workflow/utils@5.0.0-beta.7
    • @workflow/errors@5.0.0-beta.13

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

Major Changes

Minor Changes

  • #3095b4ba79e Thanks @TooTallNate! - Persist and transport the new optional encryptionPublicKey field on workflow runs, carried on run_created (and run_started for resilient start).

  • #3099a86035f Thanks @TooTallNate! - The cross-deployment capability probe now returns the target run's public key, letting start() seal workflow arguments without a separate key-lookup request.

Patch Changes

  • #31118c12358 Thanks @NathanColosimo! - Clarify runtime invariants and compression behavior.

  • #3062313a074 Thanks @karthikscale3! - Add WORKFLOW_DISABLE_ANALYTICS_READS=1 to opt the world's analytics read namespace off, forcing workflow inspect list paths onto strongly consistent primary storage. Intended for tests and tooling that read entities immediately after writing them, where the analytics store's asynchronous ingestion can return stale pages.

  • #314449276f2 Thanks @VaguelySerious! - Explain how to fix a build targeting the Vercel World that runs outside a Vercel deployment, where VERCEL_DEPLOYMENT_ID is missing.

  • Updated dependencies [8c12358, b4ba79e, a86035f, d24c91c, fc81f45, 62d570e, 62d570e]:

    • @workflow/world@5.0.0-beta.23
    • @workflow/errors@5.0.0-beta.13

@workflow/builders@5.0.0-beta.37

Minor Changes

  • #3054cfe7570 Thanks @VaguelySerious! - Add a discoverWorkflowsInNodeModules option (and WORKFLOW_DISCOVER_NODE_MODULES env var) to stop workflow discovery from descending into node_modules, skipping the cost of scanning third-party dependencies for workflow/step/serde code.

Patch Changes

@workflow/astro@5.0.0-beta.37

Patch Changes

  • #31660d6ec43 Thanks @TooTallNate! - The generated webhook route now passes the incoming request directly to its handler instead of copying it into a new Request, so the request body is no longer read before the handler runs.

  • Updated dependencies [cfe7570, b406a04, 62d570e]:

    • @workflow/builders@5.0.0-beta.37
    • @workflow/rollup@5.0.0-beta.37
    • @workflow/vite@5.0.0-beta.37

@workflow/errors@5.0.0-beta.13

Patch Changes

  • #306162d570e Thanks @NathanColosimo! - Remove the retired step route runtime and make queue health checks target the combined flow handler.

  • Updated dependencies [49276f2, 62d570e]:

    • @workflow/utils@5.0.0-beta.7

@workflow/nest@5.0.0-beta.37

Patch Changes

@workflow/next@5.0.0-beta.37

Patch Changes

@workflow/nitro@5.0.0-beta.37

Patch Changes

@workflow/nuxt@5.0.0-beta.37

Patch Changes

  • Updated dependencies [cfe7570, b406a04, 62d570e]:
    • @workflow/builders@5.0.0-beta.37
    • @workflow/nitro@5.0.0-beta.37

@workflow/rollup@5.0.0-beta.37

Patch Changes

@workflow/sveltekit@5.0.0-beta.37

Patch Changes

  • #31660d6ec43 Thanks @TooTallNate! - The generated webhook route now passes the incoming request directly to its handler instead of copying it into a new Request, so the request body is no longer read before the handler runs.

  • Updated dependencies [cfe7570, b406a04, 62d570e]:

    • @workflow/builders@5.0.0-beta.37
    • @workflow/rollup@5.0.0-beta.37
    • @workflow/vite@5.0.0-beta.37

@workflow/vite@5.0.0-beta.37

Patch Changes

@workflow/vitest@5.0.0-beta.37

Patch Changes

@workflow/web@5.0.0-beta.37

Patch Changes

  • #3146e8bc7d6 Thanks @TooTallNate! - Let observability tooling decrypt sealed (encp) payloads: key resolution now yields the run's full key capability, and hydrateDataWithKey dispatches on the envelope format.

  • #306162d570e Thanks @NathanColosimo! - Check only the combined workflow endpoint in the observability health check.

  • Updated dependencies [b4ba79e, 49276f2, 4ada27d, 62d570e]:

    • @workflow/world-local@5.0.0-beta.31

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

Patch Changes

@github-actions
github-actionsBot requested review from a team and ijjk as code ownersJuly 24, 2026 18:30
@vercel

vercelBot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

@github-actions
github-actionsBotforce-pushed the changeset-release/main branch from c9f67d0 to fc81f45CompareJuly 24, 2026 19:30
@github-actionsgithub-actionsBot reopened this Jul 24, 2026
@github-actions
github-actionsBotforce-pushed the changeset-release/main branch from f983d07 to 3069b49CompareJuly 24, 2026 21:31
@github-actionsgithub-actionsBot reopened this Jul 24, 2026
@github-actions
github-actionsBotforce-pushed the changeset-release/main branch from b36a5ee to 706b6c4CompareJuly 24, 2026 22:22
@github-actionsgithub-actionsBot reopened this Jul 24, 2026
@github-actions

github-actionsBot commented Jul 27, 2026

Copy link
Copy Markdown
ContributorAuthor

🧪 E2E Test Results

All tests passed

E2E Test Summary

Summary
PassedFailedSkippedTotal
✅ ▲ Vercel Production145502391694
✅ 💻 Local Development162102271848
✅ 📦 Local Production162102271848
✅ 🐘 Local Postgres162102271848
✅ 🪟 Windows15400154
✅ 📋 Other102002121232
✅ vercel-multi-region270027
Total7519011328651
Details by Category

✅ ▲ Vercel Production

AppPassedFailedSkipped
✅ astro126028
✅ example126028
✅ express126028
✅ fastify126028
✅ hono126028
✅ nextjs-turbopack15103
✅ nextjs-webpack15103
✅ nitro126028
✅ nuxt126028
✅ sveltekit14509
✅ vite126028

✅ 💻 Local Development

AppPassedFailedSkipped
✅ astro-stable128026
✅ express-stable128026
✅ fastify-stable128026
✅ hono-stable128026
✅ nextjs-turbopack-canary135019
✅ nextjs-turbopack-stable15400
✅ nextjs-webpack-canary135019
✅ nextjs-webpack-stable15400
✅ nitro-stable128026
✅ nuxt-stable128026
✅ sveltekit-stable14707
✅ vite-stable128026

✅ 📦 Local Production

AppPassedFailedSkipped
✅ astro-stable128026
✅ express-stable128026
✅ fastify-stable128026
✅ hono-stable128026
✅ nextjs-turbopack-canary135019
✅ nextjs-turbopack-stable15400
✅ nextjs-webpack-canary135019
✅ nextjs-webpack-stable15400
✅ nitro-stable128026
✅ nuxt-stable128026
✅ sveltekit-stable14707
✅ vite-stable128026

✅ 🐘 Local Postgres

AppPassedFailedSkipped
✅ astro-stable128026
✅ express-stable128026
✅ fastify-stable128026
✅ hono-stable128026
✅ nextjs-turbopack-canary135019
✅ nextjs-turbopack-stable15400
✅ nextjs-webpack-canary135019
✅ nextjs-webpack-stable15400
✅ nitro-stable128026
✅ nuxt-stable128026
✅ sveltekit-stable14707
✅ vite-stable128026

✅ 🪟 Windows

AppPassedFailedSkipped
✅ nextjs-turbopack15400

✅ 📋 Other

AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable128026
✅ e2e-local-dev-tanstack-start-128026
✅ e2e-local-postgres-nest-stable128026
✅ e2e-local-postgres-tanstack-start-128026
✅ e2e-local-prod-nest-stable128026
✅ e2e-local-prod-tanstack-start-128026
✅ e2e-vercel-prod-nest126028
✅ e2e-vercel-prod-tanstack-start126028

✅ vercel-multi-region

AppPassedFailedSkipped
✅ nextjs-turbopack2700

📋 View full workflow run

@github-actions

github-actionsBot commented Jul 27, 2026

Copy link
Copy Markdown
ContributorAuthor

📊 Workflow Benchmarks

commit 1c3b4f9 · Wed, 29 Jul 2026 00:19:08 GMT · run logs

Backend: vercel · app: nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep391 (-60%) 💚1378 🔴 (+28%) 🔻1419 🔴 (+29%) 🔻1717 🔴 (+13%)30
TTFSstream358 (-4.8%)1380 🔴 (+28%) 🔻1432 🔴 (+31%) 🔻1561 🔴 (+40%) 🔻30
TTFShook + stream603 (+4.3%)1712 🔴 (+18%) 🔻1790 🔴 (+19%) 🔻5576 🔴 (+184%) 🔻30
STSO1020 steps (1-20)190 (-12%)285 🔴 (-16%) 💚411 🔴 (-10%)645 🔴 (+40%) 🔻19
STSO1020 steps (101-120)182 (-9.0%)265 🔴 (-6.0%)436 🔴 (+25%) 🔻629 🔴 (+73%) 🔻19
STSO1020 steps (1001-1020)516 (+7.3%)572 🔴 (-7.6%)597 🔴 (-9.5%)616 🔴 (-10%)19
WO1020 steps416601 (-5.8%)416601 (-5.8%)416601 (-5.8%)416601 (-5.8%)1
SLstream latency102 (+3.0%)149 🔴 (-16%) 💚176 🔴 (-37%) 💚323 🔴 (-55%) 💚30
SOstream overhead (text)120 (-7.7%)199 (-27%) 💚237 (-26%) 💚387 (-52%) 💚30
SOstream overhead (structured)107 (-15%) 💚188 (-33%) 💚215 (-53%) 💚396 (-49%) 💚30
📜 Previous results (5)

af0556d

Tue, 28 Jul 2026 21:33:03 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep1319 (+87%) 🔻1497 🔴 (+48%) 🔻1543 🔴 (+52%) 🔻2390 🔴 (+58%) 🔻30
TTFSstream278 (-71%) 💚1465 🔴 (+48%) 🔻1498 🔴 (+48%) 🔻1523 🔴 (+45%) 🔻30
TTFShook + stream1634 (+35%) 🔻1809 🔴 (+40%) 🔻1831 🔴 (+37%) 🔻1914 🔴 (+19%) 🔻30
STSO1020 steps (1-20)185 (+16%) 🔻325 🔴 (+26%) 🔻482 🔴 (+59%) 🔻782 🔴 (+84%) 🔻19
STSO1020 steps (101-120)194 (+4.9%)294 🔴 (+20%) 🔻424 🔴 (+51%) 🔻557 🔴 (-21%) 💚19
STSO1020 steps (1001-1020)480 (+2.8%)535 🔴 (-5.3%)635 🔴 (+4.1%)756 🔴 (+10%)19
WO1020 steps426481 (+10%)426481 (+10%)426481 (+10%)426481 (+10%)1
SLstream latency96 (+19%) 🔻199 🔴 (+51%) 🔻233 🔴 (+66%) 🔻3735 🔴 (+1987%) 🔻30
SOstream overhead (text)113 (+12%)191 (+6.1%)309 (+53%) 🔻696 (+178%) 🔻30
SOstream overhead (structured)103 (+4.0%)163 (+0.6%)175 (-10%)186 (-14%)30

a69e1c2

Mon, 27 Jul 2026 19:58:56 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep1178 (+66%) 🔻1276 🔴 (+24%) 🔻1363 🔴 (+25%) 🔻1722 🔴 (+21%) 🔻30
TTFSstream1187 (+39%) 🔻1257 🔴 (+32%) 🔻1267 🔴 (+30%) 🔻1370 🔴 (+38%) 🔻30
TTFShook + stream670 (-39%) 💚1414 🔴 (+15%) 🔻1446 🔴 (+15%)1585 🔴 (+7.9%)30
STSO1020 steps (1-20)160 (-12%)252 🔴 (-8.7%)280 🔴 (-7.9%)287 🔴 (-27%) 💚19
STSO1020 steps (101-120)184 (-1.1%)238 🔴 (-11%)284 🔴 (-5.6%)345 🔴 (-86%) 💚19
STSO1020 steps (1001-1020)472 (+5.6%)531 🔴 (+2.9%)613 🔴 (+14%)1091 🔴 (+66%) 🔻19
WO1020 steps360324 (-6.3%)360324 (-6.3%)360324 (-6.3%)360324 (-6.3%)1
SLstream latency94 (+22%) 🔻137 🔴 (+10%)169 🔴 (+17%) 🔻634 🔴 (+149%) 🔻30
SOstream overhead (text)90 (-7.2%)149 (-3.9%)188 (+7.4%)389 (+96%) 🔻30

388e2e4

Mon, 27 Jul 2026 18:58:11 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep1209 (+70%) 🔻1282 🔴 (+24%) 🔻1330 🔴 (+22%) 🔻1629 🔴 (+15%)30
TTFSstream1228 (+43%) 🔻1363 🔴 (+43%) 🔻1392 🔴 (+43%) 🔻1408 🔴 (+42%) 🔻30
TTFShook + stream651 (-40%) 💚1559 🔴 (+27%) 🔻1615 🔴 (+28%) 🔻1725 🔴 (+17%) 🔻30
STSO1020 steps (1-20)173 (-4.4%)279 🔴 (+1.1%)341 🔴 (+12%)424 🔴 (+7.6%)19
STSO1020 steps (101-120)190 (+2.2%)258 🔴 (-3.4%)319 🔴 (+6.0%)361 🔴 (-85%) 💚19
STSO1020 steps (1001-1020)471 (+5.4%)572 🔴 (+11%)679 🔴 (+26%) 🔻983 🔴 (+50%) 🔻19
WO1020 steps383460 (±0%)383460 (±0%)383460 (±0%)383460 (±0%)1
SLstream latency91 (+18%) 🔻134 🔴 (+8.1%)146 🔴 (+1.4%)207 🔴 (-19%) 💚30
SOstream overhead (text)98 (+1.0%)158 (+1.9%)182 (+4.0%)278 (+40%) 🔻30
SOstream overhead (structured)108 (+6.9%)167 (-0.6%)199 (+12%)871 (-43%) 💚30

93df707

Mon, 27 Jul 2026 16:49:58 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep272 (-72%) 💚1275 🔴 (+9.6%)1313 🔴 (+9.9%)1320 🔴 (-12%)30
TTFSstream209 (-27%) 💚1280 🔴 (+8.6%)1290 🔴 (+5.4%)1341 🔴 (-2.3%)30
TTFShook + stream574 (-56%) 💚1560 🔴 (±0%)1655 🔴 (±0%)1686 🔴 (-3.8%)30
STSO1020 steps (1-20)163 (-13%)297 🔴 (-3.3%)339 🔴 (-10%)431 🔴 (+13%)19
STSO1020 steps (101-120)192 (-4.5%)246 🔴 (-16%) 💚285 🔴 (-22%) 💚1131 🔴 (+195%) 🔻19
STSO1020 steps (1001-1020)464 (-10%)576 🔴 (-9.0%)683 🔴 (+2.9%)700 🔴 (-15%) 💚19
WO1020 steps378319 (-15%)378319 (-15%)378319 (-15%)378319 (-15%)1
SLstream latency90 (-17%) 💚154 🔴 (-68%) 💚159 🔴 (-78%) 💚359 🔴 (-67%) 💚30
SOstream overhead (text)97 (-28%) 💚148 (-39%) 💚166 (-46%) 💚238 (-57%) 💚30
SOstream overhead (structured)97 (-27%) 💚142 (-42%) 💚150 (-49%) 💚196 (-56%) 💚30

677b41e

Mon, 27 Jul 2026 16:17:58 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep243 (-66%) 💚1301 🔴 (+25%) 🔻1323 🔴 (+20%) 🔻1369 🔴 (+19%) 🔻30
TTFSstream282 (-71%) 💚1325 🔴 (+23%) 🔻1341 🔴 (+16%) 🔻1505 🔴 (+17%) 🔻30
TTFShook + stream434 (-66%) 💚1606 🔴 (+14%)1678 🔴 (+16%) 🔻1989 🔴 (+19%) 🔻30
STSO1020 steps (1-20)181 (-9.0%)275 🔴 (±0%)466 🔴 (+35%) 🔻879 🔴 (+127%) 🔻19
STSO1020 steps (101-120)212 (-1.4%)314 🔴 (+12%)344 🔴 (+15%) 🔻394 🔴 (+4.5%)19
STSO1020 steps (1001-1020)494 (+1.0%)593 🔴 (+5.9%)650 🔴 (+9.1%)685 🔴 (+13%)19
WO1020 steps483065 (+17%) 🔻483065 (+17%) 🔻483065 (+17%) 🔻483065 (+17%) 🔻1
SLstream latency105 (+6.1%)214 🔴 (+63%) 🔻253 🔴 (+71%) 🔻575 🔴 (+176%) 🔻30
SOstream overhead (text)125 (-3.8%)280 🔴 (+29%) 🔻376 (+53%) 🔻905 (+235%) 🔻30
SOstream overhead (structured)120 (-14%)206 (-6.8%)395 (+59%) 🔻650 (-6.6%)30
ℹ️ Metric definitions & methodology

Best/P75/P90/P99 deltas compare against the most recent benchmark run on main at the time of this run. 🔻 flags a delta worse than +15%, 💚 one better than −15%.

Metrics — TTFS: time to first step body (in-deployment start() → first step body, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window)

Scenarios — step: one trivial no-op step, no stream; no hooks, so the run stays in turbo mode (in-process fast path) · stream: one streaming step; no hooks, so the run stays in turbo mode (in-process fast path) · hook + stream: registers a hook before one step, which exits turbo mode (dispatch path) · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges, and WO is the whole-run overhead outside step bodies · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) · stream overhead (text): writer streams 300 variable-length text token deltas paced at 100/s for 3s (a haiku-size LLM's token throughput) while a parallel reader drains the whole stream; SO is the end-to-end write+consume time beyond the 3s generation window (overhead/backpressure) · stream overhead (structured): same workload as stream overhead (text), but each delta is an AI-SDK-style structured object ({ type: 'text-delta', id, text }) instead of a raw string, so the SO gap vs the text scenario is the added serialization cost

🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · SO 250/500/1000 · STSO (1-20) 20/30/60 · STSO (101-120) 30/45/90 · STSO (1001-1020) 40/60/120

All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor (clientStart) right before start(), so the CI runner’s request and its path through api.vercel.com sit outside every measured window. TTFS = in-deployment start() → first step body (turbo uses the in-process fast path, non-turbo the dispatch path), and includes the VQS dispatch hop plus any /flow cold start. STSO/WO are measured between step bodies on the deployment. SL is measured inside the workflow (parallel reader/writer steps), so it no longer includes the api.vercel.com read path.

Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the /flow invocation for a large fraction of runs, inflating P75+; the Best column shows the fastest (warm-start) sample for comparison.

@github-actions

Copy link
Copy Markdown
ContributorAuthor

No backport to stable for 741a0d9 (AI decision).

This is an automated changesets "Version Packages (beta)" commit that only bumps package versions, consumes changeset files, and appends CHANGELOG entries. Release plumbing and version bumps are explicitly not backported; stable maintains its own independent (non-prerelease) versioning line.

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

741a0d9eaff8afac161507ef5c59276f906d6d60

Sign up for freeto 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.

2 participants

@TooTallNate@VaguelySerious