Skip to content

Add SDK version to workflow run executionContext for observability#868

Merged
pranaygp merged 3 commits into
mainfrom
pranaygp/wire-through-workflow-version
Jan 27, 2026
Merged

Add SDK version to workflow run executionContext for observability#868
pranaygp merged 3 commits into
mainfrom
pranaygp/wire-through-workflow-version

Conversation

@pranaygp
Copy link
Copy Markdown
Contributor

@pranaygp pranaygp commented Jan 27, 2026

Summary

  • Wire @workflow/core package version through the executionContext field when creating workflow runs
  • Display the version in the observability UI attribute panel after specVersion
  • Use genversion for build-time version injection (same pattern as @workflow/world-vercel)

Local

image (screenshot taken using agent-browser)

Vercel

image (screenshot taken using agent-browser)

Changes

  • @workflow/core:
    • Add genversion dependency and build scripts
    • Inject workflowCoreVersion into executionContext in start()
    • Add turbo.json to include src/version.ts in build outputs for caching
    • Fix hydrateResourceIO to extract workflowCoreVersion before stripping executionContext
  • @workflow/web-shared:
    • Extract and display workflowCoreVersion from executionContext in attribute panel
    • Display as @workflow/core version for readability

Verification

E2E Tests: All 45 tests passed locally against turbopack

Observability UI: Verified locally - the attribute panel now shows:

Attribute Value
workflowName sleepingWorkflow
status completed
runId wrun_01KG0JB0T3NKVG66WK3EQ9RYFB
deploymentId dpl_local@4.0.1-beta.27
specVersion 2
@workflow/core version 4.0.1-beta.41
createdAt 1/27/2026, 12:29:21.603 PM
startedAt 1/27/2026, 12:29:21.610 PM

Test plan

  • All existing tests pass (277 unit tests, 45 e2e tests)
  • Build succeeds with version.ts generated
  • Typecheck passes
  • Manual verification: @workflow/core version appears in observability UI

🤖 Generated with Claude Code

Wire `@workflow/core` package version through the `executionContext` field
when creating workflow runs. Display the version in the observability UI
attribute panel. Uses genversion for build-time version injection.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings January 27, 2026 20:14
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Jan 27, 2026

🦋 Changeset detected

Latest commit: 2cba1d2

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/web-shared Patch
@workflow/builders Patch
@workflow/cli Patch
@workflow/docs-typecheck Patch
@workflow/next Patch
@workflow/nitro Patch
workflow Patch
@workflow/astro Patch
@workflow/nest Patch
@workflow/sveltekit Patch
@workflow/world-testing Patch
@workflow/nuxt Patch
@workflow/example-nest Patch
@workflow/ai 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

@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented Jan 27, 2026

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

Project Deployment Actions Updated (UTC)
example-nextjs-workflow-turbopack Ready Ready Preview, Comment Jan 27, 2026 8:41pm
example-nextjs-workflow-webpack Ready Ready Preview, Comment Jan 27, 2026 8:41pm
example-workflow Ready Ready Preview, Comment Jan 27, 2026 8:41pm
workbench-astro-workflow Ready Ready Preview, Comment Jan 27, 2026 8:41pm
workbench-express-workflow Ready Ready Preview, Comment Jan 27, 2026 8:41pm
workbench-fastify-workflow Ready Ready Preview, Comment Jan 27, 2026 8:41pm
workbench-hono-workflow Ready Ready Preview, Comment Jan 27, 2026 8:41pm
workbench-nitro-workflow Ready Ready Preview, Comment Jan 27, 2026 8:41pm
workbench-nuxt-workflow Ready Ready Preview, Comment Jan 27, 2026 8:41pm
workbench-sveltekit-workflow Ready Ready Preview, Comment Jan 27, 2026 8:41pm
workbench-vite-workflow Ready Ready Preview, Comment Jan 27, 2026 8:41pm
workflow-docs Ready Ready Preview, Comment Jan 27, 2026 8:41pm
workflow-nest Ready Ready Preview, Comment Jan 27, 2026 8:41pm

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jan 27, 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 🥇 Nitro 0.029s (-38.8% 🟢) 1.007s (~) 0.978s 10 1.00x
💻 Local Express 0.031s (-31.8% 🟢) 1.007s (~) 0.977s 10 1.07x
💻 Local Next.js (Turbopack) 0.040s (-5.2% 🟢) 1.017s (~) 0.977s 10 1.40x
🐘 Postgres Nitro 0.204s (-26.0% 🟢) 1.015s (~) 0.812s 10 7.12x
🐘 Postgres Next.js (Turbopack) 0.263s (+46.9% 🔺) 1.022s (~) 0.758s 10 9.20x
🐘 Postgres Express 0.317s (+2.5%) 1.014s (~) 0.697s 10 11.09x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 0.655s (+4.4%) 1.562s (-9.8% 🟢) 0.907s 10 1.00x
▲ Vercel Express 0.696s (+1.3%) 1.500s (+0.7%) 0.804s 10 1.06x
▲ Vercel Next.js (Turbopack) 0.734s (-9.0% 🟢) 1.802s (-14.9% 🟢) 1.069s 10 1.12x

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

workflow with 1 step

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Nitro 1.075s (-3.4%) 2.006s (~) 0.931s 10 1.00x
💻 Local Express 1.081s (-3.4%) 2.007s (~) 0.926s 10 1.01x
💻 Local Next.js (Turbopack) 1.090s (~) 2.012s (~) 0.922s 10 1.01x
🐘 Postgres Next.js (Turbopack) 1.996s (-2.1%) 2.620s (~) 0.623s 10 1.86x
🐘 Postgres Express 2.156s (+1.4%) 3.013s (~) 0.857s 10 2.01x
🐘 Postgres Nitro 2.334s (+9.9% 🔺) 3.016s (~) 0.682s 10 2.17x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.900s (-6.7% 🟢) 3.762s (-1.1%) 0.862s 10 1.00x
▲ Vercel Nitro 3.091s (-1.6%) 3.904s (-3.9%) 0.813s 10 1.07x
▲ Vercel Next.js (Turbopack) 3.097s (+4.8%) 3.860s (-0.8%) 0.763s 10 1.07x

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

workflow with 10 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Nitro 10.550s (-2.5%) 11.016s (~) 0.466s 5 1.00x
💻 Local Express 10.575s (-2.6%) 11.016s (~) 0.441s 5 1.00x
💻 Local Next.js (Turbopack) 10.708s (~) 11.016s (~) 0.308s 5 1.01x
🐘 Postgres Next.js (Turbopack) 15.331s (+7.2% 🔺) 16.042s (+9.6% 🔺) 0.711s 5 1.45x
🐘 Postgres Nitro 15.442s (-7.3% 🟢) 16.039s (-6.9% 🟢) 0.596s 5 1.46x
🐘 Postgres Express 20.403s (~) 21.030s (~) 0.628s 5 1.93x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 24.737s (+4.8%) 25.534s (+3.1%) 0.797s 5 1.00x
▲ Vercel Next.js (Turbopack) 25.212s (+7.6% 🔺) 26.269s (+8.6% 🔺) 1.057s 5 1.02x
▲ Vercel Express 25.261s (+8.3% 🔺) 26.617s (+9.4% 🔺) 1.356s 5 1.02x

🔍 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 🥇 Nitro 1.354s (-3.1%) 2.006s (~) 0.653s 15 1.00x
💻 Local Express 1.354s (-3.2%) 2.007s (~) 0.653s 15 1.00x
💻 Local Next.js (Turbopack) 1.375s (-1.0%) 2.013s (~) 0.638s 15 1.02x
🐘 Postgres Next.js (Turbopack) 1.843s (-13.9% 🟢) 2.016s (-25.4% 🟢) 0.174s 15 1.36x
🐘 Postgres Nitro 2.107s (-4.8%) 2.751s (+6.0% 🔺) 0.644s 11 1.56x
🐘 Postgres Express 2.201s (+16.6% 🔺) 3.013s (+25.7% 🔺) 0.812s 10 1.63x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.879s (-4.2%) 3.691s (-2.3%) 0.812s 9 1.00x
▲ Vercel Nitro 3.095s (+3.1%) 3.993s (~) 0.897s 8 1.08x
▲ Vercel Next.js (Turbopack) 3.415s (-12.4% 🟢) 4.182s (-9.1% 🟢) 0.767s 8 1.19x

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

Promise.all with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Express 2.188s (-11.1% 🟢) 3.170s (+0.9%) 0.981s 10 1.00x
💻 Local Nitro 2.199s (-10.2% 🟢) 3.189s (+4.5%) 0.991s 10 1.00x
💻 Local Next.js (Turbopack) 2.506s (+3.6%) 3.085s (-1.6%) 0.579s 10 1.14x
🐘 Postgres Express 8.512s (-6.8% 🟢) 9.075s (-5.0% 🟢) 0.563s 4 3.89x
🐘 Postgres Nitro 9.804s (-2.0%) 10.381s (~) 0.577s 3 4.48x
🐘 Postgres Next.js (Turbopack) 10.651s (-19.5% 🟢) 11.367s (-15.1% 🟢) 0.715s 3 4.87x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 3.399s (-18.7% 🟢) 4.138s (-14.8% 🟢) 0.740s 8 1.00x
▲ Vercel Next.js (Turbopack) 3.482s (-9.7% 🟢) 4.229s (-9.4% 🟢) 0.748s 8 1.02x
▲ Vercel Express 3.916s (+19.9% 🔺) 4.731s (+21.5% 🔺) 0.815s 7 1.15x

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

Promise.race with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Nitro 1.349s (-4.5%) 2.006s (~) 0.657s 15 1.00x
💻 Local Express 1.361s (-3.6%) 2.007s (~) 0.647s 15 1.01x
💻 Local Next.js (Turbopack) 1.438s (+4.0%) 2.011s (~) 0.573s 15 1.07x
🐘 Postgres Next.js (Turbopack) 1.940s (-18.4% 🟢) 2.402s (-10.5% 🟢) 0.462s 13 1.44x
🐘 Postgres Express 2.174s (~) 2.595s (~) 0.421s 12 1.61x
🐘 Postgres Nitro 2.195s (-2.5%) 2.765s (+0.6%) 0.569s 11 1.63x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 2.855s (-2.7%) 3.779s (+1.8%) 0.925s 8 1.00x
▲ Vercel Nitro 3.161s (+8.7% 🔺) 3.897s (+2.5%) 0.736s 8 1.11x
▲ Vercel Express 3.672s (+22.9% 🔺) 4.488s (+20.1% 🔺) 0.816s 7 1.29x

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

Promise.race with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Express 2.263s (-15.0% 🟢) 3.252s (+3.8%) 0.990s 10 1.00x
💻 Local Nitro 2.268s (-9.7% 🟢) 3.246s (+7.7% 🔺) 0.977s 10 1.00x
💻 Local Next.js (Turbopack) 2.631s (+7.0% 🔺) 3.021s (-0.6%) 0.390s 10 1.16x
🐘 Postgres Next.js (Turbopack) 12.031s (-13.1% 🟢) 12.454s (-11.3% 🟢) 0.423s 3 5.32x
🐘 Postgres Express 12.220s (+2.3%) 12.687s (~) 0.467s 3 5.40x
🐘 Postgres Nitro 13.023s (+1.7%) 13.395s (~) 0.372s 3 5.76x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 3.115s (-18.0% 🟢) 3.758s (-17.2% 🟢) 0.644s 8 1.00x
▲ Vercel Express 3.234s (+3.7%) 4.051s (+7.5% 🔺) 0.817s 8 1.04x
▲ Vercel Next.js (Turbopack) 4.067s (+22.9% 🔺) 4.768s (+24.8% 🔺) 0.701s 7 1.31x

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

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.114s (-39.9% 🟢) 0.999s (+0.8%) 0.013s (-3.0%) 1.020s (~) 0.906s 10 1.00x
💻 Local Nitro 0.119s (-33.4% 🟢) 0.999s (+0.7%) 0.012s (-12.1% 🟢) 1.019s (~) 0.900s 10 1.04x
💻 Local Next.js (Turbopack) 0.143s (-0.7%) 1.003s (~) 0.016s (-1.8%) 1.027s (~) 0.884s 10 1.25x
🐘 Postgres Next.js (Turbopack) 1.091s (+62.7% 🔺) 1.938s (+105.5% 🔺) 0.000s (~) 2.018s (+98.5% 🔺) 0.927s 10 9.54x
🐘 Postgres Nitro 1.136s (-11.0% 🟢) 1.909s (+8.2% 🔺) 0.000s (NaN%) 2.015s (~) 0.879s 10 9.93x
🐘 Postgres Express 2.311s (+18.7% 🔺) 2.732s (+15.5% 🔺) 0.000s (NaN%) 3.015s (+15.4% 🔺) 0.704s 10 20.20x

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 3.148s (-1.6%) 3.541s (+5.8% 🔺) 0.655s (-31.6% 🟢) 4.694s (-4.0%) 1.546s 10 1.00x
▲ Vercel Express 3.204s (+3.1%) 3.384s (+2.8%) 0.797s (-38.4% 🟢) 4.693s (-8.8% 🟢) 1.488s 10 1.02x
▲ Vercel Next.js (Turbopack) 3.229s (+1.5%) 3.384s (+4.6%) 0.936s (-26.8% 🟢) 4.841s (-3.5%) 1.613s 10 1.03x

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

Summary

Fastest Framework by World

Winner determined by most benchmark wins

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

Winner determined by most benchmark wins

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

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jan 27, 2026

🧪 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

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Adds @workflow/core SDK version metadata to workflow run context and surfaces it in the observability UI.

Changes:

  • Generate a build-time src/version.ts in @workflow/core via genversion and inject workflowCoreVersion into executionContext when creating runs.
  • Display workflowCoreVersion in the web attribute panel (ordered after specVersion).
  • Misc formatting/lockfile updates.

Reviewed changes

Copilot reviewed 6 out of 8 changed files in this pull request and generated 2 comments.

Show a summary per file
File Description
pnpm-lock.yaml Adds genversion and updates lock snapshots.
packages/core/src/runtime/start.ts Injects workflowCoreVersion into executionContext on run_created.
packages/core/package.json Runs genversion during build/dev/typecheck and cleans generated file.
packages/core/.gitignore Ignores generated src/version.ts.
packages/web-shared/src/sidebar/attribute-panel.tsx Adds workflowCoreVersion attribute and attempts to extract it from executionContext.
packages/next/src/builder.ts Formatting-only change to regex block.
packages/cli/bin/run.js Formatting-only change to warning logging.
.changeset/wire-workflow-version.md Changeset to publish patch releases for core + web-shared.
Files not reviewed (1)
  • pnpm-lock.yaml: Language not supported

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +826 to +836
// Extract workflowCoreVersion from executionContext for display
const displayData = useMemo(() => {
const result = { ...data };
const execCtx = data.executionContext as
| Record<string, unknown>
| undefined;
if (execCtx?.workflowCoreVersion) {
result.workflowCoreVersion = execCtx.workflowCoreVersion;
}
return result;
}, [data]);
Copy link

Copilot AI Jan 27, 2026

Choose a reason for hiding this comment

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

displayData extracts workflowCoreVersion from data.executionContext, but executionContext appears to be stripped server-side by hydrateResourceIO (see @workflow/core/observability removing executionContext). As a result, the UI likely never receives executionContext and this field will not render. Consider hoisting workflowCoreVersion into the returned run/step/hook shape before hydration strips executionContext, or adjust hydration to preserve executionContext.workflowCoreVersion while still omitting sensitive fields like traceCarrier.

Suggested change
// Extract workflowCoreVersion from executionContext for display
const displayData = useMemo(() => {
const result = { ...data };
const execCtx = data.executionContext as
| Record<string, unknown>
| undefined;
if (execCtx?.workflowCoreVersion) {
result.workflowCoreVersion = execCtx.workflowCoreVersion;
}
return result;
}, [data]);
// Memoized view of data used for attribute display
const displayData = useMemo(() => ({ ...data }), [data]);

Copilot uses AI. Check for mistakes.
Comment on lines +38 to +43
"build": "genversion --es6 src/version.ts && tsc",
"dev": "genversion --es6 src/version.ts && tsc --watch",
"clean": "tsc --build --clean && rm -rf dist src/version.ts",
"test": "cross-env WORKFLOW_TARGET_WORLD=local vitest run src",
"test:e2e": "vitest run e2e",
"typecheck": "tsc --noEmit"
"typecheck": "genversion --es6 src/version.ts && tsc --noEmit"
Copy link

Copilot AI Jan 27, 2026

Choose a reason for hiding this comment

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

build now generates src/version.ts, but Turborepo’s root build task only declares dist/** as an output. If the build task is satisfied from cache (especially in CI/remote caching), src/version.ts may not be present for downstream tasks (notably test, which runs against src and does not run genversion). Consider adding packages/core/turbo.json (like packages/world-vercel/turbo.json) to include src/version.ts in build.outputs, or alternatively generate src/version.ts in the test script as well.

Copilot uses AI. Check for mistakes.
- Extract workflowCoreVersion from executionContext in hydrateResourceIO
  before stripping the context (addresses Copilot review comment)
- Add turbo.json to include src/version.ts in build outputs for caching

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Use a display name mapping to render the attribute as "@workflow/core version"
in the observability UI for better readability.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@pranaygp
Copy link
Copy Markdown
Contributor Author

pranaygp commented Jan 27, 2026

Verification Complete

The @workflow/core version attribute is now properly displayed in the observability UI.

Verified locally:

  • Workflow run details page shows the attribute panel
  • The attribute displays as @workflow/core version: 4.0.1-beta.41
  • Positioned right after specVersion as expected

E2E Tests: All 45 tests passed locally against turbopack.

Changes in this PR:

  1. @workflow/core: Added genversion for build-time version injection, injected workflowCoreVersion into executionContext in start()
  2. @workflow/core: Fixed hydrateResourceIO to extract workflowCoreVersion before stripping executionContext
  3. @workflow/core: Added turbo.json to include src/version.ts in build outputs for caching
  4. @workflow/web-shared: Added display name mapping to render as @workflow/core version in the UI

Copy link
Copy Markdown
Member

@TooTallNate TooTallNate left a comment

Choose a reason for hiding this comment

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

Should be the version of the workflow package, not @workflow/core, right?

@pranaygp
Copy link
Copy Markdown
Contributor Author

Vercel World Verification

Confirmed that workflowCoreVersion is properly wired through the Vercel world as well!

From the CI logs of E2E Vercel Prod Tests (nextjs-turbopack):

{
  "runId": "wrun_01KG0K0WSY5KPNZRVJBW2HMQSP",
  "status": "completed",
  "deploymentId": "dpl_EP7h7F3eDGxrPXzbVHF4uig6Ufo2",
  "workflowName": "workflow//example/workflows/99_e2e.ts//addTenWorkflow",
  "specVersion": 2,
  "input": [123],
  "output": 133,
  "workflowCoreVersion": "4.0.1-beta.41"
}

The version is being stored in executionContext and properly extracted by hydrateResourceIO for both:

  • Local world (verified via local e2e tests + observability UI)
  • Vercel world (verified via CI e2e test logs above)

@pranaygp
Copy link
Copy Markdown
Contributor Author

pranaygp commented Jan 27, 2026

Vercel World Screenshot Verification

Confirmed: @workflow/core version: 4.0.1-beta.41 is properly displayed in the Vercel world observability UI!

Screenshot Details:

  • Connected to: vercel-labs/example-nextjs-workflow-turbopack (preview environment)
  • Run ID: wrun_01KG0K0WSY5KPNZRVJBW2HMQSP
  • Deployment ID: dpl_EP7h7F3eDGxrPXzbVHF4uig6Ufo2
  • Workflow: addTenWorkflow

Attribute Panel shows:

Attribute Value
workflowName addTenWorkflow
status completed
runId wrun_01KG0K0WSY5KPNZRVJBW2HMQSP
deploymentId dpl_EP7h7F3eDGxrPXzbVHF4uig6Ufo2
specVersion 2
@workflow/core version 4.0.1-beta.41

Screenshot saved at: /tmp/vercel-world-version-screenshot.png

To add the screenshot to this PR, drag and drop the image file into the PR description edit box.

@pranaygp pranaygp requested a review from TooTallNate January 27, 2026 21:08
Copy link
Copy Markdown
Member

@TooTallNate TooTallNate left a comment

Choose a reason for hiding this comment

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

In a follow-up we should update changesets' configuration to keep workflow and @workflow/core package version numbers in sync.

Copy link
Copy Markdown
Contributor

@karthikscale3 karthikscale3 left a comment

Choose a reason for hiding this comment

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

Tested and looks great!

@pranaygp
Copy link
Copy Markdown
Contributor Author

In a follow-up we should update changesets' configuration to keep workflow and @workflow/core package version numbers in sync.

will do

@pranaygp pranaygp merged commit c45bc3f into main Jan 27, 2026
98 checks passed
@pranaygp pranaygp deleted the pranaygp/wire-through-workflow-version branch January 27, 2026 21:15
@pranaygp
Copy link
Copy Markdown
Contributor Author

In a follow-up we should update changesets' configuration to keep workflow and @workflow/core package version numbers in sync.

Done in #871

pranaygp added a commit that referenced this pull request Jan 28, 2026
…s-and-commands

* origin/main:
  fix(@workflow/ai): support provider-executed tools (AI SDK v6) (#734)
  Publish "workflow" and "@workflow/core" package versions in sync (#870)
  Add SDK version to workflow run executionContext for observability (#868)
  Allow recreateRun to accept an optional deploymentId parameter (#869)
  Add support for top-level `using` declarations inside of step / workflow functions (#866)
  docs: URL in docs was missing the docs/ prefix, 404 errors (#852)
  Add "classes" object to `manifest.json` file (#864)
  Fix Nest workbench app build (#865)
  Ignore Astro on local dev tests for source map e2e tests (#863)
  Enable custom class serialization transformations for "client" mode (#860)
  Submit request bodies with CBOR encoding (#844)
  [world-vercel] Update queue to use VQS v3 API (#799)
  NestJS framework support (#840)
  Fix resolve hook theming and token fetching. (#856)
  docs: rename Control Flow Patterns to Common Patterns and add new content (#846)
  docs: revamp World documentation pages (#763)
  Remove unused `getWritable` stub function (#855)

# Conflicts:
#	packages/core/package.json
#	pnpm-lock.yaml
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.

4 participants