Skip to content

Expose workflow manifest via HTTP when WORKFLOW_PUBLIC_MANIFEST=1#963

Merged
TooTallNate merged 2 commits intomainfrom
02-06-workflow_public_manifest
Feb 6, 2026
Merged

Expose workflow manifest via HTTP when WORKFLOW_PUBLIC_MANIFEST=1#963
TooTallNate merged 2 commits intomainfrom
02-06-workflow_public_manifest

Conversation

@TooTallNate
Copy link
Copy Markdown
Member

@TooTallNate TooTallNate commented Feb 6, 2026

Summary

When WORKFLOW_PUBLIC_MANIFEST=1 is set, each framework builder exposes the workflow manifest at /.well-known/workflow/v1/manifest.json via the most appropriate mechanism for the framework:

  • Next.js: Copies manifest to public/.well-known/workflow/v1/manifest.json (served as a static file)
  • SvelteKit: Copies manifest to static/.well-known/workflow/v1/manifest.json (served as a static file)
  • Vercel Build Output API (example workbench): Copies manifest to .vercel/output/static/.well-known/workflow/v1/manifest.json (served as a static file)
  • Nitro (vite, hono, express, fastify, nuxt, nitro-v2, nitro-v3): Registers a virtual handler that reads and serves the manifest JSON
  • Astro: Generates a manifest.json.js page route that returns the manifest JSON
  • NestJS: Adds a @Get('manifest.json') endpoint on the WorkflowController (gated by the env var at runtime)

Other changes

  • BaseBuilder.createManifest() now returns the manifest JSON string so framework builders can use it
  • Added shouldExposePublicManifest getter to BaseBuilder
  • Fixed Astro LocalBuilder which was missing the createManifest() call that all other framework builders have
  • Removed unused public/ directory and static file copy from the example workbench build script
  • Added WORKFLOW_PUBLIC_MANIFEST to turbo.json build task env so Vercel builds can access it
  • Added generated manifest paths to .gitignore

Copilot AI review requested due to automatic review settings February 6, 2026 09:14
@vercel
Copy link
Copy Markdown
Contributor

vercel bot commented Feb 6, 2026

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Feb 6, 2026

📊 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 🥇 Next.js (Turbopack) 0.038s (-11.8% 🟢) 1.016s (~) 0.978s 10 1.00x
💻 Local Express 0.043s (-2.0%) 1.007s (~) 0.964s 10 1.13x
💻 Local Nitro 0.043s (-6.5% 🟢) 1.008s (~) 0.964s 10 1.14x
🐘 Postgres Next.js (Turbopack) 0.127s (-35.8% 🟢) 1.023s (~) 0.897s 10 3.33x
🐘 Postgres Express 0.232s (-41.8% 🟢) 1.015s (~) 0.783s 10 6.09x
🐘 Postgres Nitro 0.334s (-16.7% 🟢) 1.015s (-2.6%) 0.682s 10 8.75x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 0.592s (+3.5%) 1.705s (+12.2% 🔺) 1.114s 10 1.00x
▲ Vercel Express 0.604s (-15.7% 🟢) 1.462s (-9.1% 🟢) 0.857s 10 1.02x
▲ Vercel Next.js (Turbopack) 0.727s (-9.6% 🟢) 1.507s (-14.6% 🟢) 0.780s 10 1.23x

🔍 Observability: Nitro | Express | Next.js (Turbopack)

workflow with 1 step

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 1.100s (~) 2.012s (~) 0.912s 10 1.00x
💻 Local Nitro 1.115s (~) 2.006s (~) 0.892s 10 1.01x
💻 Local Express 1.116s (~) 2.006s (~) 0.890s 10 1.02x
🐘 Postgres Express 2.182s (-6.9% 🟢) 3.013s (~) 0.831s 10 1.98x
🐘 Postgres Nitro 2.369s (+3.2%) 3.014s (~) 0.646s 10 2.15x
🐘 Postgres Next.js (Turbopack) 2.415s (+31.4% 🔺) 3.019s (+42.6% 🔺) 0.604s 10 2.20x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.716s (+4.4%) 3.835s (+6.4% 🔺) 1.119s 10 1.00x
▲ Vercel Next.js (Turbopack) 2.755s (+6.5% 🔺) 3.651s (-1.4%) 0.896s 10 1.01x
▲ Vercel Express 2.853s (+11.1% 🔺) 3.738s (+5.2% 🔺) 0.885s 10 1.05x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

workflow with 10 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 10.726s (~) 11.020s (~) 0.294s 3 1.00x
💻 Local Express 10.831s (~) 11.015s (~) 0.183s 3 1.01x
💻 Local Nitro 10.844s (~) 11.016s (~) 0.171s 3 1.01x
🐘 Postgres Nitro 20.250s (~) 21.042s (~) 0.791s 2 1.89x
🐘 Postgres Next.js (Turbopack) 20.304s (+32.3% 🔺) 21.039s (+31.2% 🔺) 0.735s 2 1.89x
🐘 Postgres Express 20.476s (+1.0%) 21.026s (~) 0.550s 2 1.91x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 20.846s (-1.8%) 21.742s (-0.5%) 0.895s 2 1.00x
▲ Vercel Nitro 21.228s (-3.2%) 22.051s (-2.3%) 0.823s 2 1.02x
▲ Vercel Express 21.992s (+1.9%) 22.936s (+2.9%) 0.944s 2 1.05x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

workflow with 25 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 27.240s (~) 28.022s (~) 0.782s 3 1.00x
💻 Local Nitro 27.471s (~) 28.024s (~) 0.553s 3 1.01x
💻 Local Express 27.472s (~) 28.024s (~) 0.552s 3 1.01x
🐘 Postgres Next.js (Turbopack) 38.215s (+1.2%) 39.082s (+2.7%) 0.866s 2 1.40x
🐘 Postgres Express 43.157s (-14.1% 🟢) 43.554s (-14.7% 🟢) 0.397s 2 1.58x
🐘 Postgres Nitro 50.132s (+30.9% 🔺) 51.079s (+30.8% 🔺) 0.948s 2 1.84x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 52.502s (-4.8%) 52.948s (-4.6%) 0.445s 2 1.00x
▲ Vercel Next.js (Turbopack) 52.591s (-1.5%) 53.385s (-1.6%) 0.794s 2 1.00x
▲ Vercel Express 53.499s (-0.6%) 54.604s (~) 1.105s 2 1.02x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

workflow with 50 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 56.742s (~) 57.046s (~) 0.304s 2 1.00x
💻 Local Express 57.087s (~) 58.040s (~) 0.952s 2 1.01x
💻 Local Nitro 57.196s (~) 58.042s (~) 0.846s 2 1.01x
🐘 Postgres Express 75.214s (-21.0% 🟢) 76.099s (-20.8% 🟢) 0.885s 2 1.33x
🐘 Postgres Next.js (Turbopack) 77.851s (-1.9%) 78.614s (-1.9%) 0.763s 2 1.37x
🐘 Postgres Nitro 100.440s (+33.2% 🔺) 101.142s (+32.9% 🔺) 0.702s 1 1.77x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 110.869s (-4.6%) 111.884s (-4.3%) 1.015s 1 1.00x
▲ Vercel Next.js (Turbopack) 111.535s (-1.3%) 112.704s (-1.2%) 1.169s 1 1.01x
▲ Vercel Express 113.864s (+4.8%) 114.497s (+5.0% 🔺) 0.633s 1 1.03x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

Promise.all with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 1.389s (+0.9%) 2.011s (~) 0.622s 15 1.00x
💻 Local Nitro 1.404s (-0.8%) 2.006s (~) 0.602s 15 1.01x
💻 Local Express 1.415s (~) 2.007s (~) 0.592s 15 1.02x
🐘 Postgres Express 1.933s (-10.9% 🟢) 2.153s (-21.6% 🟢) 0.220s 14 1.39x
🐘 Postgres Next.js (Turbopack) 2.086s (+19.5% 🔺) 2.602s (+16.5% 🔺) 0.515s 12 1.50x
🐘 Postgres Nitro 2.514s (+7.3% 🔺) 3.013s (+10.0% 🔺) 0.499s 10 1.81x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.819s (-9.2% 🟢) 3.784s (-6.1% 🟢) 0.965s 8 1.00x
▲ Vercel Next.js (Turbopack) 2.855s (+4.3%) 3.756s (-2.8%) 0.902s 8 1.01x
▲ Vercel Nitro 2.931s (-7.2% 🟢) 4.027s (-2.9%) 1.096s 8 1.04x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

Promise.all with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Express 2.542s (-1.0%) 3.014s (~) 0.472s 10 1.00x
💻 Local Next.js (Turbopack) 2.566s (+1.6%) 3.034s (-1.1%) 0.469s 10 1.01x
💻 Local Nitro 2.583s (~) 3.022s (~) 0.439s 10 1.02x
🐘 Postgres Nitro 7.997s (-17.2% 🟢) 8.320s (-17.2% 🟢) 0.324s 4 3.15x
🐘 Postgres Express 9.867s (+0.5%) 10.352s (+2.7%) 0.485s 3 3.88x
🐘 Postgres Next.js (Turbopack) 11.105s (+1.3%) 11.714s (~) 0.609s 3 4.37x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 3.337s (+7.2% 🔺) 4.129s (+5.6% 🔺) 0.792s 8 1.00x
▲ Vercel Nitro 3.421s (+4.3%) 4.179s (+4.1%) 0.758s 8 1.03x
▲ Vercel Next.js (Turbopack) 3.555s (+21.1% 🔺) 4.827s (+23.4% 🔺) 1.271s 8 1.07x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Promise.all with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Express 7.307s (~) 8.292s (+2.4%) 0.985s 4 1.00x
💻 Local Nitro 7.341s (+2.0%) 8.343s (+7.0% 🔺) 1.002s 4 1.00x
💻 Local Next.js (Turbopack) 7.449s (+7.9% 🔺) 8.480s (+10.4% 🔺) 1.032s 4 1.02x
🐘 Postgres Nitro 45.477s (-0.6%) 46.191s (~) 0.714s 1 6.22x
🐘 Postgres Express 47.827s (-3.8%) 48.180s (-3.9%) 0.353s 1 6.55x
🐘 Postgres Next.js (Turbopack) 56.057s (+7.5% 🔺) 56.129s (+5.6% 🔺) 0.072s 1 7.67x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 3.614s (+6.2% 🔺) 4.755s (+10.7% 🔺) 1.141s 7 1.00x
▲ Vercel Next.js (Turbopack) 3.854s (+16.7% 🔺) 4.730s (+12.8% 🔺) 0.876s 7 1.07x
▲ Vercel Nitro 4.401s (+12.0% 🔺) 5.281s (+12.4% 🔺) 0.880s 6 1.22x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

Promise.race with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Express 1.434s (-0.7%) 2.006s (~) 0.573s 15 1.00x
💻 Local Nitro 1.440s (+0.7%) 2.007s (~) 0.566s 15 1.00x
💻 Local Next.js (Turbopack) 1.443s (+2.5%) 2.011s (~) 0.568s 15 1.01x
🐘 Postgres Express 1.900s (-13.4% 🟢) 2.011s (-22.6% 🟢) 0.110s 15 1.33x
🐘 Postgres Nitro 2.178s (+3.6%) 2.749s (+9.4% 🔺) 0.572s 11 1.52x
🐘 Postgres Next.js (Turbopack) 2.359s (+5.1% 🔺) 2.931s (+6.5% 🔺) 0.572s 11 1.65x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.660s (-9.5% 🟢) 3.663s (-6.5% 🟢) 1.003s 9 1.00x
▲ Vercel Nitro 2.674s (+4.5%) 3.919s (+11.0% 🔺) 1.246s 8 1.00x
▲ Vercel Next.js (Turbopack) 2.732s (+3.8%) 3.800s (+1.8%) 1.068s 8 1.03x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Promise.race with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Nitro 2.627s (-2.2%) 3.010s (~) 0.383s 10 1.00x
💻 Local Express 2.658s (+1.4%) 3.013s (~) 0.355s 10 1.01x
💻 Local Next.js (Turbopack) 2.713s (-2.8%) 3.014s (-9.3% 🟢) 0.301s 10 1.03x
🐘 Postgres Express 10.677s (-9.5% 🟢) 11.353s (-5.7% 🟢) 0.676s 3 4.06x
🐘 Postgres Nitro 11.782s (-1.1%) 12.077s (-2.4%) 0.295s 3 4.49x
🐘 Postgres Next.js (Turbopack) 14.077s (+4.8%) 14.364s (+4.7%) 0.287s 3 5.36x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.802s (~) 3.697s (-0.6%) 0.894s 9 1.00x
▲ Vercel Nitro 2.952s (+2.5%) 3.865s (-0.8%) 0.913s 8 1.05x
▲ Vercel Next.js (Turbopack) 3.443s (+20.3% 🔺) 4.418s (+14.2% 🔺) 0.976s 7 1.23x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Promise.race with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Express 7.811s (+4.4%) 8.753s (+3.2%) 0.942s 4 1.00x
💻 Local Next.js (Turbopack) 7.826s (-4.8%) 8.769s (-0.9%) 0.943s 4 1.00x
💻 Local Nitro 7.885s (+1.6%) 8.805s (+1.2%) 0.920s 4 1.01x
🐘 Postgres Express 48.346s (-7.5% 🟢) 49.165s (-7.5% 🟢) 0.819s 1 6.19x
🐘 Postgres Nitro 51.044s (-7.2% 🟢) 51.159s (-7.2% 🟢) 0.115s 1 6.54x
🐘 Postgres Next.js (Turbopack) 57.719s (+6.9% 🔺) 58.146s (+7.4% 🔺) 0.427s 1 7.39x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 3.333s (+4.7%) 4.227s (+12.7% 🔺) 0.895s 8 1.00x
▲ Vercel Next.js (Turbopack) 3.715s (+9.6% 🔺) 4.294s (+5.7% 🔺) 0.580s 7 1.11x
▲ Vercel Express 4.059s (+26.3% 🔺) 4.581s (+15.7% 🔺) 0.523s 7 1.22x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

Stream Benchmarks (includes TTFB metrics)
workflow with stream

💻 Local Development

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 0.148s (+4.5%) 1.003s (~) 0.015s (-24.6% 🟢) 1.026s (~) 0.878s 10 1.00x
💻 Local Nitro 0.178s (-2.8%) 0.993s (~) 0.014s (-1.4%) 1.021s (~) 0.842s 10 1.20x
💻 Local Express 0.181s (-1.8%) 0.992s (~) 0.014s (+1.5%) 1.020s (~) 0.840s 10 1.22x
🐘 Postgres Next.js (Turbopack) 1.321s (+25.2% 🔺) 1.777s (+38.8% 🔺) 0.000s (NaN%) 2.017s (+32.9% 🔺) 0.696s 10 8.92x
🐘 Postgres Express 1.414s (+6.3% 🔺) 1.656s (-3.2%) 0.000s (+Infinity% 🔺) 2.014s (~) 0.600s 10 9.55x
🐘 Postgres Nitro 2.141s (+91.8% 🔺) 2.904s (+48.0% 🔺) 0.000s (NaN%) 3.017s (+49.8% 🔺) 0.876s 10 14.45x

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 2.785s (+5.6% 🔺) 3.296s (+2.6%) 0.118s (-40.0% 🟢) 3.904s (-0.5%) 1.119s 10 1.00x
▲ Vercel Nitro 2.803s (+3.6%) 3.292s (+3.9%) 0.199s (-31.6% 🟢) 4.022s (+1.9%) 1.219s 10 1.01x
▲ Vercel Express 2.903s (+13.8% 🔺) 3.219s (+3.6%) 0.178s (-30.5% 🟢) 3.892s (+3.3%) 0.989s 10 1.04x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World 🥇 Fastest Framework Wins
💻 Local Next.js (Turbopack) 7/12
🐘 Postgres Express 6/12
▲ Vercel Nitro 5/12
Fastest World by Framework

Winner determined by most benchmark wins

Framework 🥇 Fastest World Wins
Express 💻 Local 10/12
Next.js (Turbopack) 💻 Local 10/12
Nitro 💻 Local 10/12
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

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Feb 6, 2026

🧪 E2E Test Results

Some tests failed

Summary

Passed Failed Skipped Total
✅ ▲ Vercel Production 479 0 38 517
✅ 💻 Local Development 438 0 32 470
✅ 📦 Local Production 438 0 32 470
✅ 🐘 Local Postgres 438 0 32 470
✅ 🪟 Windows 47 0 0 47
❌ 🌍 Community Worlds 31 169 0 200
✅ 📋 Other 129 0 12 141
Total 2000 169 146 2315

❌ Failed Tests

🌍 Community Worlds (169 failed)

mongodb (42 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
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

redis (42 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
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

starter (43 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
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

turso (42 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
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • 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 43 0 4
✅ example 43 0 4
✅ express 43 0 4
✅ fastify 43 0 4
✅ hono 43 0 4
✅ nextjs-turbopack 46 0 1
✅ nextjs-webpack 46 0 1
✅ nitro 43 0 4
✅ nuxt 43 0 4
✅ sveltekit 43 0 4
✅ vite 43 0 4
✅ 💻 Local Development
App Passed Failed Skipped
✅ astro-stable 43 0 4
✅ express-stable 43 0 4
✅ fastify-stable 43 0 4
✅ hono-stable 43 0 4
✅ nextjs-turbopack-stable 47 0 0
✅ nextjs-webpack-stable 47 0 0
✅ nitro-stable 43 0 4
✅ nuxt-stable 43 0 4
✅ sveltekit-stable 43 0 4
✅ vite-stable 43 0 4
✅ 📦 Local Production
App Passed Failed Skipped
✅ astro-stable 43 0 4
✅ express-stable 43 0 4
✅ fastify-stable 43 0 4
✅ hono-stable 43 0 4
✅ nextjs-turbopack-stable 47 0 0
✅ nextjs-webpack-stable 47 0 0
✅ nitro-stable 43 0 4
✅ nuxt-stable 43 0 4
✅ sveltekit-stable 43 0 4
✅ vite-stable 43 0 4
✅ 🐘 Local Postgres
App Passed Failed Skipped
✅ astro-stable 43 0 4
✅ express-stable 43 0 4
✅ fastify-stable 43 0 4
✅ hono-stable 43 0 4
✅ nextjs-turbopack-stable 47 0 0
✅ nextjs-webpack-stable 47 0 0
✅ nitro-stable 43 0 4
✅ nuxt-stable 43 0 4
✅ sveltekit-stable 43 0 4
✅ vite-stable 43 0 4
✅ 🪟 Windows
App Passed Failed Skipped
✅ nextjs-turbopack 47 0 0
❌ 🌍 Community Worlds
App Passed Failed Skipped
✅ mongodb-dev 3 0 0
❌ mongodb 5 42 0
✅ redis-dev 3 0 0
❌ redis 5 42 0
✅ starter-dev 3 0 0
❌ starter 4 43 0
✅ turso-dev 3 0 0
❌ turso 5 42 0
✅ 📋 Other
App Passed Failed Skipped
✅ e2e-local-dev-nest-stable 43 0 4
✅ e2e-local-postgres-nest-stable 43 0 4
✅ e2e-local-prod-nest-stable 43 0 4

📋 View full workflow run

@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Feb 6, 2026

🦋 Changeset detected

Latest commit: 97e1d18

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

This PR includes changesets to release 15 packages
Name Type
@workflow/sveltekit Patch
@workflow/builders Patch
@workflow/astro Patch
@workflow/nitro Patch
@workflow/nest Patch
@workflow/next Patch
workflow Patch
@workflow/cli Patch
@workflow/rollup Patch
@workflow/vite Patch
@workflow/nuxt Patch
@workflow/docs-typecheck Patch
@workflow/world-testing Patch
@workflow/core Patch
@workflow/web-shared 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

@TooTallNate TooTallNate force-pushed the 02-06-workflow_public_manifest branch from 1ea385a to c5e2098 Compare February 6, 2026 09:18
@TooTallNate TooTallNate force-pushed the 02-06-workflow_public_manifest branch from c5e2098 to 5128c98 Compare February 6, 2026 09:19
@TooTallNate TooTallNate changed the title feat: expose workflow manifest via HTTP when WORKFLOW_PUBLIC_MANIFEST=1 Expose workflow manifest via HTTP when WORKFLOW_PUBLIC_MANIFEST=1 Feb 6, 2026
When WORKFLOW_PUBLIC_MANIFEST=1 is set, each framework builder exposes
the manifest at /.well-known/workflow/v1/manifest.json via the most
appropriate mechanism for the framework:

- Next.js: Copies to public/.well-known/workflow/v1/ (static)
- SvelteKit: Copies to static/.well-known/workflow/v1/ (static)
- VercelBuildOutputAPI: Copies to .vercel/output/static/.well-known/workflow/v1/ (static)
- Nitro (vite/hono/express/fastify/nuxt/nitro-v2/v3): Virtual handler
- Astro: Generated manifest.json.js page route
- NestJS: @get endpoint on WorkflowController

Also fixes Astro LocalBuilder missing createManifest() call, removes
the unused example workbench public/ directory, and changes
BaseBuilder.createManifest() to return the manifest JSON string.
@TooTallNate TooTallNate force-pushed the 02-06-workflow_public_manifest branch from 67ad128 to fa58466 Compare February 6, 2026 18:43
@TooTallNate TooTallNate changed the title Expose workflow manifest via HTTP when WORKFLOW_PUBLIC_MANIFEST=1 Expose workflow manifest via HTTP when WORKFLOW_PUBLIC_MANIFEST=1 Feb 6, 2026
await copyFile(
join(workflowGeneratedDir, 'manifest.json'),
join(publicManifestDir, 'manifest.json')
);
Copy link
Copy Markdown
Member

@ijjk ijjk Feb 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of placing this in a static folder which won't get cleaned up if this is added for one run but not on a successive run and then could get deployed it feels more correct for the flow.js endpoint to handle serving this or not.

That would reduce additional endpoint being exposed as well, similar to what we did for the health check

Copy link
Copy Markdown
Member Author

TooTallNate commented Feb 6, 2026

Merge activity

  • Feb 6, 8:22 PM UTC: A user started a stack merge that includes this pull request via Graphite.
  • Feb 6, 8:22 PM UTC: @TooTallNate merged this pull request with Graphite.

@xmlking
Copy link
Copy Markdown

xmlking commented Apr 2, 2026

do we need to add public/.well-known/workflow/v1/manifest.json to .gitignore ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants