Ensure class serialization / deserialization only happens in the proper global context

[TooTallNate]

Fixed class serialization/deserialization to properly respect VM context boundaries, ensuring workflow code only accesses classes registered in its own global context.

What changed?

• Modified getSerializationClass() to no longer fall back to checking globalThis when a class isn't found in the provided global context
• Updated the serialization tests to properly simulate how classes are registered and accessed in both host and VM contexts
• Added VM-specific class registration in tests to better match production behavior where workflow code runs in isolation

How to test?

• Run the updated serialization tests which now properly simulate the VM boundary
• Verify that class serialization/deserialization works correctly when classes are registered in their respective contexts
• Confirm that classes registered in one context aren't accessible from another context

Why make this change?

This change ensures proper isolation between the host environment and workflow VM contexts, matching production serverless behavior where workflow code runs in isolation. Previously, the code could leak class registrations between contexts, potentially causing unexpected behavior or security issues. This fix maintains proper boundaries between execution contexts.

[changeset-bot]

🦋 Changeset detected

Latest commit: 1566da2

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

This PR includes changesets to release 15 packages

Name	Type
@workflow/core	Patch
@workflow/builders	Patch
@workflow/cli	Patch
@workflow/docs-typecheck	Patch
@workflow/next	Patch
@workflow/nitro	Patch
@workflow/web-shared	Patch
workflow	Patch
@workflow/astro	Patch
@workflow/nest	Patch
@workflow/rollup	Patch
@workflow/sveltekit	Patch
@workflow/vite	Patch
@workflow/world-testing	Patch
@workflow/nuxt	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]

🧪 E2E Test Results

❌ Some tests failed

Summary

	Passed	Failed	Skipped	Total
✅ ▲ Vercel Production	457	0	38	495
✅ 💻 Local Development	418	0	32	450
✅ 📦 Local Production	418	0	32	450
✅ 🐘 Local Postgres	418	0	32	450
✅ 🪟 Windows	45	0	0	45
❌ 🌍 Community Worlds	31	161	0	192
✅ 📋 Other	123	0	12	135
Total	1910	161	146	2217

❌ Failed Tests

🌍 Community Worlds (161 failed)

mongodb (40 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

redis (40 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

starter (41 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• health check (CLI) - workflow health command reports healthy endpoints
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

turso (40 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

Details by Category

✅ ▲ Vercel Production

App	Passed	Failed	Skipped
✅ astro	41	0	4
✅ example	41	0	4
✅ express	41	0	4
✅ fastify	41	0	4
✅ hono	41	0	4
✅ nextjs-turbopack	44	0	1
✅ nextjs-webpack	44	0	1
✅ nitro	41	0	4
✅ nuxt	41	0	4
✅ sveltekit	41	0	4
✅ vite	41	0	4

✅ 💻 Local Development

App	Passed	Failed	Skipped
✅ astro-stable	41	0	4
✅ express-stable	41	0	4
✅ fastify-stable	41	0	4
✅ hono-stable	41	0	4
✅ nextjs-turbopack-stable	45	0	0
✅ nextjs-webpack-stable	45	0	0
✅ nitro-stable	41	0	4
✅ nuxt-stable	41	0	4
✅ sveltekit-stable	41	0	4
✅ vite-stable	41	0	4

✅ 📦 Local Production

App	Passed	Failed	Skipped
✅ astro-stable	41	0	4
✅ express-stable	41	0	4
✅ fastify-stable	41	0	4
✅ hono-stable	41	0	4
✅ nextjs-turbopack-stable	45	0	0
✅ nextjs-webpack-stable	45	0	0
✅ nitro-stable	41	0	4
✅ nuxt-stable	41	0	4
✅ sveltekit-stable	41	0	4
✅ vite-stable	41	0	4

✅ 🐘 Local Postgres

App	Passed	Failed	Skipped
✅ astro-stable	41	0	4
✅ express-stable	41	0	4
✅ fastify-stable	41	0	4
✅ hono-stable	41	0	4
✅ nextjs-turbopack-stable	45	0	0
✅ nextjs-webpack-stable	45	0	0
✅ nitro-stable	41	0	4
✅ nuxt-stable	41	0	4
✅ sveltekit-stable	41	0	4
✅ vite-stable	41	0	4

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack	45	0	0

❌ 🌍 Community Worlds

App	Passed	Failed	Skipped
✅ mongodb-dev	3	0	0
❌ mongodb	5	40	0
✅ redis-dev	3	0	0
❌ redis	5	40	0
✅ starter-dev	3	0	0
❌ starter	4	41	0
✅ turso-dev	3	0	0
❌ turso	5	40	0

✅ 📋 Other

App	Passed	Failed	Skipped
✅ e2e-local-dev-nest-stable	41	0	4
✅ e2e-local-postgres-nest-stable	41	0	4
✅ e2e-local-prod-nest-stable	41	0	4

---

📋 View full workflow run

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
example-nextjs-workflow-turbopack	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
example-nextjs-workflow-webpack	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
example-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-astro-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-express-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-fastify-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-hono-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-nitro-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-nuxt-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-sveltekit-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-vite-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workflow-docs	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workflow-nest	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am

[TooTallNate]

• Add support for "use step" functions in class instance methods #777: 2 dependent PRs (#876, #899)
• Add discovered serializable classes in all context modes #874
• Ensure class serialization / deserialization only happens in the proper global context #873 👈 (View in Graphite)
• Fix class ID generation when class is bound to a variable #872
• Add discovery for custom classes with workflow serialization #859
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[TooTallNate]

Merge activity

• Feb 3, 7:18 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Feb 3, 7:20 AM UTC: Graphite couldn't merge this pull request because a downstack PR Fix class ID generation when class is bound to a variable #872 failed to merge.
• Feb 3, 7:22 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Feb 3, 7:24 AM UTC: Graphite rebased this pull request as part of a merge.
• Feb 3, 7:24 AM UTC: @TooTallNate merged this pull request with Graphite.

[github-actions]

📊 Benchmark Results

📈 Comparing against baseline from main branch. Green 🟢 = faster, Red 🔺 = slower.

workflow with no steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	0.043s (~)	1.008s (~)	0.965s	10	1.00x
🐘 Postgres	Express	0.231s (+0.5%)	1.029s (+1.3%)	0.798s	10	5.38x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	0.693s (+18.5% 🔺)	1.716s (+10.7% 🔺)	1.023s	10	1.00x

🔍 Observability: Express

workflow with 1 step

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	1.116s (~)	2.008s (~)	0.892s	10	1.00x
🐘 Postgres	Express	2.466s (+9.1% 🔺)	3.014s (~)	0.548s	10	2.21x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.014s (+2.7%)	3.770s (-1.4%)	0.757s	10	1.00x

🔍 Observability: Express

workflow with 10 sequential steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	10.846s (~)	11.015s (~)	0.169s	5	1.00x
🐘 Postgres	Express	20.296s (~)	21.042s (~)	0.746s	5	1.87x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	22.608s (-2.9%)	23.176s (-2.8%)	0.568s	5	1.00x

🔍 Observability: Express

Promise.all with 10 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.173s (~)	6.175s (~)	1.001s	5	1.00x
🐘 Postgres	Express	29.529s (+3.5%)	29.682s (+1.9%)	0.153s	2	5.71x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.212s (-12.8% 🟢)	3.768s (-16.5% 🟢)	0.555s	8	1.00x

🔍 Observability: Express

Promise.all with 25 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.334s (+0.7%)	6.323s (+0.5%)	0.989s	5	1.00x
🐘 Postgres	Express	32.161s (-2.9%)	32.207s (-2.9%)	0.046s	1	6.03x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.060s (-1.6%)	3.684s (-1.0%)	0.625s	9	1.00x

🔍 Observability: Express

Promise.race with 10 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.544s (+3.3%)	6.502s (+2.8%)	0.958s	5	1.00x
🐘 Postgres	Express	32.984s (-5.5% 🟢)	33.206s (-5.7% 🟢)	0.222s	1	5.95x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.035s (-6.0% 🟢)	3.668s (-10.3% 🟢)	0.633s	9	1.00x

🔍 Observability: Express

Promise.race with 25 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.792s (+5.9% 🔺)	6.616s (+2.7%)	0.824s	5	1.00x
🐘 Postgres	Express	35.490s (+8.4% 🔺)	36.066s (+9.1% 🔺)	0.576s	1	6.13x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.021s (-33.6% 🟢)	3.751s (-30.1% 🟢)	0.730s	9	1.00x

🔍 Observability: Express

Stream Benchmarks(includes TTFB metrics)

workflow with stream

💻 Local Development

World	Framework	Workflow Time	TTFB	Slurp	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	0.180s (-3.7%)	0.992s (~)	0.017s (+10.7% 🔺)	1.024s (~)	0.844s	10	1.00x
🐘 Postgres	Express	1.634s (-23.8% 🟢)	2.425s (-16.4% 🟢)	0.000s (+100.0% 🔺)	2.516s (-16.6% 🟢)	0.882s	10	9.07x

▲ Production (Vercel)

World	Framework	Workflow Time	TTFB	Slurp	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	2.789s (-8.6% 🟢)	3.296s (+2.2%)	0.334s (-61.3% 🟢)	4.141s (-11.1% 🟢)	1.352s	10	1.00x

🔍 Observability: Express

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World	🥇 Fastest Framework	Wins
💻 Local	Express	8/8
🐘 Postgres	Express	8/8
▲ Vercel	Express	8/8

Fastest World by Framework

Winner determined by most benchmark wins

Framework	🥇 Fastest World	Wins
Express	💻 Local	4/8

Column Definitions

• Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
• TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
• Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
• Wall Time: Total testbench time (trigger workflow + poll for result)
• Overhead: Testbench overhead (Wall Time - Workflow Time)
• Samples: Number of benchmark iterations run
• vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

• 💻 Local: In-memory filesystem world (local development)
• 🐘 Postgres: PostgreSQL database world (local development)
• ▲ Vercel: Vercel production/preview deployment
• 🌐 Starter: Community world (local development)
• 🌐 Turso: Community world (local development)
• 🌐 MongoDB: Community world (local development)
• 🌐 Redis: Community world (local development)
• 🌐 Jazz: Community world (local development)

---

📋 View full workflow run

[TooTallNate]

Fixed class serialization/deserialization to properly respect VM context boundaries, ensuring workflow code only accesses classes registered in its own global context.

What changed?

• Modified getSerializationClass() to no longer fall back to checking globalThis when a class isn't found in the provided global context
• Updated the serialization tests to properly simulate how classes are registered and accessed in both host and VM contexts
• Added VM-specific class registration in tests to better match production behavior where workflow code runs in isolation

How to test?

• Run the updated serialization tests which now properly simulate the VM boundary
• Verify that class serialization/deserialization works correctly when classes are registered in their respective contexts
• Confirm that classes registered in one context aren't accessible from another context

Why make this change?

This change ensures proper isolation between the host environment and workflow VM contexts, matching production serverless behavior where workflow code runs in isolation. Previously, the code could leak class registrations between contexts, potentially causing unexpected behavior or security issues. This fix maintains proper boundaries between execution contexts.

[changeset-bot]

🦋 Changeset detected

Latest commit: 1566da2

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

This PR includes changesets to release 15 packages

Name	Type
@workflow/core	Patch
@workflow/builders	Patch
@workflow/cli	Patch
@workflow/docs-typecheck	Patch
@workflow/next	Patch
@workflow/nitro	Patch
@workflow/web-shared	Patch
workflow	Patch
@workflow/astro	Patch
@workflow/nest	Patch
@workflow/rollup	Patch
@workflow/sveltekit	Patch
@workflow/vite	Patch
@workflow/world-testing	Patch
@workflow/nuxt	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]

🧪 E2E Test Results

❌ Some tests failed

Summary

	Passed	Failed	Skipped	Total
✅ ▲ Vercel Production	457	0	38	495
✅ 💻 Local Development	418	0	32	450
✅ 📦 Local Production	418	0	32	450
✅ 🐘 Local Postgres	418	0	32	450
✅ 🪟 Windows	45	0	0	45
❌ 🌍 Community Worlds	31	161	0	192
✅ 📋 Other	123	0	12	135
Total	1910	161	146	2217

❌ Failed Tests

🌍 Community Worlds (161 failed)

mongodb (40 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

redis (40 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

starter (41 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• health check (CLI) - workflow health command reports healthy endpoints
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

turso (40 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

Details by Category

✅ ▲ Vercel Production

App	Passed	Failed	Skipped
✅ astro	41	0	4
✅ example	41	0	4
✅ express	41	0	4
✅ fastify	41	0	4
✅ hono	41	0	4
✅ nextjs-turbopack	44	0	1
✅ nextjs-webpack	44	0	1
✅ nitro	41	0	4
✅ nuxt	41	0	4
✅ sveltekit	41	0	4
✅ vite	41	0	4

✅ 💻 Local Development

App	Passed	Failed	Skipped
✅ astro-stable	41	0	4
✅ express-stable	41	0	4
✅ fastify-stable	41	0	4
✅ hono-stable	41	0	4
✅ nextjs-turbopack-stable	45	0	0
✅ nextjs-webpack-stable	45	0	0
✅ nitro-stable	41	0	4
✅ nuxt-stable	41	0	4
✅ sveltekit-stable	41	0	4
✅ vite-stable	41	0	4

✅ 📦 Local Production

App	Passed	Failed	Skipped
✅ astro-stable	41	0	4
✅ express-stable	41	0	4
✅ fastify-stable	41	0	4
✅ hono-stable	41	0	4
✅ nextjs-turbopack-stable	45	0	0
✅ nextjs-webpack-stable	45	0	0
✅ nitro-stable	41	0	4
✅ nuxt-stable	41	0	4
✅ sveltekit-stable	41	0	4
✅ vite-stable	41	0	4

✅ 🐘 Local Postgres

App	Passed	Failed	Skipped
✅ astro-stable	41	0	4
✅ express-stable	41	0	4
✅ fastify-stable	41	0	4
✅ hono-stable	41	0	4
✅ nextjs-turbopack-stable	45	0	0
✅ nextjs-webpack-stable	45	0	0
✅ nitro-stable	41	0	4
✅ nuxt-stable	41	0	4
✅ sveltekit-stable	41	0	4
✅ vite-stable	41	0	4

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack	45	0	0

❌ 🌍 Community Worlds

App	Passed	Failed	Skipped
✅ mongodb-dev	3	0	0
❌ mongodb	5	40	0
✅ redis-dev	3	0	0
❌ redis	5	40	0
✅ starter-dev	3	0	0
❌ starter	4	41	0
✅ turso-dev	3	0	0
❌ turso	5	40	0

✅ 📋 Other

App	Passed	Failed	Skipped
✅ e2e-local-dev-nest-stable	41	0	4
✅ e2e-local-postgres-nest-stable	41	0	4
✅ e2e-local-prod-nest-stable	41	0	4

---

📋 View full workflow run

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
example-nextjs-workflow-turbopack	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
example-nextjs-workflow-webpack	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
example-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-astro-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-express-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-fastify-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-hono-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-nitro-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-nuxt-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-sveltekit-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-vite-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workflow-docs	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workflow-nest	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am

[TooTallNate]

• Add support for "use step" functions in class instance methods #777: 2 dependent PRs (#876, #899)
• Add discovered serializable classes in all context modes #874
• Ensure class serialization / deserialization only happens in the proper global context #873 👈 (View in Graphite)
• Fix class ID generation when class is bound to a variable #872
• Add discovery for custom classes with workflow serialization #859
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[TooTallNate]

Merge activity

• Feb 3, 7:18 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Feb 3, 7:20 AM UTC: Graphite couldn't merge this pull request because a downstack PR Fix class ID generation when class is bound to a variable #872 failed to merge.
• Feb 3, 7:22 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Feb 3, 7:24 AM UTC: Graphite rebased this pull request as part of a merge.
• Feb 3, 7:24 AM UTC: @TooTallNate merged this pull request with Graphite.

[github-actions]

📊 Benchmark Results

📈 Comparing against baseline from main branch. Green 🟢 = faster, Red 🔺 = slower.

workflow with no steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	0.043s (~)	1.008s (~)	0.965s	10	1.00x
🐘 Postgres	Express	0.231s (+0.5%)	1.029s (+1.3%)	0.798s	10	5.38x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	0.693s (+18.5% 🔺)	1.716s (+10.7% 🔺)	1.023s	10	1.00x

🔍 Observability: Express

workflow with 1 step

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	1.116s (~)	2.008s (~)	0.892s	10	1.00x
🐘 Postgres	Express	2.466s (+9.1% 🔺)	3.014s (~)	0.548s	10	2.21x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.014s (+2.7%)	3.770s (-1.4%)	0.757s	10	1.00x

🔍 Observability: Express

workflow with 10 sequential steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	10.846s (~)	11.015s (~)	0.169s	5	1.00x
🐘 Postgres	Express	20.296s (~)	21.042s (~)	0.746s	5	1.87x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	22.608s (-2.9%)	23.176s (-2.8%)	0.568s	5	1.00x

🔍 Observability: Express

Promise.all with 10 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.173s (~)	6.175s (~)	1.001s	5	1.00x
🐘 Postgres	Express	29.529s (+3.5%)	29.682s (+1.9%)	0.153s	2	5.71x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.212s (-12.8% 🟢)	3.768s (-16.5% 🟢)	0.555s	8	1.00x

🔍 Observability: Express

Promise.all with 25 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.334s (+0.7%)	6.323s (+0.5%)	0.989s	5	1.00x
🐘 Postgres	Express	32.161s (-2.9%)	32.207s (-2.9%)	0.046s	1	6.03x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.060s (-1.6%)	3.684s (-1.0%)	0.625s	9	1.00x

🔍 Observability: Express

Promise.race with 10 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.544s (+3.3%)	6.502s (+2.8%)	0.958s	5	1.00x
🐘 Postgres	Express	32.984s (-5.5% 🟢)	33.206s (-5.7% 🟢)	0.222s	1	5.95x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.035s (-6.0% 🟢)	3.668s (-10.3% 🟢)	0.633s	9	1.00x

🔍 Observability: Express

Promise.race with 25 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.792s (+5.9% 🔺)	6.616s (+2.7%)	0.824s	5	1.00x
🐘 Postgres	Express	35.490s (+8.4% 🔺)	36.066s (+9.1% 🔺)	0.576s	1	6.13x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.021s (-33.6% 🟢)	3.751s (-30.1% 🟢)	0.730s	9	1.00x

🔍 Observability: Express

Stream Benchmarks(includes TTFB metrics)

workflow with stream

💻 Local Development

World	Framework	Workflow Time	TTFB	Slurp	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	0.180s (-3.7%)	0.992s (~)	0.017s (+10.7% 🔺)	1.024s (~)	0.844s	10	1.00x
🐘 Postgres	Express	1.634s (-23.8% 🟢)	2.425s (-16.4% 🟢)	0.000s (+100.0% 🔺)	2.516s (-16.6% 🟢)	0.882s	10	9.07x

▲ Production (Vercel)

World	Framework	Workflow Time	TTFB	Slurp	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	2.789s (-8.6% 🟢)	3.296s (+2.2%)	0.334s (-61.3% 🟢)	4.141s (-11.1% 🟢)	1.352s	10	1.00x

🔍 Observability: Express

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World	🥇 Fastest Framework	Wins
💻 Local	Express	8/8
🐘 Postgres	Express	8/8
▲ Vercel	Express	8/8

Fastest World by Framework

Winner determined by most benchmark wins

Framework	🥇 Fastest World	Wins
Express	💻 Local	4/8

Column Definitions

• Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
• TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
• Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
• Wall Time: Total testbench time (trigger workflow + poll for result)
• Overhead: Testbench overhead (Wall Time - Workflow Time)
• Samples: Number of benchmark iterations run
• vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

• 💻 Local: In-memory filesystem world (local development)
• 🐘 Postgres: PostgreSQL database world (local development)
• ▲ Vercel: Vercel production/preview deployment
• 🌐 Starter: Community world (local development)
• 🌐 Turso: Community world (local development)
• 🌐 MongoDB: Community world (local development)
• 🌐 Redis: Community world (local development)
• 🌐 Jazz: Community world (local development)

---

📋 View full workflow run

[TooTallNate]

Fixed class serialization/deserialization to properly respect VM context boundaries, ensuring workflow code only accesses classes registered in its own global context.

What changed?

• Modified getSerializationClass() to no longer fall back to checking globalThis when a class isn't found in the provided global context
• Updated the serialization tests to properly simulate how classes are registered and accessed in both host and VM contexts
• Added VM-specific class registration in tests to better match production behavior where workflow code runs in isolation

How to test?

• Run the updated serialization tests which now properly simulate the VM boundary
• Verify that class serialization/deserialization works correctly when classes are registered in their respective contexts
• Confirm that classes registered in one context aren't accessible from another context

Why make this change?

This change ensures proper isolation between the host environment and workflow VM contexts, matching production serverless behavior where workflow code runs in isolation. Previously, the code could leak class registrations between contexts, potentially causing unexpected behavior or security issues. This fix maintains proper boundaries between execution contexts.

[changeset-bot]

🦋 Changeset detected

Latest commit: 1566da2

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

This PR includes changesets to release 15 packages

Name	Type
@workflow/core	Patch
@workflow/builders	Patch
@workflow/cli	Patch
@workflow/docs-typecheck	Patch
@workflow/next	Patch
@workflow/nitro	Patch
@workflow/web-shared	Patch
workflow	Patch
@workflow/astro	Patch
@workflow/nest	Patch
@workflow/rollup	Patch
@workflow/sveltekit	Patch
@workflow/vite	Patch
@workflow/world-testing	Patch
@workflow/nuxt	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]

🧪 E2E Test Results

❌ Some tests failed

Summary

	Passed	Failed	Skipped	Total
✅ ▲ Vercel Production	457	0	38	495
✅ 💻 Local Development	418	0	32	450
✅ 📦 Local Production	418	0	32	450
✅ 🐘 Local Postgres	418	0	32	450
✅ 🪟 Windows	45	0	0	45
❌ 🌍 Community Worlds	31	161	0	192
✅ 📋 Other	123	0	12	135
Total	1910	161	146	2217

❌ Failed Tests

🌍 Community Worlds (161 failed)

mongodb (40 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

redis (40 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

starter (41 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• health check (CLI) - workflow health command reports healthy endpoints
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

turso (40 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

Details by Category

✅ ▲ Vercel Production

App	Passed	Failed	Skipped
✅ astro	41	0	4
✅ example	41	0	4
✅ express	41	0	4
✅ fastify	41	0	4
✅ hono	41	0	4
✅ nextjs-turbopack	44	0	1
✅ nextjs-webpack	44	0	1
✅ nitro	41	0	4
✅ nuxt	41	0	4
✅ sveltekit	41	0	4
✅ vite	41	0	4

✅ 💻 Local Development

App	Passed	Failed	Skipped
✅ astro-stable	41	0	4
✅ express-stable	41	0	4
✅ fastify-stable	41	0	4
✅ hono-stable	41	0	4
✅ nextjs-turbopack-stable	45	0	0
✅ nextjs-webpack-stable	45	0	0
✅ nitro-stable	41	0	4
✅ nuxt-stable	41	0	4
✅ sveltekit-stable	41	0	4
✅ vite-stable	41	0	4

✅ 📦 Local Production

App	Passed	Failed	Skipped
✅ astro-stable	41	0	4
✅ express-stable	41	0	4
✅ fastify-stable	41	0	4
✅ hono-stable	41	0	4
✅ nextjs-turbopack-stable	45	0	0
✅ nextjs-webpack-stable	45	0	0
✅ nitro-stable	41	0	4
✅ nuxt-stable	41	0	4
✅ sveltekit-stable	41	0	4
✅ vite-stable	41	0	4

✅ 🐘 Local Postgres

App	Passed	Failed	Skipped
✅ astro-stable	41	0	4
✅ express-stable	41	0	4
✅ fastify-stable	41	0	4
✅ hono-stable	41	0	4
✅ nextjs-turbopack-stable	45	0	0
✅ nextjs-webpack-stable	45	0	0
✅ nitro-stable	41	0	4
✅ nuxt-stable	41	0	4
✅ sveltekit-stable	41	0	4
✅ vite-stable	41	0	4

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack	45	0	0

❌ 🌍 Community Worlds

App	Passed	Failed	Skipped
✅ mongodb-dev	3	0	0
❌ mongodb	5	40	0
✅ redis-dev	3	0	0
❌ redis	5	40	0
✅ starter-dev	3	0	0
❌ starter	4	41	0
✅ turso-dev	3	0	0
❌ turso	5	40	0

✅ 📋 Other

App	Passed	Failed	Skipped
✅ e2e-local-dev-nest-stable	41	0	4
✅ e2e-local-postgres-nest-stable	41	0	4
✅ e2e-local-prod-nest-stable	41	0	4

---

📋 View full workflow run

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
example-nextjs-workflow-turbopack	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
example-nextjs-workflow-webpack	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
example-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-astro-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-express-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-fastify-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-hono-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-nitro-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-nuxt-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-sveltekit-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-vite-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workflow-docs	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workflow-nest	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am

[TooTallNate]

• Add support for "use step" functions in class instance methods #777: 2 dependent PRs (#876, #899)
• Add discovered serializable classes in all context modes #874
• Ensure class serialization / deserialization only happens in the proper global context #873 👈 (View in Graphite)
• Fix class ID generation when class is bound to a variable #872
• Add discovery for custom classes with workflow serialization #859
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[TooTallNate]

Merge activity

• Feb 3, 7:18 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Feb 3, 7:20 AM UTC: Graphite couldn't merge this pull request because a downstack PR Fix class ID generation when class is bound to a variable #872 failed to merge.
• Feb 3, 7:22 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Feb 3, 7:24 AM UTC: Graphite rebased this pull request as part of a merge.
• Feb 3, 7:24 AM UTC: @TooTallNate merged this pull request with Graphite.

[github-actions]

📊 Benchmark Results

📈 Comparing against baseline from main branch. Green 🟢 = faster, Red 🔺 = slower.

workflow with no steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	0.043s (~)	1.008s (~)	0.965s	10	1.00x
🐘 Postgres	Express	0.231s (+0.5%)	1.029s (+1.3%)	0.798s	10	5.38x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	0.693s (+18.5% 🔺)	1.716s (+10.7% 🔺)	1.023s	10	1.00x

🔍 Observability: Express

workflow with 1 step

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	1.116s (~)	2.008s (~)	0.892s	10	1.00x
🐘 Postgres	Express	2.466s (+9.1% 🔺)	3.014s (~)	0.548s	10	2.21x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.014s (+2.7%)	3.770s (-1.4%)	0.757s	10	1.00x

🔍 Observability: Express

workflow with 10 sequential steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	10.846s (~)	11.015s (~)	0.169s	5	1.00x
🐘 Postgres	Express	20.296s (~)	21.042s (~)	0.746s	5	1.87x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	22.608s (-2.9%)	23.176s (-2.8%)	0.568s	5	1.00x

🔍 Observability: Express

Promise.all with 10 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.173s (~)	6.175s (~)	1.001s	5	1.00x
🐘 Postgres	Express	29.529s (+3.5%)	29.682s (+1.9%)	0.153s	2	5.71x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.212s (-12.8% 🟢)	3.768s (-16.5% 🟢)	0.555s	8	1.00x

🔍 Observability: Express

Promise.all with 25 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.334s (+0.7%)	6.323s (+0.5%)	0.989s	5	1.00x
🐘 Postgres	Express	32.161s (-2.9%)	32.207s (-2.9%)	0.046s	1	6.03x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.060s (-1.6%)	3.684s (-1.0%)	0.625s	9	1.00x

🔍 Observability: Express

Promise.race with 10 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.544s (+3.3%)	6.502s (+2.8%)	0.958s	5	1.00x
🐘 Postgres	Express	32.984s (-5.5% 🟢)	33.206s (-5.7% 🟢)	0.222s	1	5.95x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.035s (-6.0% 🟢)	3.668s (-10.3% 🟢)	0.633s	9	1.00x

🔍 Observability: Express

Promise.race with 25 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.792s (+5.9% 🔺)	6.616s (+2.7%)	0.824s	5	1.00x
🐘 Postgres	Express	35.490s (+8.4% 🔺)	36.066s (+9.1% 🔺)	0.576s	1	6.13x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.021s (-33.6% 🟢)	3.751s (-30.1% 🟢)	0.730s	9	1.00x

🔍 Observability: Express

Stream Benchmarks(includes TTFB metrics)

workflow with stream

💻 Local Development

World	Framework	Workflow Time	TTFB	Slurp	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	0.180s (-3.7%)	0.992s (~)	0.017s (+10.7% 🔺)	1.024s (~)	0.844s	10	1.00x
🐘 Postgres	Express	1.634s (-23.8% 🟢)	2.425s (-16.4% 🟢)	0.000s (+100.0% 🔺)	2.516s (-16.6% 🟢)	0.882s	10	9.07x

▲ Production (Vercel)

World	Framework	Workflow Time	TTFB	Slurp	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	2.789s (-8.6% 🟢)	3.296s (+2.2%)	0.334s (-61.3% 🟢)	4.141s (-11.1% 🟢)	1.352s	10	1.00x

🔍 Observability: Express

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World	🥇 Fastest Framework	Wins
💻 Local	Express	8/8
🐘 Postgres	Express	8/8
▲ Vercel	Express	8/8

Fastest World by Framework

Winner determined by most benchmark wins

Framework	🥇 Fastest World	Wins
Express	💻 Local	4/8

Column Definitions

• Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
• TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
• Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
• Wall Time: Total testbench time (trigger workflow + poll for result)
• Overhead: Testbench overhead (Wall Time - Workflow Time)
• Samples: Number of benchmark iterations run
• vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

• 💻 Local: In-memory filesystem world (local development)
• 🐘 Postgres: PostgreSQL database world (local development)
• ▲ Vercel: Vercel production/preview deployment
• 🌐 Starter: Community world (local development)
• 🌐 Turso: Community world (local development)
• 🌐 MongoDB: Community world (local development)
• 🌐 Redis: Community world (local development)
• 🌐 Jazz: Community world (local development)

---

📋 View full workflow run

[TooTallNate]

Fixed class serialization/deserialization to properly respect VM context boundaries, ensuring workflow code only accesses classes registered in its own global context.

What changed?

• Modified getSerializationClass() to no longer fall back to checking globalThis when a class isn't found in the provided global context
• Updated the serialization tests to properly simulate how classes are registered and accessed in both host and VM contexts
• Added VM-specific class registration in tests to better match production behavior where workflow code runs in isolation

How to test?

• Run the updated serialization tests which now properly simulate the VM boundary
• Verify that class serialization/deserialization works correctly when classes are registered in their respective contexts
• Confirm that classes registered in one context aren't accessible from another context

Why make this change?

This change ensures proper isolation between the host environment and workflow VM contexts, matching production serverless behavior where workflow code runs in isolation. Previously, the code could leak class registrations between contexts, potentially causing unexpected behavior or security issues. This fix maintains proper boundaries between execution contexts.

[changeset-bot]

🦋 Changeset detected

Latest commit: 1566da2

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

This PR includes changesets to release 15 packages

Name	Type
@workflow/core	Patch
@workflow/builders	Patch
@workflow/cli	Patch
@workflow/docs-typecheck	Patch
@workflow/next	Patch
@workflow/nitro	Patch
@workflow/web-shared	Patch
workflow	Patch
@workflow/astro	Patch
@workflow/nest	Patch
@workflow/rollup	Patch
@workflow/sveltekit	Patch
@workflow/vite	Patch
@workflow/world-testing	Patch
@workflow/nuxt	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]

🧪 E2E Test Results

❌ Some tests failed

Summary

	Passed	Failed	Skipped	Total
✅ ▲ Vercel Production	457	0	38	495
✅ 💻 Local Development	418	0	32	450
✅ 📦 Local Production	418	0	32	450
✅ 🐘 Local Postgres	418	0	32	450
✅ 🪟 Windows	45	0	0	45
❌ 🌍 Community Worlds	31	161	0	192
✅ 📋 Other	123	0	12	135
Total	1910	161	146	2217

❌ Failed Tests

🌍 Community Worlds (161 failed)

mongodb (40 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

redis (40 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

starter (41 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• health check (CLI) - workflow health command reports healthy endpoints
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

turso (40 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

Details by Category

✅ ▲ Vercel Production

App	Passed	Failed	Skipped
✅ astro	41	0	4
✅ example	41	0	4
✅ express	41	0	4
✅ fastify	41	0	4
✅ hono	41	0	4
✅ nextjs-turbopack	44	0	1
✅ nextjs-webpack	44	0	1
✅ nitro	41	0	4
✅ nuxt	41	0	4
✅ sveltekit	41	0	4
✅ vite	41	0	4

✅ 💻 Local Development

App	Passed	Failed	Skipped
✅ astro-stable	41	0	4
✅ express-stable	41	0	4
✅ fastify-stable	41	0	4
✅ hono-stable	41	0	4
✅ nextjs-turbopack-stable	45	0	0
✅ nextjs-webpack-stable	45	0	0
✅ nitro-stable	41	0	4
✅ nuxt-stable	41	0	4
✅ sveltekit-stable	41	0	4
✅ vite-stable	41	0	4

✅ 📦 Local Production

App	Passed	Failed	Skipped
✅ astro-stable	41	0	4
✅ express-stable	41	0	4
✅ fastify-stable	41	0	4
✅ hono-stable	41	0	4
✅ nextjs-turbopack-stable	45	0	0
✅ nextjs-webpack-stable	45	0	0
✅ nitro-stable	41	0	4
✅ nuxt-stable	41	0	4
✅ sveltekit-stable	41	0	4
✅ vite-stable	41	0	4

✅ 🐘 Local Postgres

App	Passed	Failed	Skipped
✅ astro-stable	41	0	4
✅ express-stable	41	0	4
✅ fastify-stable	41	0	4
✅ hono-stable	41	0	4
✅ nextjs-turbopack-stable	45	0	0
✅ nextjs-webpack-stable	45	0	0
✅ nitro-stable	41	0	4
✅ nuxt-stable	41	0	4
✅ sveltekit-stable	41	0	4
✅ vite-stable	41	0	4

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack	45	0	0

❌ 🌍 Community Worlds

App	Passed	Failed	Skipped
✅ mongodb-dev	3	0	0
❌ mongodb	5	40	0
✅ redis-dev	3	0	0
❌ redis	5	40	0
✅ starter-dev	3	0	0
❌ starter	4	41	0
✅ turso-dev	3	0	0
❌ turso	5	40	0

✅ 📋 Other

App	Passed	Failed	Skipped
✅ e2e-local-dev-nest-stable	41	0	4
✅ e2e-local-postgres-nest-stable	41	0	4
✅ e2e-local-prod-nest-stable	41	0	4

---

📋 View full workflow run

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
example-nextjs-workflow-turbopack	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
example-nextjs-workflow-webpack	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
example-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-astro-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-express-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-fastify-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-hono-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-nitro-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-nuxt-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-sveltekit-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-vite-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workflow-docs	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workflow-nest	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am

[TooTallNate]

• Add support for "use step" functions in class instance methods #777: 2 dependent PRs (#876, #899)
• Add discovered serializable classes in all context modes #874
• Ensure class serialization / deserialization only happens in the proper global context #873 👈 (View in Graphite)
• Fix class ID generation when class is bound to a variable #872
• Add discovery for custom classes with workflow serialization #859
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[TooTallNate]

Merge activity

• Feb 3, 7:18 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Feb 3, 7:20 AM UTC: Graphite couldn't merge this pull request because a downstack PR Fix class ID generation when class is bound to a variable #872 failed to merge.
• Feb 3, 7:22 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Feb 3, 7:24 AM UTC: Graphite rebased this pull request as part of a merge.
• Feb 3, 7:24 AM UTC: @TooTallNate merged this pull request with Graphite.

[github-actions]

📊 Benchmark Results

📈 Comparing against baseline from main branch. Green 🟢 = faster, Red 🔺 = slower.

workflow with no steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	0.043s (~)	1.008s (~)	0.965s	10	1.00x
🐘 Postgres	Express	0.231s (+0.5%)	1.029s (+1.3%)	0.798s	10	5.38x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	0.693s (+18.5% 🔺)	1.716s (+10.7% 🔺)	1.023s	10	1.00x

🔍 Observability: Express

workflow with 1 step

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	1.116s (~)	2.008s (~)	0.892s	10	1.00x
🐘 Postgres	Express	2.466s (+9.1% 🔺)	3.014s (~)	0.548s	10	2.21x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.014s (+2.7%)	3.770s (-1.4%)	0.757s	10	1.00x

🔍 Observability: Express

workflow with 10 sequential steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	10.846s (~)	11.015s (~)	0.169s	5	1.00x
🐘 Postgres	Express	20.296s (~)	21.042s (~)	0.746s	5	1.87x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	22.608s (-2.9%)	23.176s (-2.8%)	0.568s	5	1.00x

🔍 Observability: Express

Promise.all with 10 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.173s (~)	6.175s (~)	1.001s	5	1.00x
🐘 Postgres	Express	29.529s (+3.5%)	29.682s (+1.9%)	0.153s	2	5.71x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.212s (-12.8% 🟢)	3.768s (-16.5% 🟢)	0.555s	8	1.00x

🔍 Observability: Express

Promise.all with 25 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.334s (+0.7%)	6.323s (+0.5%)	0.989s	5	1.00x
🐘 Postgres	Express	32.161s (-2.9%)	32.207s (-2.9%)	0.046s	1	6.03x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.060s (-1.6%)	3.684s (-1.0%)	0.625s	9	1.00x

🔍 Observability: Express

Promise.race with 10 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.544s (+3.3%)	6.502s (+2.8%)	0.958s	5	1.00x
🐘 Postgres	Express	32.984s (-5.5% 🟢)	33.206s (-5.7% 🟢)	0.222s	1	5.95x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.035s (-6.0% 🟢)	3.668s (-10.3% 🟢)	0.633s	9	1.00x

🔍 Observability: Express

Promise.race with 25 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.792s (+5.9% 🔺)	6.616s (+2.7%)	0.824s	5	1.00x
🐘 Postgres	Express	35.490s (+8.4% 🔺)	36.066s (+9.1% 🔺)	0.576s	1	6.13x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.021s (-33.6% 🟢)	3.751s (-30.1% 🟢)	0.730s	9	1.00x

🔍 Observability: Express

Stream Benchmarks(includes TTFB metrics)

workflow with stream

💻 Local Development

World	Framework	Workflow Time	TTFB	Slurp	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	0.180s (-3.7%)	0.992s (~)	0.017s (+10.7% 🔺)	1.024s (~)	0.844s	10	1.00x
🐘 Postgres	Express	1.634s (-23.8% 🟢)	2.425s (-16.4% 🟢)	0.000s (+100.0% 🔺)	2.516s (-16.6% 🟢)	0.882s	10	9.07x

▲ Production (Vercel)

World	Framework	Workflow Time	TTFB	Slurp	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	2.789s (-8.6% 🟢)	3.296s (+2.2%)	0.334s (-61.3% 🟢)	4.141s (-11.1% 🟢)	1.352s	10	1.00x

🔍 Observability: Express

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World	🥇 Fastest Framework	Wins
💻 Local	Express	8/8
🐘 Postgres	Express	8/8
▲ Vercel	Express	8/8

Fastest World by Framework

Winner determined by most benchmark wins

Framework	🥇 Fastest World	Wins
Express	💻 Local	4/8

Column Definitions

• Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
• TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
• Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
• Wall Time: Total testbench time (trigger workflow + poll for result)
• Overhead: Testbench overhead (Wall Time - Workflow Time)
• Samples: Number of benchmark iterations run
• vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

• 💻 Local: In-memory filesystem world (local development)
• 🐘 Postgres: PostgreSQL database world (local development)
• ▲ Vercel: Vercel production/preview deployment
• 🌐 Starter: Community world (local development)
• 🌐 Turso: Community world (local development)
• 🌐 MongoDB: Community world (local development)
• 🌐 Redis: Community world (local development)
• 🌐 Jazz: Community world (local development)

---

📋 View full workflow run

[TooTallNate]

Fixed class serialization/deserialization to properly respect VM context boundaries, ensuring workflow code only accesses classes registered in its own global context.

What changed?

• Modified getSerializationClass() to no longer fall back to checking globalThis when a class isn't found in the provided global context
• Updated the serialization tests to properly simulate how classes are registered and accessed in both host and VM contexts
• Added VM-specific class registration in tests to better match production behavior where workflow code runs in isolation

How to test?

• Run the updated serialization tests which now properly simulate the VM boundary
• Verify that class serialization/deserialization works correctly when classes are registered in their respective contexts
• Confirm that classes registered in one context aren't accessible from another context

Why make this change?

This change ensures proper isolation between the host environment and workflow VM contexts, matching production serverless behavior where workflow code runs in isolation. Previously, the code could leak class registrations between contexts, potentially causing unexpected behavior or security issues. This fix maintains proper boundaries between execution contexts.

[changeset-bot]

🦋 Changeset detected

Latest commit: 1566da2

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

This PR includes changesets to release 15 packages

Name	Type
@workflow/core	Patch
@workflow/builders	Patch
@workflow/cli	Patch
@workflow/docs-typecheck	Patch
@workflow/next	Patch
@workflow/nitro	Patch
@workflow/web-shared	Patch
workflow	Patch
@workflow/astro	Patch
@workflow/nest	Patch
@workflow/rollup	Patch
@workflow/sveltekit	Patch
@workflow/vite	Patch
@workflow/world-testing	Patch
@workflow/nuxt	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]

🧪 E2E Test Results

❌ Some tests failed

Summary

	Passed	Failed	Skipped	Total
✅ ▲ Vercel Production	457	0	38	495
✅ 💻 Local Development	418	0	32	450
✅ 📦 Local Production	418	0	32	450
✅ 🐘 Local Postgres	418	0	32	450
✅ 🪟 Windows	45	0	0	45
❌ 🌍 Community Worlds	31	161	0	192
✅ 📋 Other	123	0	12	135
Total	1910	161	146	2217

❌ Failed Tests

🌍 Community Worlds (161 failed)

mongodb (40 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

redis (40 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

starter (41 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• health check (CLI) - workflow health command reports healthy endpoints
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

turso (40 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

Details by Category

✅ ▲ Vercel Production

App	Passed	Failed	Skipped
✅ astro	41	0	4
✅ example	41	0	4
✅ express	41	0	4
✅ fastify	41	0	4
✅ hono	41	0	4
✅ nextjs-turbopack	44	0	1
✅ nextjs-webpack	44	0	1
✅ nitro	41	0	4
✅ nuxt	41	0	4
✅ sveltekit	41	0	4
✅ vite	41	0	4

✅ 💻 Local Development

App	Passed	Failed	Skipped
✅ astro-stable	41	0	4
✅ express-stable	41	0	4
✅ fastify-stable	41	0	4
✅ hono-stable	41	0	4
✅ nextjs-turbopack-stable	45	0	0
✅ nextjs-webpack-stable	45	0	0
✅ nitro-stable	41	0	4
✅ nuxt-stable	41	0	4
✅ sveltekit-stable	41	0	4
✅ vite-stable	41	0	4

✅ 📦 Local Production

App	Passed	Failed	Skipped
✅ astro-stable	41	0	4
✅ express-stable	41	0	4
✅ fastify-stable	41	0	4
✅ hono-stable	41	0	4
✅ nextjs-turbopack-stable	45	0	0
✅ nextjs-webpack-stable	45	0	0
✅ nitro-stable	41	0	4
✅ nuxt-stable	41	0	4
✅ sveltekit-stable	41	0	4
✅ vite-stable	41	0	4

✅ 🐘 Local Postgres

App	Passed	Failed	Skipped
✅ astro-stable	41	0	4
✅ express-stable	41	0	4
✅ fastify-stable	41	0	4
✅ hono-stable	41	0	4
✅ nextjs-turbopack-stable	45	0	0
✅ nextjs-webpack-stable	45	0	0
✅ nitro-stable	41	0	4
✅ nuxt-stable	41	0	4
✅ sveltekit-stable	41	0	4
✅ vite-stable	41	0	4

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack	45	0	0

❌ 🌍 Community Worlds

App	Passed	Failed	Skipped
✅ mongodb-dev	3	0	0
❌ mongodb	5	40	0
✅ redis-dev	3	0	0
❌ redis	5	40	0
✅ starter-dev	3	0	0
❌ starter	4	41	0
✅ turso-dev	3	0	0
❌ turso	5	40	0

✅ 📋 Other

App	Passed	Failed	Skipped
✅ e2e-local-dev-nest-stable	41	0	4
✅ e2e-local-postgres-nest-stable	41	0	4
✅ e2e-local-prod-nest-stable	41	0	4

---

📋 View full workflow run

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
example-nextjs-workflow-turbopack	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
example-nextjs-workflow-webpack	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
example-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-astro-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-express-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-fastify-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-hono-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-nitro-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-nuxt-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-sveltekit-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-vite-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workflow-docs	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workflow-nest	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am

[TooTallNate]

• Add support for "use step" functions in class instance methods #777: 2 dependent PRs (#876, #899)
• Add discovered serializable classes in all context modes #874
• Ensure class serialization / deserialization only happens in the proper global context #873 👈 (View in Graphite)
• Fix class ID generation when class is bound to a variable #872
• Add discovery for custom classes with workflow serialization #859
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[TooTallNate]

Merge activity

• Feb 3, 7:18 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Feb 3, 7:20 AM UTC: Graphite couldn't merge this pull request because a downstack PR Fix class ID generation when class is bound to a variable #872 failed to merge.
• Feb 3, 7:22 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Feb 3, 7:24 AM UTC: Graphite rebased this pull request as part of a merge.
• Feb 3, 7:24 AM UTC: @TooTallNate merged this pull request with Graphite.

[github-actions]

📊 Benchmark Results

📈 Comparing against baseline from main branch. Green 🟢 = faster, Red 🔺 = slower.

workflow with no steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	0.043s (~)	1.008s (~)	0.965s	10	1.00x
🐘 Postgres	Express	0.231s (+0.5%)	1.029s (+1.3%)	0.798s	10	5.38x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	0.693s (+18.5% 🔺)	1.716s (+10.7% 🔺)	1.023s	10	1.00x

🔍 Observability: Express

workflow with 1 step

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	1.116s (~)	2.008s (~)	0.892s	10	1.00x
🐘 Postgres	Express	2.466s (+9.1% 🔺)	3.014s (~)	0.548s	10	2.21x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.014s (+2.7%)	3.770s (-1.4%)	0.757s	10	1.00x

🔍 Observability: Express

workflow with 10 sequential steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	10.846s (~)	11.015s (~)	0.169s	5	1.00x
🐘 Postgres	Express	20.296s (~)	21.042s (~)	0.746s	5	1.87x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	22.608s (-2.9%)	23.176s (-2.8%)	0.568s	5	1.00x

🔍 Observability: Express

Promise.all with 10 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.173s (~)	6.175s (~)	1.001s	5	1.00x
🐘 Postgres	Express	29.529s (+3.5%)	29.682s (+1.9%)	0.153s	2	5.71x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.212s (-12.8% 🟢)	3.768s (-16.5% 🟢)	0.555s	8	1.00x

🔍 Observability: Express

Promise.all with 25 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.334s (+0.7%)	6.323s (+0.5%)	0.989s	5	1.00x
🐘 Postgres	Express	32.161s (-2.9%)	32.207s (-2.9%)	0.046s	1	6.03x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.060s (-1.6%)	3.684s (-1.0%)	0.625s	9	1.00x

🔍 Observability: Express

Promise.race with 10 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.544s (+3.3%)	6.502s (+2.8%)	0.958s	5	1.00x
🐘 Postgres	Express	32.984s (-5.5% 🟢)	33.206s (-5.7% 🟢)	0.222s	1	5.95x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.035s (-6.0% 🟢)	3.668s (-10.3% 🟢)	0.633s	9	1.00x

🔍 Observability: Express

Promise.race with 25 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.792s (+5.9% 🔺)	6.616s (+2.7%)	0.824s	5	1.00x
🐘 Postgres	Express	35.490s (+8.4% 🔺)	36.066s (+9.1% 🔺)	0.576s	1	6.13x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.021s (-33.6% 🟢)	3.751s (-30.1% 🟢)	0.730s	9	1.00x

🔍 Observability: Express

Stream Benchmarks(includes TTFB metrics)

workflow with stream

💻 Local Development

World	Framework	Workflow Time	TTFB	Slurp	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	0.180s (-3.7%)	0.992s (~)	0.017s (+10.7% 🔺)	1.024s (~)	0.844s	10	1.00x
🐘 Postgres	Express	1.634s (-23.8% 🟢)	2.425s (-16.4% 🟢)	0.000s (+100.0% 🔺)	2.516s (-16.6% 🟢)	0.882s	10	9.07x

▲ Production (Vercel)

World	Framework	Workflow Time	TTFB	Slurp	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	2.789s (-8.6% 🟢)	3.296s (+2.2%)	0.334s (-61.3% 🟢)	4.141s (-11.1% 🟢)	1.352s	10	1.00x

🔍 Observability: Express

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World	🥇 Fastest Framework	Wins
💻 Local	Express	8/8
🐘 Postgres	Express	8/8
▲ Vercel	Express	8/8

Fastest World by Framework

Winner determined by most benchmark wins

Framework	🥇 Fastest World	Wins
Express	💻 Local	4/8

Column Definitions

• Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
• TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
• Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
• Wall Time: Total testbench time (trigger workflow + poll for result)
• Overhead: Testbench overhead (Wall Time - Workflow Time)
• Samples: Number of benchmark iterations run
• vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

• 💻 Local: In-memory filesystem world (local development)
• 🐘 Postgres: PostgreSQL database world (local development)
• ▲ Vercel: Vercel production/preview deployment
• 🌐 Starter: Community world (local development)
• 🌐 Turso: Community world (local development)
• 🌐 MongoDB: Community world (local development)
• 🌐 Redis: Community world (local development)
• 🌐 Jazz: Community world (local development)

---

📋 View full workflow run

[TooTallNate]

Fixed class serialization/deserialization to properly respect VM context boundaries, ensuring workflow code only accesses classes registered in its own global context.

What changed?

• Modified getSerializationClass() to no longer fall back to checking globalThis when a class isn't found in the provided global context
• Updated the serialization tests to properly simulate how classes are registered and accessed in both host and VM contexts
• Added VM-specific class registration in tests to better match production behavior where workflow code runs in isolation

How to test?

• Run the updated serialization tests which now properly simulate the VM boundary
• Verify that class serialization/deserialization works correctly when classes are registered in their respective contexts
• Confirm that classes registered in one context aren't accessible from another context

Why make this change?

This change ensures proper isolation between the host environment and workflow VM contexts, matching production serverless behavior where workflow code runs in isolation. Previously, the code could leak class registrations between contexts, potentially causing unexpected behavior or security issues. This fix maintains proper boundaries between execution contexts.

[changeset-bot]

🦋 Changeset detected

Latest commit: 1566da2

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

This PR includes changesets to release 15 packages

Name	Type
@workflow/core	Patch
@workflow/builders	Patch
@workflow/cli	Patch
@workflow/docs-typecheck	Patch
@workflow/next	Patch
@workflow/nitro	Patch
@workflow/web-shared	Patch
workflow	Patch
@workflow/astro	Patch
@workflow/nest	Patch
@workflow/rollup	Patch
@workflow/sveltekit	Patch
@workflow/vite	Patch
@workflow/world-testing	Patch
@workflow/nuxt	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]

🧪 E2E Test Results

❌ Some tests failed

Summary

	Passed	Failed	Skipped	Total
✅ ▲ Vercel Production	457	0	38	495
✅ 💻 Local Development	418	0	32	450
✅ 📦 Local Production	418	0	32	450
✅ 🐘 Local Postgres	418	0	32	450
✅ 🪟 Windows	45	0	0	45
❌ 🌍 Community Worlds	31	161	0	192
✅ 📋 Other	123	0	12	135
Total	1910	161	146	2217

❌ Failed Tests

🌍 Community Worlds (161 failed)

mongodb (40 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

redis (40 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

starter (41 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• health check (CLI) - workflow health command reports healthy endpoints
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

turso (40 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

Details by Category

✅ ▲ Vercel Production

App	Passed	Failed	Skipped
✅ astro	41	0	4
✅ example	41	0	4
✅ express	41	0	4
✅ fastify	41	0	4
✅ hono	41	0	4
✅ nextjs-turbopack	44	0	1
✅ nextjs-webpack	44	0	1
✅ nitro	41	0	4
✅ nuxt	41	0	4
✅ sveltekit	41	0	4
✅ vite	41	0	4

✅ 💻 Local Development

App	Passed	Failed	Skipped
✅ astro-stable	41	0	4
✅ express-stable	41	0	4
✅ fastify-stable	41	0	4
✅ hono-stable	41	0	4
✅ nextjs-turbopack-stable	45	0	0
✅ nextjs-webpack-stable	45	0	0
✅ nitro-stable	41	0	4
✅ nuxt-stable	41	0	4
✅ sveltekit-stable	41	0	4
✅ vite-stable	41	0	4

✅ 📦 Local Production

App	Passed	Failed	Skipped
✅ astro-stable	41	0	4
✅ express-stable	41	0	4
✅ fastify-stable	41	0	4
✅ hono-stable	41	0	4
✅ nextjs-turbopack-stable	45	0	0
✅ nextjs-webpack-stable	45	0	0
✅ nitro-stable	41	0	4
✅ nuxt-stable	41	0	4
✅ sveltekit-stable	41	0	4
✅ vite-stable	41	0	4

✅ 🐘 Local Postgres

App	Passed	Failed	Skipped
✅ astro-stable	41	0	4
✅ express-stable	41	0	4
✅ fastify-stable	41	0	4
✅ hono-stable	41	0	4
✅ nextjs-turbopack-stable	45	0	0
✅ nextjs-webpack-stable	45	0	0
✅ nitro-stable	41	0	4
✅ nuxt-stable	41	0	4
✅ sveltekit-stable	41	0	4
✅ vite-stable	41	0	4

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack	45	0	0

❌ 🌍 Community Worlds

App	Passed	Failed	Skipped
✅ mongodb-dev	3	0	0
❌ mongodb	5	40	0
✅ redis-dev	3	0	0
❌ redis	5	40	0
✅ starter-dev	3	0	0
❌ starter	4	41	0
✅ turso-dev	3	0	0
❌ turso	5	40	0

✅ 📋 Other

App	Passed	Failed	Skipped
✅ e2e-local-dev-nest-stable	41	0	4
✅ e2e-local-postgres-nest-stable	41	0	4
✅ e2e-local-prod-nest-stable	41	0	4

---

📋 View full workflow run

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
example-nextjs-workflow-turbopack	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
example-nextjs-workflow-webpack	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
example-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-astro-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-express-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-fastify-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-hono-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-nitro-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-nuxt-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-sveltekit-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-vite-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workflow-docs	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workflow-nest	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am

[TooTallNate]

• Add support for "use step" functions in class instance methods #777: 2 dependent PRs (#876, #899)
• Add discovered serializable classes in all context modes #874
• Ensure class serialization / deserialization only happens in the proper global context #873 👈 (View in Graphite)
• Fix class ID generation when class is bound to a variable #872
• Add discovery for custom classes with workflow serialization #859
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[TooTallNate]

Merge activity

• Feb 3, 7:18 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Feb 3, 7:20 AM UTC: Graphite couldn't merge this pull request because a downstack PR Fix class ID generation when class is bound to a variable #872 failed to merge.
• Feb 3, 7:22 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Feb 3, 7:24 AM UTC: Graphite rebased this pull request as part of a merge.
• Feb 3, 7:24 AM UTC: @TooTallNate merged this pull request with Graphite.

[github-actions]

📊 Benchmark Results

📈 Comparing against baseline from main branch. Green 🟢 = faster, Red 🔺 = slower.

workflow with no steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	0.043s (~)	1.008s (~)	0.965s	10	1.00x
🐘 Postgres	Express	0.231s (+0.5%)	1.029s (+1.3%)	0.798s	10	5.38x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	0.693s (+18.5% 🔺)	1.716s (+10.7% 🔺)	1.023s	10	1.00x

🔍 Observability: Express

workflow with 1 step

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	1.116s (~)	2.008s (~)	0.892s	10	1.00x
🐘 Postgres	Express	2.466s (+9.1% 🔺)	3.014s (~)	0.548s	10	2.21x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.014s (+2.7%)	3.770s (-1.4%)	0.757s	10	1.00x

🔍 Observability: Express

workflow with 10 sequential steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	10.846s (~)	11.015s (~)	0.169s	5	1.00x
🐘 Postgres	Express	20.296s (~)	21.042s (~)	0.746s	5	1.87x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	22.608s (-2.9%)	23.176s (-2.8%)	0.568s	5	1.00x

🔍 Observability: Express

Promise.all with 10 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.173s (~)	6.175s (~)	1.001s	5	1.00x
🐘 Postgres	Express	29.529s (+3.5%)	29.682s (+1.9%)	0.153s	2	5.71x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.212s (-12.8% 🟢)	3.768s (-16.5% 🟢)	0.555s	8	1.00x

🔍 Observability: Express

Promise.all with 25 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.334s (+0.7%)	6.323s (+0.5%)	0.989s	5	1.00x
🐘 Postgres	Express	32.161s (-2.9%)	32.207s (-2.9%)	0.046s	1	6.03x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.060s (-1.6%)	3.684s (-1.0%)	0.625s	9	1.00x

🔍 Observability: Express

Promise.race with 10 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.544s (+3.3%)	6.502s (+2.8%)	0.958s	5	1.00x
🐘 Postgres	Express	32.984s (-5.5% 🟢)	33.206s (-5.7% 🟢)	0.222s	1	5.95x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.035s (-6.0% 🟢)	3.668s (-10.3% 🟢)	0.633s	9	1.00x

🔍 Observability: Express

Promise.race with 25 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.792s (+5.9% 🔺)	6.616s (+2.7%)	0.824s	5	1.00x
🐘 Postgres	Express	35.490s (+8.4% 🔺)	36.066s (+9.1% 🔺)	0.576s	1	6.13x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.021s (-33.6% 🟢)	3.751s (-30.1% 🟢)	0.730s	9	1.00x

🔍 Observability: Express

Stream Benchmarks(includes TTFB metrics)

workflow with stream

💻 Local Development

World	Framework	Workflow Time	TTFB	Slurp	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	0.180s (-3.7%)	0.992s (~)	0.017s (+10.7% 🔺)	1.024s (~)	0.844s	10	1.00x
🐘 Postgres	Express	1.634s (-23.8% 🟢)	2.425s (-16.4% 🟢)	0.000s (+100.0% 🔺)	2.516s (-16.6% 🟢)	0.882s	10	9.07x

▲ Production (Vercel)

World	Framework	Workflow Time	TTFB	Slurp	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	2.789s (-8.6% 🟢)	3.296s (+2.2%)	0.334s (-61.3% 🟢)	4.141s (-11.1% 🟢)	1.352s	10	1.00x

🔍 Observability: Express

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World	🥇 Fastest Framework	Wins
💻 Local	Express	8/8
🐘 Postgres	Express	8/8
▲ Vercel	Express	8/8

Fastest World by Framework

Winner determined by most benchmark wins

Framework	🥇 Fastest World	Wins
Express	💻 Local	4/8

Column Definitions

• Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
• TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
• Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
• Wall Time: Total testbench time (trigger workflow + poll for result)
• Overhead: Testbench overhead (Wall Time - Workflow Time)
• Samples: Number of benchmark iterations run
• vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

• 💻 Local: In-memory filesystem world (local development)
• 🐘 Postgres: PostgreSQL database world (local development)
• ▲ Vercel: Vercel production/preview deployment
• 🌐 Starter: Community world (local development)
• 🌐 Turso: Community world (local development)
• 🌐 MongoDB: Community world (local development)
• 🌐 Redis: Community world (local development)
• 🌐 Jazz: Community world (local development)

---

📋 View full workflow run

[TooTallNate]

Fixed class serialization/deserialization to properly respect VM context boundaries, ensuring workflow code only accesses classes registered in its own global context.

What changed?

• Modified getSerializationClass() to no longer fall back to checking globalThis when a class isn't found in the provided global context
• Updated the serialization tests to properly simulate how classes are registered and accessed in both host and VM contexts
• Added VM-specific class registration in tests to better match production behavior where workflow code runs in isolation

How to test?

• Run the updated serialization tests which now properly simulate the VM boundary
• Verify that class serialization/deserialization works correctly when classes are registered in their respective contexts
• Confirm that classes registered in one context aren't accessible from another context

Why make this change?

This change ensures proper isolation between the host environment and workflow VM contexts, matching production serverless behavior where workflow code runs in isolation. Previously, the code could leak class registrations between contexts, potentially causing unexpected behavior or security issues. This fix maintains proper boundaries between execution contexts.

[changeset-bot]

🦋 Changeset detected

Latest commit: 1566da2

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

This PR includes changesets to release 15 packages

Name	Type
@workflow/core	Patch
@workflow/builders	Patch
@workflow/cli	Patch
@workflow/docs-typecheck	Patch
@workflow/next	Patch
@workflow/nitro	Patch
@workflow/web-shared	Patch
workflow	Patch
@workflow/astro	Patch
@workflow/nest	Patch
@workflow/rollup	Patch
@workflow/sveltekit	Patch
@workflow/vite	Patch
@workflow/world-testing	Patch
@workflow/nuxt	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]

🧪 E2E Test Results

❌ Some tests failed

Summary

	Passed	Failed	Skipped	Total
✅ ▲ Vercel Production	457	0	38	495
✅ 💻 Local Development	418	0	32	450
✅ 📦 Local Production	418	0	32	450
✅ 🐘 Local Postgres	418	0	32	450
✅ 🪟 Windows	45	0	0	45
❌ 🌍 Community Worlds	31	161	0	192
✅ 📋 Other	123	0	12	135
Total	1910	161	146	2217

❌ Failed Tests

🌍 Community Worlds (161 failed)

mongodb (40 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

redis (40 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

starter (41 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• health check (CLI) - workflow health command reports healthy endpoints
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

turso (40 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

Details by Category

✅ ▲ Vercel Production

App	Passed	Failed	Skipped
✅ astro	41	0	4
✅ example	41	0	4
✅ express	41	0	4
✅ fastify	41	0	4
✅ hono	41	0	4
✅ nextjs-turbopack	44	0	1
✅ nextjs-webpack	44	0	1
✅ nitro	41	0	4
✅ nuxt	41	0	4
✅ sveltekit	41	0	4
✅ vite	41	0	4

✅ 💻 Local Development

App	Passed	Failed	Skipped
✅ astro-stable	41	0	4
✅ express-stable	41	0	4
✅ fastify-stable	41	0	4
✅ hono-stable	41	0	4
✅ nextjs-turbopack-stable	45	0	0
✅ nextjs-webpack-stable	45	0	0
✅ nitro-stable	41	0	4
✅ nuxt-stable	41	0	4
✅ sveltekit-stable	41	0	4
✅ vite-stable	41	0	4

✅ 📦 Local Production

App	Passed	Failed	Skipped
✅ astro-stable	41	0	4
✅ express-stable	41	0	4
✅ fastify-stable	41	0	4
✅ hono-stable	41	0	4
✅ nextjs-turbopack-stable	45	0	0
✅ nextjs-webpack-stable	45	0	0
✅ nitro-stable	41	0	4
✅ nuxt-stable	41	0	4
✅ sveltekit-stable	41	0	4
✅ vite-stable	41	0	4

✅ 🐘 Local Postgres

App	Passed	Failed	Skipped
✅ astro-stable	41	0	4
✅ express-stable	41	0	4
✅ fastify-stable	41	0	4
✅ hono-stable	41	0	4
✅ nextjs-turbopack-stable	45	0	0
✅ nextjs-webpack-stable	45	0	0
✅ nitro-stable	41	0	4
✅ nuxt-stable	41	0	4
✅ sveltekit-stable	41	0	4
✅ vite-stable	41	0	4

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack	45	0	0

❌ 🌍 Community Worlds

App	Passed	Failed	Skipped
✅ mongodb-dev	3	0	0
❌ mongodb	5	40	0
✅ redis-dev	3	0	0
❌ redis	5	40	0
✅ starter-dev	3	0	0
❌ starter	4	41	0
✅ turso-dev	3	0	0
❌ turso	5	40	0

✅ 📋 Other

App	Passed	Failed	Skipped
✅ e2e-local-dev-nest-stable	41	0	4
✅ e2e-local-postgres-nest-stable	41	0	4
✅ e2e-local-prod-nest-stable	41	0	4

---

📋 View full workflow run

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
example-nextjs-workflow-turbopack	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
example-nextjs-workflow-webpack	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
example-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-astro-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-express-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-fastify-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-hono-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-nitro-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-nuxt-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-sveltekit-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-vite-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workflow-docs	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workflow-nest	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am

[TooTallNate]

• Add support for "use step" functions in class instance methods #777: 2 dependent PRs (#876, #899)
• Add discovered serializable classes in all context modes #874
• Ensure class serialization / deserialization only happens in the proper global context #873 👈 (View in Graphite)
• Fix class ID generation when class is bound to a variable #872
• Add discovery for custom classes with workflow serialization #859
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[TooTallNate]

Merge activity

• Feb 3, 7:18 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Feb 3, 7:20 AM UTC: Graphite couldn't merge this pull request because a downstack PR Fix class ID generation when class is bound to a variable #872 failed to merge.
• Feb 3, 7:22 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Feb 3, 7:24 AM UTC: Graphite rebased this pull request as part of a merge.
• Feb 3, 7:24 AM UTC: @TooTallNate merged this pull request with Graphite.

[github-actions]

📊 Benchmark Results

📈 Comparing against baseline from main branch. Green 🟢 = faster, Red 🔺 = slower.

workflow with no steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	0.043s (~)	1.008s (~)	0.965s	10	1.00x
🐘 Postgres	Express	0.231s (+0.5%)	1.029s (+1.3%)	0.798s	10	5.38x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	0.693s (+18.5% 🔺)	1.716s (+10.7% 🔺)	1.023s	10	1.00x

🔍 Observability: Express

workflow with 1 step

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	1.116s (~)	2.008s (~)	0.892s	10	1.00x
🐘 Postgres	Express	2.466s (+9.1% 🔺)	3.014s (~)	0.548s	10	2.21x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.014s (+2.7%)	3.770s (-1.4%)	0.757s	10	1.00x

🔍 Observability: Express

workflow with 10 sequential steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	10.846s (~)	11.015s (~)	0.169s	5	1.00x
🐘 Postgres	Express	20.296s (~)	21.042s (~)	0.746s	5	1.87x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	22.608s (-2.9%)	23.176s (-2.8%)	0.568s	5	1.00x

🔍 Observability: Express

Promise.all with 10 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.173s (~)	6.175s (~)	1.001s	5	1.00x
🐘 Postgres	Express	29.529s (+3.5%)	29.682s (+1.9%)	0.153s	2	5.71x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.212s (-12.8% 🟢)	3.768s (-16.5% 🟢)	0.555s	8	1.00x

🔍 Observability: Express

Promise.all with 25 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.334s (+0.7%)	6.323s (+0.5%)	0.989s	5	1.00x
🐘 Postgres	Express	32.161s (-2.9%)	32.207s (-2.9%)	0.046s	1	6.03x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.060s (-1.6%)	3.684s (-1.0%)	0.625s	9	1.00x

🔍 Observability: Express

Promise.race with 10 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.544s (+3.3%)	6.502s (+2.8%)	0.958s	5	1.00x
🐘 Postgres	Express	32.984s (-5.5% 🟢)	33.206s (-5.7% 🟢)	0.222s	1	5.95x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.035s (-6.0% 🟢)	3.668s (-10.3% 🟢)	0.633s	9	1.00x

🔍 Observability: Express

Promise.race with 25 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.792s (+5.9% 🔺)	6.616s (+2.7%)	0.824s	5	1.00x
🐘 Postgres	Express	35.490s (+8.4% 🔺)	36.066s (+9.1% 🔺)	0.576s	1	6.13x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.021s (-33.6% 🟢)	3.751s (-30.1% 🟢)	0.730s	9	1.00x

🔍 Observability: Express

Stream Benchmarks(includes TTFB metrics)

workflow with stream

💻 Local Development

World	Framework	Workflow Time	TTFB	Slurp	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	0.180s (-3.7%)	0.992s (~)	0.017s (+10.7% 🔺)	1.024s (~)	0.844s	10	1.00x
🐘 Postgres	Express	1.634s (-23.8% 🟢)	2.425s (-16.4% 🟢)	0.000s (+100.0% 🔺)	2.516s (-16.6% 🟢)	0.882s	10	9.07x

▲ Production (Vercel)

World	Framework	Workflow Time	TTFB	Slurp	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	2.789s (-8.6% 🟢)	3.296s (+2.2%)	0.334s (-61.3% 🟢)	4.141s (-11.1% 🟢)	1.352s	10	1.00x

🔍 Observability: Express

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World	🥇 Fastest Framework	Wins
💻 Local	Express	8/8
🐘 Postgres	Express	8/8
▲ Vercel	Express	8/8

Fastest World by Framework

Winner determined by most benchmark wins

Framework	🥇 Fastest World	Wins
Express	💻 Local	4/8

Column Definitions

• Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
• TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
• Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
• Wall Time: Total testbench time (trigger workflow + poll for result)
• Overhead: Testbench overhead (Wall Time - Workflow Time)
• Samples: Number of benchmark iterations run
• vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

• 💻 Local: In-memory filesystem world (local development)
• 🐘 Postgres: PostgreSQL database world (local development)
• ▲ Vercel: Vercel production/preview deployment
• 🌐 Starter: Community world (local development)
• 🌐 Turso: Community world (local development)
• 🌐 MongoDB: Community world (local development)
• 🌐 Redis: Community world (local development)
• 🌐 Jazz: Community world (local development)

---

📋 View full workflow run

[TooTallNate]

Fixed class serialization/deserialization to properly respect VM context boundaries, ensuring workflow code only accesses classes registered in its own global context.

What changed?

• Modified getSerializationClass() to no longer fall back to checking globalThis when a class isn't found in the provided global context
• Updated the serialization tests to properly simulate how classes are registered and accessed in both host and VM contexts
• Added VM-specific class registration in tests to better match production behavior where workflow code runs in isolation

How to test?

• Run the updated serialization tests which now properly simulate the VM boundary
• Verify that class serialization/deserialization works correctly when classes are registered in their respective contexts
• Confirm that classes registered in one context aren't accessible from another context

Why make this change?

This change ensures proper isolation between the host environment and workflow VM contexts, matching production serverless behavior where workflow code runs in isolation. Previously, the code could leak class registrations between contexts, potentially causing unexpected behavior or security issues. This fix maintains proper boundaries between execution contexts.

[changeset-bot]

🦋 Changeset detected

Latest commit: 1566da2

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

This PR includes changesets to release 15 packages

Name	Type
@workflow/core	Patch
@workflow/builders	Patch
@workflow/cli	Patch
@workflow/docs-typecheck	Patch
@workflow/next	Patch
@workflow/nitro	Patch
@workflow/web-shared	Patch
workflow	Patch
@workflow/astro	Patch
@workflow/nest	Patch
@workflow/rollup	Patch
@workflow/sveltekit	Patch
@workflow/vite	Patch
@workflow/world-testing	Patch
@workflow/nuxt	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]

🧪 E2E Test Results

❌ Some tests failed

Summary

	Passed	Failed	Skipped	Total
✅ ▲ Vercel Production	457	0	38	495
✅ 💻 Local Development	418	0	32	450
✅ 📦 Local Production	418	0	32	450
✅ 🐘 Local Postgres	418	0	32	450
✅ 🪟 Windows	45	0	0	45
❌ 🌍 Community Worlds	31	161	0	192
✅ 📋 Other	123	0	12	135
Total	1910	161	146	2217

❌ Failed Tests

🌍 Community Worlds (161 failed)

mongodb (40 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

redis (40 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

starter (41 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• health check (CLI) - workflow health command reports healthy endpoints
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

turso (40 failed):

• addTenWorkflow
• addTenWorkflow
• should work with react rendering in step
• promiseAllWorkflow
• promiseRaceWorkflow
• promiseAnyWorkflow
• readableStreamWorkflow
• hookWorkflow
• webhookWorkflow
• sleepingWorkflow
• nullByteWorkflow
• workflowAndStepMetadataWorkflow
• outputStreamWorkflow
• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• fetchWorkflow
• promiseRaceStressTestWorkflow
• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling retry behavior regular Error retries until success
• error handling retry behavior FatalError fails immediately without retries
• error handling retry behavior RetryableError respects custom retryAfter delay
• error handling retry behavior maxRetries=0 disables retries
• error handling catchability FatalError can be caught and detected with FatalError.is()
• hookCleanupTestWorkflow - hook token reuse after workflow completion
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
• closureVariableWorkflow - nested step functions with closure variables
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
• pathsAliasWorkflow - TypeScript path aliases resolve correctly
• Calculator.calculate - static workflow method using static step methods from another class
• AllInOneService.processNumber - static workflow method using sibling static step methods
• ChainableService.processWithThis - static step methods using this to reference the class
• thisSerializationWorkflow - step function invoked with .call() and .apply()
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
• pages router addTenWorkflow via pages router
• pages router promiseAllWorkflow via pages router
• pages router sleepingWorkflow via pages router

Details by Category

✅ ▲ Vercel Production

App	Passed	Failed	Skipped
✅ astro	41	0	4
✅ example	41	0	4
✅ express	41	0	4
✅ fastify	41	0	4
✅ hono	41	0	4
✅ nextjs-turbopack	44	0	1
✅ nextjs-webpack	44	0	1
✅ nitro	41	0	4
✅ nuxt	41	0	4
✅ sveltekit	41	0	4
✅ vite	41	0	4

✅ 💻 Local Development

App	Passed	Failed	Skipped
✅ astro-stable	41	0	4
✅ express-stable	41	0	4
✅ fastify-stable	41	0	4
✅ hono-stable	41	0	4
✅ nextjs-turbopack-stable	45	0	0
✅ nextjs-webpack-stable	45	0	0
✅ nitro-stable	41	0	4
✅ nuxt-stable	41	0	4
✅ sveltekit-stable	41	0	4
✅ vite-stable	41	0	4

✅ 📦 Local Production

App	Passed	Failed	Skipped
✅ astro-stable	41	0	4
✅ express-stable	41	0	4
✅ fastify-stable	41	0	4
✅ hono-stable	41	0	4
✅ nextjs-turbopack-stable	45	0	0
✅ nextjs-webpack-stable	45	0	0
✅ nitro-stable	41	0	4
✅ nuxt-stable	41	0	4
✅ sveltekit-stable	41	0	4
✅ vite-stable	41	0	4

✅ 🐘 Local Postgres

App	Passed	Failed	Skipped
✅ astro-stable	41	0	4
✅ express-stable	41	0	4
✅ fastify-stable	41	0	4
✅ hono-stable	41	0	4
✅ nextjs-turbopack-stable	45	0	0
✅ nextjs-webpack-stable	45	0	0
✅ nitro-stable	41	0	4
✅ nuxt-stable	41	0	4
✅ sveltekit-stable	41	0	4
✅ vite-stable	41	0	4

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack	45	0	0

❌ 🌍 Community Worlds

App	Passed	Failed	Skipped
✅ mongodb-dev	3	0	0
❌ mongodb	5	40	0
✅ redis-dev	3	0	0
❌ redis	5	40	0
✅ starter-dev	3	0	0
❌ starter	4	41	0
✅ turso-dev	3	0	0
❌ turso	5	40	0

✅ 📋 Other

App	Passed	Failed	Skipped
✅ e2e-local-dev-nest-stable	41	0	4
✅ e2e-local-postgres-nest-stable	41	0	4
✅ e2e-local-prod-nest-stable	41	0	4

---

📋 View full workflow run

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
example-nextjs-workflow-turbopack	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
example-nextjs-workflow-webpack	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
example-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-astro-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-express-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-fastify-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-hono-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-nitro-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-nuxt-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-sveltekit-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workbench-vite-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workflow-docs	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am
workflow-nest	Ready	Preview, Comment, Open in v0	Feb 3, 2026 7:26am

[TooTallNate]

• Add support for "use step" functions in class instance methods #777: 2 dependent PRs (#876, #899)
• Add discovered serializable classes in all context modes #874
• Ensure class serialization / deserialization only happens in the proper global context #873 👈 (View in Graphite)
• Fix class ID generation when class is bound to a variable #872
• Add discovery for custom classes with workflow serialization #859
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[TooTallNate]

Merge activity

• Feb 3, 7:18 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Feb 3, 7:20 AM UTC: Graphite couldn't merge this pull request because a downstack PR Fix class ID generation when class is bound to a variable #872 failed to merge.
• Feb 3, 7:22 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Feb 3, 7:24 AM UTC: Graphite rebased this pull request as part of a merge.
• Feb 3, 7:24 AM UTC: @TooTallNate merged this pull request with Graphite.

[github-actions]

📊 Benchmark Results

📈 Comparing against baseline from main branch. Green 🟢 = faster, Red 🔺 = slower.

workflow with no steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	0.043s (~)	1.008s (~)	0.965s	10	1.00x
🐘 Postgres	Express	0.231s (+0.5%)	1.029s (+1.3%)	0.798s	10	5.38x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	0.693s (+18.5% 🔺)	1.716s (+10.7% 🔺)	1.023s	10	1.00x

🔍 Observability: Express

workflow with 1 step

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	1.116s (~)	2.008s (~)	0.892s	10	1.00x
🐘 Postgres	Express	2.466s (+9.1% 🔺)	3.014s (~)	0.548s	10	2.21x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.014s (+2.7%)	3.770s (-1.4%)	0.757s	10	1.00x

🔍 Observability: Express

workflow with 10 sequential steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	10.846s (~)	11.015s (~)	0.169s	5	1.00x
🐘 Postgres	Express	20.296s (~)	21.042s (~)	0.746s	5	1.87x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	22.608s (-2.9%)	23.176s (-2.8%)	0.568s	5	1.00x

🔍 Observability: Express

Promise.all with 10 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.173s (~)	6.175s (~)	1.001s	5	1.00x
🐘 Postgres	Express	29.529s (+3.5%)	29.682s (+1.9%)	0.153s	2	5.71x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.212s (-12.8% 🟢)	3.768s (-16.5% 🟢)	0.555s	8	1.00x

🔍 Observability: Express

Promise.all with 25 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.334s (+0.7%)	6.323s (+0.5%)	0.989s	5	1.00x
🐘 Postgres	Express	32.161s (-2.9%)	32.207s (-2.9%)	0.046s	1	6.03x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.060s (-1.6%)	3.684s (-1.0%)	0.625s	9	1.00x

🔍 Observability: Express

Promise.race with 10 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.544s (+3.3%)	6.502s (+2.8%)	0.958s	5	1.00x
🐘 Postgres	Express	32.984s (-5.5% 🟢)	33.206s (-5.7% 🟢)	0.222s	1	5.95x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.035s (-6.0% 🟢)	3.668s (-10.3% 🟢)	0.633s	9	1.00x

🔍 Observability: Express

Promise.race with 25 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	5.792s (+5.9% 🔺)	6.616s (+2.7%)	0.824s	5	1.00x
🐘 Postgres	Express	35.490s (+8.4% 🔺)	36.066s (+9.1% 🔺)	0.576s	1	6.13x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	3.021s (-33.6% 🟢)	3.751s (-30.1% 🟢)	0.730s	9	1.00x

🔍 Observability: Express

Stream Benchmarks(includes TTFB metrics)

workflow with stream

💻 Local Development

World	Framework	Workflow Time	TTFB	Slurp	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Express	0.180s (-3.7%)	0.992s (~)	0.017s (+10.7% 🔺)	1.024s (~)	0.844s	10	1.00x
🐘 Postgres	Express	1.634s (-23.8% 🟢)	2.425s (-16.4% 🟢)	0.000s (+100.0% 🔺)	2.516s (-16.6% 🟢)	0.882s	10	9.07x

▲ Production (Vercel)

World	Framework	Workflow Time	TTFB	Slurp	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	2.789s (-8.6% 🟢)	3.296s (+2.2%)	0.334s (-61.3% 🟢)	4.141s (-11.1% 🟢)	1.352s	10	1.00x

🔍 Observability: Express

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World	🥇 Fastest Framework	Wins
💻 Local	Express	8/8
🐘 Postgres	Express	8/8
▲ Vercel	Express	8/8

Fastest World by Framework

Winner determined by most benchmark wins

Framework	🥇 Fastest World	Wins
Express	💻 Local	4/8

Column Definitions

• Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
• TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
• Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
• Wall Time: Total testbench time (trigger workflow + poll for result)
• Overhead: Testbench overhead (Wall Time - Workflow Time)
• Samples: Number of benchmark iterations run
• vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

• 💻 Local: In-memory filesystem world (local development)
• 🐘 Postgres: PostgreSQL database world (local development)
• ▲ Vercel: Vercel production/preview deployment
• 🌐 Starter: Community world (local development)
• 🌐 Turso: Community world (local development)
• 🌐 MongoDB: Community world (local development)
• 🌐 Redis: Community world (local development)
• 🌐 Jazz: Community world (local development)

---

📋 View full workflow run