[next] Bundle workflows created after their import, or deleted and restored by VaguelySerious · Pull Request #4547 · vercel/workflow

VaguelySerious · 2026-10-01T00:38:54Z

Follow-up to #4396. The graph-scoped next dev watcher only watches modules discovery reached, the directories they live in, and the route roots. Two common edits fell outside that scope, and the workflow stayed unbundled (WorkflowNotRegisteredError) until the dev server was restarted. Before #4396 both worked.

edit	`main`	this PR
write `import '@/lib/billing/wf'`, then create `lib/billing/wf.ts` (new directory, or directly in the project root / `src/`)	never bundled	bundled
same, but the importer is a workflow file (the bundle build fails on the missing import)	never bundled	bundled
delete a workflow module whose importer is unchanged, then restore it	never re-bundled; editing the restored file doesn't help	re-bundled

Fix

@workflow/builders: discovery records unresolvedImportCandidates, the paths an unresolved relative or tsconfig-alias import would resolve to (same extension and index.* rules discovery already uses). Imports that resolve to an existing non-source file (CSS, images) and bare package specifiers are not recorded.
@workflow/next: the watch scope passes those paths to Watchpack's missing list. Watchpack tracks them through their nearest existing parent, so this adds no recursive watches. Creating one forces a rediscovery. classifyRebuild's isEntrypoint option is renamed to forcesRediscovery to cover both cases.
Failed rebuilds: when the importer is a workflow or step module, esbuild rejects the unresolved import and the rebuild throws before discoveredEntries is replaced. The watcher then reads that attempt's cached discovery result and keeps its candidates in scope until a rediscovery succeeds.

Testing

fast-discovery.test.ts: candidates for a missing relative import, alias import and explicit-extension import; none for imports that resolve, existing stylesheets, or a missing bare package.
watch-scope.test.ts: candidates land in missing without following their directories. With a live Watchpack, a candidate created inside a directory that doesn't exist yet is reported, and so is a deleted-then-restored module.
dev.test.ts: two new Next cases (should bundle a workflow created after its import was written, should bundle a workflow again after it is deleted and restored). Locally against nextjs-turbopack, both fail on main (3/3 runs) and pass here. The full dev suite passed 3/3 runs (9 passed, 2 skipped).
Manual scratch Next 16.3.6 app: all scenarios in the table above, before and after.

Two live tests in watch-scope.test.ts (watches directories only…, does not replay an edit that predates the attach) fail on this macOS machine on unmodified main too. They are unrelated to this change and CI runs them on Linux/Windows.

🤖 Generated with Claude Code

…stored The graph-scoped dev watcher (#4396) only watches modules discovery reached, the directories they live in, and the route roots. Two edits fell outside that scope and left a workflow unbundled until the dev server restarted: - writing an import before creating its target in a directory the graph does not occupy yet (or directly in the project root or `src/`) - deleting a graph module while its importer is unchanged, then restoring it Discovery now records where each unresolved relative or tsconfig-alias import would resolve, and the Next watcher tracks those paths as `missing`. Creating one forces a rediscovery. When the importer is a workflow or step module the bundle build throws on the unresolved import, so the failed attempt's candidates are kept in scope until a rediscovery succeeds. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

vercel · 2026-10-01T00:38:57Z

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

Project	Deployment	Actions	Updated
example-nextjs-workflow-turbopack	Ready	Preview, v0	Oct 1, 2026 12:43am UTC
example-nextjs-workflow-webpack	Ready	Preview, v0	Oct 1, 2026 12:43am UTC
example-workflow	Ready	Preview, v0	Oct 1, 2026 12:43am UTC
workbench-astro-workflow	Building	Preview, v0	Oct 1, 2026 12:43am UTC
workbench-express-workflow	Ready	Preview, v0	Oct 1, 2026 12:43am UTC
workbench-fastify-workflow	Ready	Preview, v0	Oct 1, 2026 12:43am UTC
workbench-hono-workflow	Ready	Preview, v0	Oct 1, 2026 12:43am UTC
workbench-nestjs-workflow	Ready	Preview, v0	Oct 1, 2026 12:43am UTC
workbench-nitro-workflow	Ready	Preview, v0	Oct 1, 2026 12:43am UTC
workbench-nuxt-workflow	Ready	Preview, v0	Oct 1, 2026 12:43am UTC
workbench-python-workflow	Ready	Preview, v0	Oct 1, 2026 12:43am UTC
workbench-sveltekit-workflow	Ready	Preview, v0	Oct 1, 2026 12:43am UTC
workbench-tanstack-start-workflow	Ready	Preview, v0	Oct 1, 2026 12:43am UTC
workbench-vite-workflow	Ready	Preview, v0	Oct 1, 2026 12:43am UTC
workflow-docs	Ready	Preview, v0	Oct 1, 2026 12:43am UTC
workflow-swc-playground	Ready	Preview, v0	Oct 1, 2026 12:43am UTC
workflow-tarballs	Ready	Preview, v0	Oct 1, 2026 12:43am UTC
workflow-web	Ready	Preview, v0	Oct 1, 2026 12:43am UTC

changeset-bot · 2026-10-01T00:39:04Z

🦋 Changeset detected

Latest commit: 946a666

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 17 packages

Name	Type
@workflow/next	Patch
@workflow/builders	Patch
workflow	Patch
@workflow/astro	Patch
@workflow/cli	Patch
@workflow/nest	Patch
@workflow/nitro	Patch
@workflow/rollup	Patch
@workflow/sveltekit	Patch
@workflow/vite	Patch
@workflow/vitest	Patch
@workflow/world-testing	Patch
@workflow/nuxt	Patch
@workflow/core	Patch
@workflow/world-vercel	Patch
@workflow/web-shared	Patch
@workflow/web	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

github-actions · 2026-10-01T00:39:12Z

🧪 E2E Test Results

✅ All tests passed

⚠️ Flaky E2E Tests (passed on retry)

These tests failed at least once and passed on a retry. A recurring entry here is a real race worth investigating.

'hookGetConflictWithParallelStepWorkfl…' - hook.getConflict() does not block step execution (nextjs-webpack · local-dev / local / node / stable)
a run can take over its own earlier hook (sveltekit · local-dev / local / node / stable)
concurrent hook token conflict - two workflows cannot use the same hook token simultaneously (nuxt · local-dev / local / quickjs / stable)
hookGetConflictWorkflow - hook.getConflict() resolves with the conflicting run when token is already registered (nextjs-webpack · local-dev / local / node / stable)

🛠 Infra Events (absorbed by the harness)

Platform anomalies the e2e harness detected and worked around (e.g. a run the queue never picked up, replaced by a fresh run). Clustered timestamps indicate a backend blip; a steady drip indicates a platform issue worth escalating.

run-pickup-stall · runs app-generated source against a registered step (tanstack-start) · at 00:43:53Z · abandoned wrun_01M3TENE218VN8X89RYVEH4XWP
cold-start-warmup · suite warmup (tanstack-start) · at 00:44:00Z · abandoned wrun_01M3TENE23Z8A4QFC93VGFFKKG
run-pickup-stall · Calculator.calculate - static workflow method using static step methods from another class (vite) · at 00:45:21Z · abandoned wrun_01M3TER44QMHV11XG664VPES9M
run-pickup-stall · hookGetConflictWorkflow - hook.getConflict() resolves with the conflicting run when token is already registered (nextjs-webpack) · at 00:49:44Z · abandoned wrun_01M3TF04TS37Y4QGE5TG6XR705

E2E Test Summary

Summary

	Passed	Skipped	Total
✅ ▲ Vercel Production	3904	875	4779
✅ 💻 Local Development	4406	550	4956
✅ 📦 Local Production	4406	550	4956
✅ 🐘 Local Postgres	4406	550	4956
✅ 🪟 Windows	342	12	354
✅ 🌐 Cross-language Conformance	68	84	152
✅ dynamic-runs	0	0	0
✅ vercel-http-transport	879	183	1062
✅ vercel-multi-region	27	0	27
✅ vercel-ws-transport	595	113	708
Total	19033	2917	21950

Details by Category

✅ ▲ Vercel Production

App	Passed	Skipped
✅ astro-node	142	35
✅ astro-quickjs	142	35
✅ example-node	142	35
✅ example-quickjs	142	35
✅ express-node	142	35
✅ express-quickjs	142	35
✅ fastify-node	142	35
✅ fastify-quickjs	142	35
✅ hono-node	142	35
✅ hono-quickjs	142	35
✅ nest-node	142	35
✅ nest-quickjs	142	35
✅ nextjs-turbopack-node	169	8
✅ nextjs-turbopack-quickjs	169	8
✅ nextjs-webpack-node	169	8
✅ nextjs-webpack-quickjs	169	8
✅ nitro-node	142	35
✅ nitro-quickjs	142	35
✅ nuxt-node	142	35
✅ nuxt-quickjs	142	35
✅ python-node	66	111
✅ sveltekit-node	161	16
✅ sveltekit-quickjs	161	16
✅ tanstack-start-node	142	35
✅ tanstack-start-quickjs	142	35
✅ vite-node	142	35
✅ vite-quickjs	142	35

✅ 💻 Local Development

App	Passed	Skipped
✅ astro-stable-node	148	29
✅ astro-stable-quickjs	148	29
✅ express-stable-node	148	29
✅ express-stable-quickjs	148	29
✅ fastify-stable-node	148	29
✅ fastify-stable-quickjs	148	29
✅ hono-stable-node	148	29
✅ hono-stable-quickjs	148	29
✅ nest-stable-node	148	29
✅ nest-stable-quickjs	148	29
✅ nextjs-turbopack-canary-node	176	1
✅ nextjs-turbopack-canary-quickjs	176	1
✅ nextjs-turbopack-stable-node	176	1
✅ nextjs-turbopack-stable-quickjs	176	1
✅ nextjs-webpack-canary-node	176	1
✅ nextjs-webpack-canary-quickjs	176	1
✅ nextjs-webpack-stable-node	176	1
✅ nextjs-webpack-stable-quickjs	176	1
✅ nitro-stable-node	148	29
✅ nitro-stable-quickjs	148	29
✅ nuxt-stable-node	148	29
✅ nuxt-stable-quickjs	148	29
✅ sveltekit-stable-node	167	10
✅ sveltekit-stable-quickjs	167	10
✅ tanstack-start-node	148	29
✅ tanstack-start-quickjs	148	29
✅ vite-stable-node	148	29
✅ vite-stable-quickjs	148	29

✅ 📦 Local Production

App	Passed	Skipped
✅ astro-stable-node	148	29
✅ astro-stable-quickjs	148	29
✅ express-stable-node	148	29
✅ express-stable-quickjs	148	29
✅ fastify-stable-node	148	29
✅ fastify-stable-quickjs	148	29
✅ hono-stable-node	148	29
✅ hono-stable-quickjs	148	29
✅ nest-stable-node	148	29
✅ nest-stable-quickjs	148	29
✅ nextjs-turbopack-canary-node	176	1
✅ nextjs-turbopack-canary-quickjs	176	1
✅ nextjs-turbopack-stable-node	176	1
✅ nextjs-turbopack-stable-quickjs	176	1
✅ nextjs-webpack-canary-node	176	1
✅ nextjs-webpack-canary-quickjs	176	1
✅ nextjs-webpack-stable-node	176	1
✅ nextjs-webpack-stable-quickjs	176	1
✅ nitro-stable-node	148	29
✅ nitro-stable-quickjs	148	29
✅ nuxt-stable-node	148	29
✅ nuxt-stable-quickjs	148	29
✅ sveltekit-stable-node	167	10
✅ sveltekit-stable-quickjs	167	10
✅ tanstack-start-node	148	29
✅ tanstack-start-quickjs	148	29
✅ vite-stable-node	148	29
✅ vite-stable-quickjs	148	29

✅ 🐘 Local Postgres

App	Passed	Skipped
✅ astro-stable-node	148	29
✅ astro-stable-quickjs	148	29
✅ express-stable-node	148	29
✅ express-stable-quickjs	148	29
✅ fastify-stable-node	148	29
✅ fastify-stable-quickjs	148	29
✅ hono-stable-node	148	29
✅ hono-stable-quickjs	148	29
✅ nest-stable-node	148	29
✅ nest-stable-quickjs	148	29
✅ nextjs-turbopack-canary-node	176	1
✅ nextjs-turbopack-canary-quickjs	176	1
✅ nextjs-turbopack-stable-node	176	1
✅ nextjs-turbopack-stable-quickjs	176	1
✅ nextjs-webpack-canary-node	176	1
✅ nextjs-webpack-canary-quickjs	176	1
✅ nextjs-webpack-stable-node	176	1
✅ nextjs-webpack-stable-quickjs	176	1
✅ nitro-stable-node	148	29
✅ nitro-stable-quickjs	148	29
✅ nuxt-stable-node	148	29
✅ nuxt-stable-quickjs	148	29
✅ sveltekit-stable-node	167	10
✅ sveltekit-stable-quickjs	167	10
✅ tanstack-start-node	148	29
✅ tanstack-start-quickjs	148	29
✅ vite-stable-node	148	29
✅ vite-stable-quickjs	148	29

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack-node	171	0	6
✅ nextjs-turbopack-quickjs	171	0	6

✅ 🌐 Cross-language Conformance

App	Passed	Failed	Skipped
✅ python	68	0	84

✅ dynamic-runs

App	Passed	Failed	Skipped
✅ astro-vercel	0	0	0
✅ example-vercel	0	0	0
✅ express-vercel	0	0	0
✅ fastify-vercel	0	0	0
✅ hono-vercel	0	0	0
✅ nest-vercel	0	0	0
✅ nextjs-turbopack-vercel	0	0	0
✅ nextjs-webpack-vercel	0	0	0
✅ nitro-vercel	0	0	0
✅ nuxt-vercel	0	0	0
✅ sveltekit-vercel	0	0	0
✅ tanstack-start-vercel	0	0	0
✅ vite-vercel	0	0	0

✅ vercel-http-transport

App	Passed	Skipped
✅ example	142	35
✅ express	142	35
✅ hono	142	35
✅ nextjs-turbopack	169	8
✅ nitro	142	35
✅ vite	142	35

✅ vercel-multi-region

App	Passed	Failed	Skipped
✅ nextjs-turbopack	27	0	0

✅ vercel-ws-transport

App	Passed	Skipped
✅ example	142	35
✅ express	142	35
✅ nextjs-turbopack	169	8
✅ vite	142	35

📋 View full workflow run

github-actions · 2026-10-01T00:39:15Z

📊 Workflow Benchmarks

commit 946a666 · Thu, 01 Oct 2026 00:58:55 GMT · run logs

Backend: vercel · app: nextjs-turbopack

Metric	Scenario	Best (ms)	P75 (ms)	P90 (ms)	P99 (ms)	Samples
TTFS	step	492 (-74%) 💚	2524 🔴 (+23%) 🔻	2539 🔴 (+19%) 🔻	2564 🔴 (+16%) 🔻	30
TTFS	stream	2279 (+340%) 🔻	2436 🔴 (+6.4%)	2466 🔴 (+4.6%)	2551 🔴 (-6.8%)	30
TTFS	hook + stream	778 (-68%) 💚	2855 🔴 (+6.8%)	3119 🔴 (+12%)	3268 🔴 (+13%)	30
Fan-out TTFS	Promise.all(100 steps)	584 (+7.9%)	836 (+4.5%)	897 (-11%)	3135 (+13%)	10
Fan-out TTLS	Promise.all(100 steps)	2015 (-27%) 💚	3309 (-64%) 💚	4758 (-48%) 💚	10883 (+17%) 🔻	10
STSO	1020 steps (inline)	144 (±0%)	183 (-29%) 💚	197 (-45%) 💚	259 (-65%) 💚	1019
WO	1020 steps	181396 (-27%) 💚	181396 (-27%) 💚	181396 (-27%) 💚	181396 (-27%) 💚	1
CRTT	first chunk (pooled)	64 (-4.5%)	102 (-31%) 💚	115 (-29%) 💚	187 (-13%)	28

Streams

Scenario	CRTT 1st	p75	p90	p99	CDV max	iters
paced control (100/s, 60B)	74.5 (-37%)	128 (-35%)	179 (-39%)	417 (-28%)	160 (-35%)	10
size sweep (100/s, 160B-12KB)	89 (-6%)	151 (-14%)	216 (-12%)	500 (+34%)	149 (-25%)	10
replay gateway-gpt-5.4-nano-2000t (1x)	70 (-51%)	119 (-35%)	160 (-38%)	392 (-47%)	310 (+11%)	3
replay eve-gpt-5.6-sol-2000t (1x)	66.5 (-57%)	122 (-34%)	154 (-36%)	361 (-40%)	242 (-54%)	2
replay eve-gpt-5.6-sol-2000t (2x)	154 (+26%)	159 (-29%)	203 (-33%)	276 (-40%)	229 (-23%)	3

📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 249094ms → this run 181110ms (Δ -67984ms, -27%)

  100-150 ms  ┃                         main   3  this   1    -2
  150-200 ms  ███████████░░░░░░░░░░░░┃  main 423  this 927  +504
  200-250 ms  █┃██████                  main 314  this  79  -235
  250-300 ms  ┃██                       main 120  this  10  -110
  300-350 ms  ┃                         main  52  this   2   -50
  350-400 ms  ┃                         main  30  this   0   -30
  400-450 ms  ┃                         main  24  this   0   -24
  450-500 ms  ┃                         main  12  this   0   -12
  500-550 ms  ┃                         main  10  this   0   -10
  550-600 ms  ┃                         main   7  this   0    -7
  600-650 ms  ┃                         main   6  this   0    -6
  650-700 ms  ┃                         main   4  this   0    -4
  700-750 ms  ┃                         main   4  this   0    -4
  750-800 ms  ┃                         main   2  this   0    -2
  800-850 ms  ┃                         main   4  this   0    -4
  850-900 ms  ┃                         main   1  this   0    -1
  900-950 ms  ┃                         main   1  this   0    -1
1200-1250 ms  ┃                         main   2  this   0    -2

📈 CRTT drill-down vs main (RTT distributions & profiles)

variant  RTT 1ms→5s+             avg         p50         p90         p99     n
control  ······▆█▁····  113.4 (-31%)  106 (-25%)  179 (-39%)  417 (-28%)  3000
sweep    ······▄█▁▁···  125.4 (-14%)  115 (-14%)  216 (-12%)  500 (+34%)  3000
gw 1x    ·····▁█▅▁····    105 (-31%)   94 (-30%)  160 (-38%)  392 (-47%)  5295
eve 1x   ·····▁█▆▁▁···  101.9 (-35%)   91 (-35%)  154 (-36%)  361 (-40%)  5186
eve 2x   ·····▁▄█▁····  129.2 (-29%)  126 (-25%)  203 (-33%)  276 (-40%)  7779

RTT over stream progress (avg per tenth of stream, bars scaled min→max):

control  █▄▄▄▅▂▁▂▁▁  102–137ms
sweep    ▃▁▃▂▆█▁▁▂█  114–147ms
gw 1x    ▄▆▄▃▁█▂▃▅▂  94–121ms
eve 1x   ▃▁▂▃▂▂▃█▃▁  90–134ms
eve 2x   █▁▄▂▁▂▆▅▇▁  121–142ms

RTT by chunk size (avg per log size bin, ~160B → ~12KB serialized, bars scaled min→max):

sweep  ██▄▁▅▃▆  124–127ms

Delivery jitter over stream progress (avg positive CDV per tenth of stream, bars scaled min→max):

control  ▆▄█▄▇▁▂▆▁▃  30–38ms
sweep    ▃▃▄▄█▃▅▂▆▁  41–64ms
gw 1x    ▇▆▆▁▅█▅▅▇▅  24–34ms
eve 1x   ▂▄▅▃▅▅█▇▁▆  19–24ms
eve 2x   █▄▃▄▅▂▃▁▃▄  17–28ms

ℹ️ Metric definitions & methodology

_{Streams: first-chunk RTT (the stream-open path, before any buffering/backpressure), CRTT percentiles, and worst delivery stall (CDV max). Cells are medians across iterations; per-run values in the artifacts. No 🔴/🟢 marks until targets attach.}

_{The collapsed STSO distribution section above buckets every step gap, split inline (same warm process — pure framework overhead) vs queue-hop (fresh process — dispatch, reinit, replay). █ = main, ┃ = this run, ░ = fill.}

_{The collapsed CRTT drill-down: per-variant RTT histograms (fixed log bins, · = empty) and mean RTT/positive-CDV profile lines over stream progress and chunk size. Histograms, avgs, and profiles merge exactly across runs; p50–p99 are percentile-of-percentiles. Per-index rows live in the artifacts.}

_{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) · Fan-out TTFS: fan-out time to first step (in-deployment start() → first of the parallel step bodies to complete) · Fan-out TTLS: fan-out time to last step (in-deployment start() → last of the parallel step bodies to complete, i.e. when the Promise.all resolves) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · CRTT: chunk round-trip time (per-chunk write → read latency, one clock domain: deployment → stream backend → same deployment) · CDV: chunk delay variation / delivery jitter (inter-arrival gap minus inter-write gap per seq-adjacent pair; skew-free; the row is each run's MAX positive value, so one stall moves it)}

_{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 · Promise.all(100 steps): 100 trivial no-op steps started together in a single Promise.all; Fan-out TTFS is the first of them to complete and Fan-out TTLS the last, both from the in-deployment clientStart, so their gap is the spread the runtime adds across the fan-out · paced control (100/s, 60B): the control: 300 tiny (~60B) deltas metronome-paced at 100/s — zero workload structure, so it reads the transport floor and flush cadence, and disambiguates transport-wide vs workload-specific when a replay row moves · size sweep (100/s, 160B-12KB): same pacing as the control with deltas padded in rotation across seven log-spaced sizes (~160B–12KB) — rotation decouples size from stream position, so it isolates whether chunk size causes latency · replay gateway-gpt-5.4-nano-2000t (1x): raw provider SSE cadence captured at the AI gateway boundary (gpt-5.4-nano, the most popular gateway model; per-token deltas p50 208B = the modal production chunk size), replayed exactly as measured — the typical customer's workload; its CDV is the typical customer's real delivery jitter · replay eve-gpt-5.6-sol-2000t (1x): a captured eve turn (gpt-5.6-sol, the most-used demanding eve model; ~2000 output tokens = production p50 turn length) replayed exactly as measured — eve's envelope protocol re-ships the cumulative message so sizes ramp 142B→13KB; the demanding outlier tenant's reality · replay eve-gpt-5.6-sol-2000t (2x): the same eve capture at 2x — the headroom/stress row; real fast-tier models emit the same chunk sizes at proportionally higher rate, so time compression is a faithful speed model · first chunk (pooled): every run's seq-0 RTT pooled across all stream scenarios — the first chunk precedes any workload differentiation, so pooling samples one shared stream-open path with exact percentiles}

_{Replay cadences (semantic sha256) — eve-gpt-5.6-sol-2000t eaf22f5946e7c61f3c65c7006d550df180cfabd4e706254a09f22aec0cfb420d · gateway-gpt-5.4-nano-2000t 6f24ac518b6b83ff1d0e85a5fe78230db192716d66a7fc6b2fe022752001d041}

_{🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600}

_{All timestamps are deployment-side; runs are triggered in-deployment, so the CI runner and api.vercel.com sit outside every measured window. TTFS = start() → first step body (includes dispatch + any cold start); Fan-out TTFS/TTLS = first/last step completion of one Promise.all from the same anchor (the gap is the runtime’s fan-out spread); STSO/WO between step bodies; CRTT inside the workflow (excludes the api.vercel.com read path).}

_{Cold starts stay in the numbers (real bursty-workload latency, inflates P75+); Best is the warm floor.}

github-actions · 2026-10-01T00:42:02Z

Sim World

Simulated world deterministic testing for races. Traces

🟠 world-sim scenario book — 1 fail of 42 total

fence=per-spec

scenario	outcome	events	virt	replay
✅ `smoke-no-steps`	completed	3	0ms	ok
✅ `smoke-one-step`	completed	6	0ms	ok
✅ `hook-at-step-started`	completed	12	0ms	ok
✅ `hook-at-step-completed`	completed	12	0ms	ok
✅ `hook-at-hook-created`	completed	12	0ms	ok
✅ `deadline-hook-wins`	completed	7	1.0h	ok
✅ `deadline-expires`	completed	7	1.0h	ok
✅ `step-vs-timer-early-settlement`	completed	8	1.0h	ok
✅ `long-sleep`	completed	11	30.0d	ok
✅ `hook-never-arrives`	stalled	3	0ms	skipped
✅ `step-retries-twice`	completed	10	2.0s	ok
✅ `parallel-steps`	completed	9	0ms	ok
✅ `hook-on-execution-state`	completed	12	0ms	ok
✅ `peek-hook-before-branch`	completed	12	0ms	ok
✅ `peek-hook-after-branch`	completed	12	0ms	ok
✅ `peek-hook-at-registration`	completed	12	0ms	ok
✅ `race-hook-before-probe`	completed	12	0ms	ok
✅ `race-hook-after-probe`	completed	12	0ms	ok
✅ `race-duplicate-delivery`	completed	13	0ms	ok
✅ `attr-hook-before-step`	completed	11	0ms	ok
✅ `attr-hook-after-step`	completed	11	0ms	ok
✅ `attr-from-step-body`	completed	13	0ms	ok
✅ `fork-hook-after-timeout`	completed	14	1.0m	ok
✅ `fork-hook-before-timeout`	completed	14	1.0m	ok
✅ `count-hook-after-timeout`	completed	17	1.0m	ok
✅ `count-hook-before-timeout`	completed	20	1.0m	ok
✅ `stale-read-step-count-fork`	completed	20	1.0m	ok
✅ `stale-read-equal-step-counts`	completed	14	1.0m	ok
✅ `step-vs-step-fork`	completed	12	0ms	ok
✅ `step-vs-step-fork-fenced`	completed	12	0ms	ok
✅ `fence-catches-benign-direction`	completed	12	5ms	ok
✅ `in-flight-before-decision`	completed	17	1.0m	ok
❌ `in-flight-before-decision-counted`	completed	17	1.0m	ok
✅ `in-flight-after-decision`	completed	19	2.0m	ok
✅ `stale-read-step-count-fork-fenced`	completed	20	1.0m	ok
✅ `fork-hook-wins`	completed	13	1.0m	ok
✅ `fork-timeout-wins`	completed	13	1.0m	ok
✅ `unclaimed-payload-under-fork`	completed	17	1.0m	ok
✅ `claimed-payload-under-fork`	completed	17	1.0m	ok
✅ `writers-independent-step-bodies`	completed	12	0ms	ok
✅ `writers-scripted-tempo`	completed	12	0ms	ok
✅ `cancel-mid-step`	cancelled	7	0ms	skipped

Full trace: world-sim.txt

github-actions · 2026-10-01T00:43:50Z

Framework	Flow route	Step reg.	Framework output
hono	265.9 KiB (±0)	97.2 KiB (±0)	1.99 MiB (-12 B)
nextjs-turbopack	273.3 KiB (±0)	426 B (±0)	981.6 KiB (-4 B)

About these numbers

Sizes are gzip; parentheses show the change against main.
Flow route and Step reg. gate this job, on raw bytes rather than the gzip shown, at max(2%, 50.0 KiB). Framework output is informational.

946a666 · run

github-actions · 2026-10-01T04:40:35Z

No backport to stable for a11d037 (AI decision).

This fixes the graph-scoped next dev watcher introduced in #4396, which does not exist on stable: packages/next/src/watch-scope.ts and packages/next/src/watch-rebuild.ts are both absent there (verified with git ls-tree origin/stable), and the docs change targets docs/content/docs/v5/, the main-only docs version. The change therefore builds entirely on main-only APIs and has no corresponding defect on the maintenance line.

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

a11d037cee76143a2060fb34698aec5fc9f9a270

VaguelySerious requested a review from a team as a code owner October 1, 2026 00:38

vercel Bot deployed to Preview – workflow-docs October 1, 2026 00:41

View deployment

karthikscale3 approved these changes Oct 1, 2026

View reviewed changes

VaguelySerious merged commit a11d037 into main Oct 1, 2026
323 of 326 checks passed

VaguelySerious deleted the peter/next-dev-watch-unresolved-imports branch October 1, 2026 04:39

This was referenced Oct 1, 2026

Version Packages #4526

Merged

Version Packages Thegreatsura/workflow#1

Open

pranaygp mentioned this pull request Oct 2, 2026

[docs] Document Serializable, fatal dynamic start() refusals, and snapshot storage #4588

Open

VaguelySerious mentioned this pull request Nov 4, 2026

Fix the local-dev e2e reload race and recurring CI flakes #5243

Merged

Navigation Menu

Repository navigation

[next] Bundle workflows created after their import, or deleted and restored - #4547

[next] Bundle workflows created after their import, or deleted and restored#4547
VaguelySerious merged 1 commit into
mainfrom
peter/next-dev-watch-unresolved-imports

VaguelySerious commented Oct 1, 2026

Uh oh!

vercel Bot commented Oct 1, 2026 •

edited

Loading

Uh oh!

changeset-bot Bot commented Oct 1, 2026

Uh oh!

github-actions Bot commented Oct 1, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Oct 1, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Oct 1, 2026

Uh oh!

github-actions Bot commented Oct 1, 2026

Uh oh!

Uh oh!

github-actions Bot commented Oct 1, 2026

Uh oh!

This branch was successfully deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

VaguelySerious commented Oct 1, 2026

Fix

Testing

Uh oh!

vercel Bot commented Oct 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

changeset-bot Bot commented Oct 1, 2026

🦋 Changeset detected

Uh oh!

github-actions Bot commented Oct 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🧪 E2E Test Results

⚠️ Flaky E2E Tests (passed on retry)

🛠 Infra Events (absorbed by the harness)

E2E Test Summary

Uh oh!

github-actions Bot commented Oct 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📊 Workflow Benchmarks

Uh oh!

github-actions Bot commented Oct 1, 2026

Sim World

Uh oh!

github-actions Bot commented Oct 1, 2026

Uh oh!

Uh oh!

github-actions Bot commented Oct 1, 2026

Uh oh!

This branch was successfully deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

vercel Bot commented Oct 1, 2026 •

edited

Loading

github-actions Bot commented Oct 1, 2026 •

edited

Loading

github-actions Bot commented Oct 1, 2026 •

edited

Loading