[cli] [core] Probe deployment specVersion before CLI start - #1629

Merged
VaguelySerious merged 17 commits into
mainfrom
peter/cli-specversion-probe
Apr 7, 2026
Merged

[cli] [core] Probe deployment specVersion before CLI start#1629
VaguelySerious merged 17 commits into
mainfrom
peter/cli-specversion-probe

Conversation

@VaguelySerious

@VaguelySeriousVaguelySerious commented Apr 7, 2026

Copy link
Copy Markdown
Member

Summary

Based on #1627. CLI start command now probes the target deployment's specVersion via health check before calling start(), ensuring the correct queue transport is used.

  • Health check always uses JSON transport (specVersion: SPEC_VERSION_LEGACY) so the probe works against both old and new deployments
  • Adds deploymentId option to HealthCheckOptions for targeted health checks
  • Falls back to the existing run's specVersion if health check fails (e.g. old deployment without health check support)

Other paths that call start() without knowing specVersion

Call siteKnows specVersion?Notes
CLI startNow probedThis PR
recreateRunFromExisting (web dashboard replay)YesUses run.specVersion from original run
User code (import { start } from 'workflow')N/ARuns ON the deployment, so SPEC_VERSION_CURRENT is correct
Testing server (world-testing)NoNot production-relevant

Test plan

  • packages/core unit tests pass (580/580)
  • Full build passes
  • e2e: CLI start against old deployment uses JSON transport
  • e2e: CLI start against new deployment uses CBOR transport
  • e2e: CLI start with health check timeout falls back to run specVersion

🤖 Generated with Claude Code

VaguelySeriousand others added 13 commits April 6, 2026 15:56
@VaguelySerious@claude
fix: gate queue transport format on specVersion for CBOR compat
8399d51
Bump SPEC_VERSION_CURRENT to 3 and fix isLegacySpecVersion to check
against SPEC_VERSION_LEGACY instead of SPEC_VERSION_CURRENT, preventing
v2 runs from being incorrectly treated as legacy when the version bumps.
Add JsonTransport and DualTransport to world-vercel queue: the handler
uses DualTransport (CBOR-first, JSON fallback) to accept messages from
both old and new deployments, while the send path selects CBOR or JSON
based on the target run's specVersion. Pass specVersion through queue
opts from start(), reenqueueRun(), wakeUpRun(), and resumeHook().
Only include runInput in the queue payload for specVersion >= 3, creating
clean separation between old and new behavior.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
[core] [world] Gate CBOR queue transport on specVersion
b6b6dcf
Bump specVersion to 3. Use JSON transport for queue messages targeting
older deployments (specVersion < 3), CBOR for new ones. Handler uses
dual transport that deserializes both formats, so new deployments can
receive messages from old and new senders.
Fixes replay/reenqueue from the dashboard to older deployments that
expect JSON queue messages.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Use named spec version constants for feature boundaries
dd2699b
Replace SPEC_VERSION_CURRENT comparisons with named constants
(SPEC_VERSION_SUPPORTS_CBOR_QUEUE_TRANSPORT, SPEC_VERSION_SUPPORTS_EVENT_SOURCING)
so future SPEC_VERSION_CURRENT bumps don't shift existing feature gates.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Update world-postgres test to use SPEC_VERSION_CURRENT
ddc8c31
Replace hardcoded specVersion: 2 with SPEC_VERSION_CURRENT so
the test tracks spec version bumps.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Include specVersion in health check responses
cf3dd88
Both the HTTP health check endpoint (?__health) and the queue-based
health check stream now return specVersion, allowing observability
tools to query deployment capabilities.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious
Merge branch 'main' into peter/cbor-transport-compat
50407fe
@VaguelySerious
fix health check test
330d70d
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@vercel@VaguelySerious
Fix: Health check e2e test assertions are missing the endpoint fiel…
82dcbe2
…d, causing `toEqual` to fail due to exact equality mismatch.
This commit fixes the issue reported at packages/core/e2e/e2e.test.ts:1550
**Bug explanation:**
The `withHealthCheck` handler in `packages/core/src/runtime/helpers.ts` returns a JSON response with three fields: `{ healthy: true, endpoint: url.pathname, specVersion: SPEC_VERSION_CURRENT }`. However, the HTTP-based health check e2e test in `packages/core/e2e/e2e.test.ts` (lines 1549-1553 and 1567-1571) uses `toEqual` to assert against objects that only have two fields: `{ healthy: true, specVersion: SPEC_VERSION_CURRENT }`, missing the `endpoint` field.
In Vitest, `toEqual` performs exact deep equality checking. When the actual response object contains `{ healthy: true, endpoint: "/.well-known/workflow/v1/flow", specVersion: "..." }` but the expected object only has `{ healthy: true, specVersion: "..." }`, the assertion fails because the actual object has an extra `endpoint` property not present in the expected object.
This affects both the flow endpoint health check assertion and the step endpoint health check assertion.
**Fix explanation:**
Added the missing `endpoint` field to both `toEqual` assertions:
- For the flow endpoint: `endpoint: '/.well-known/workflow/v1/flow'` (the pathname portion of `/.well-known/workflow/v1/flow?__health`)
- For the step endpoint: `endpoint: '/.well-known/workflow/v1/step'` (the pathname portion of `/.well-known/workflow/v1/step?__health`)
These values match what `url.pathname` returns in the handler (the `?__health` query parameter is not part of the pathname). This makes the test assertions exactly match the actual response structure from the handler.
Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Co-authored-by: VaguelySerious <mittgfu@gmail.com>
@VaguelySerious
fix
ce9ba33
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious
fix
57cb399
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious@claude
Propagate specVersion through queue-based health check result
419de89
Update HealthCheckResult to include specVersion and parse it from the
stream response, so observability tools can query deployment capabilities
through both the HTTP and queue-based health check paths.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Fix TypeScript cast in parseHealthCheckResponse
ff8a79c
Use Record<string, unknown> instead of narrower casts that tsc
rejects as insufficient overlap.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
[cli] [core] Probe deployment specVersion before CLI start
7b42568
CLI start command now queries the deployment's health check endpoint
to determine its specVersion before calling start(). This ensures the
correct queue transport is used (JSON for old deployments, CBOR for
new). Falls back to the run's specVersion if health check fails.
Health check always uses JSON transport (specVersion: SPEC_VERSION_LEGACY)
so the probe works against both old and new deployments. Also adds
deploymentId option to HealthCheckOptions for targeted health checks.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@vercel

vercelBot commented Apr 7, 2026•
edited
Loading

Copy link
Copy Markdown
Contributor

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

ProjectDeploymentActionsUpdated (UTC)
example-nextjs-workflow-turbopackReadyReadyPreview, CommentApr 7, 2026 5:52pm
example-nextjs-workflow-webpackReadyReadyPreview, CommentApr 7, 2026 5:52pm
example-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-astro-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-express-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-fastify-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-hono-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-nitro-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-nuxt-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-sveltekit-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-vite-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workflow-docsReadyReadyPreview, Comment, Open in v0Apr 7, 2026 5:52pm
workflow-swc-playgroundReadyReadyPreview, CommentApr 7, 2026 5:52pm

@VaguelySerious
VaguelySerious requested a review from a team as a code ownerApril 7, 2026 00:22
@changeset-bot

changeset-botBot commented Apr 7, 2026•
edited
Loading

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 51fb2ab

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

This PR includes changesets to release 16 packages
NameType
@workflow/corePatch
@workflow/cliPatch
@workflow/buildersPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/vitestPatch
@workflow/web-sharedPatch
workflowPatch
@workflow/world-testingPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch
@workflow/aiPatch

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

github-actionsBot commented Apr 7, 2026•
edited
Loading

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

❌ Some tests failed

Summary

PassedFailedSkippedTotal
❌ ▲ Vercel Production878167946
✅ 💻 Local Development85401781032
✅ 📦 Local Production85401781032
✅ 🐘 Local Postgres85401781032
✅ 🪟 Windows780886
❌ 🌍 Community Worlds1660884
✅ 📋 Other216042258
Total3750616594470

❌ Failed Tests

▲ Vercel Production (1 failed)

hono (1 failed):

🌍 Community Worlds (60 failed)

mongodb-dev (1 failed):

  • dev e2e should rebuild on imported step dependency change

redis-dev (1 failed):

  • dev e2e should rebuild on imported step dependency change

turso-dev (1 failed):

  • dev e2e should rebuild on imported step dependency change

turso (57 failed):

  • addTenWorkflow | wrun_01KNMH5VCWZ2YQDPP365WEZTM4
  • addTenWorkflow | wrun_01KNMH5VCWZ2YQDPP365WEZTM4
  • wellKnownAgentWorkflow (.well-known/agent) | wrun_01KNMH75H1GT8X09J9WS5F6FA6
  • should work with react rendering in step
  • promiseAllWorkflow | wrun_01KNMH63YAHQKDCZQT1EPYKGX8
  • promiseRaceWorkflow | wrun_01KNMH699ZAQD55FBQV3XNHM7X
  • promiseAnyWorkflow | wrun_01KNMH6C1XSP0EZ96TT0J5E8PF
  • importedStepOnlyWorkflow | wrun_01KNMH7GSJTNP0DX1PGSPFNTZZ
  • hookWorkflow | wrun_01KNMH6S06RS6VXGS41PF3GWSB
  • hookWorkflow is not resumable via public webhook endpoint | wrun_01KNMH76KMG0ZCB7ST88V553JE
  • webhookWorkflow | wrun_01KNMH7H30FD15T64RRS74743D
  • sleepingWorkflow | wrun_01KNMH7TG251JCYH1HS6DV9PKV
  • parallelSleepWorkflow | wrun_01KNMH87BSQPDNQBW8RR8GMHVR
  • nullByteWorkflow | wrun_01KNMH8B46P0EM2F1T1T2EQT07
  • workflowAndStepMetadataWorkflow | wrun_01KNMH8DKDK9H0CTSMSMJYV7J1
  • fetchWorkflow | wrun_01KNMHBA5EJNGZ9Y10R47QQ7TS
  • promiseRaceStressTestWorkflow | wrun_01KNMHBD0VT8JK2JD5N8JDTNTX
  • 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()
  • error handling not registered WorkflowNotRegisteredError fails the run when workflow does not exist
  • error handling not registered StepNotRegisteredError fails the step but workflow can catch it
  • error handling not registered StepNotRegisteredError fails the run when not caught in workflow
  • hookCleanupTestWorkflow - hook token reuse after workflow completion | wrun_01KNMHF707573TY2VWEG6X4DNH
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously | wrun_01KNMHFWK8Q44KY5E9X4R9ASHD
  • hookDisposeTestWorkflow - hook token reuse after explicit disposal while workflow still running | wrun_01KNMHGM9JGZWZSBXT32C90R37
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars) | wrun_01KNMHHA40QC8M5BFCX3WRN9DS
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument | wrun_01KNMHHKY5FCTHAD7DQ2RGH0AW
  • closureVariableWorkflow - nested step functions with closure variables | wrun_01KNMHHT09G8K4G7EG4F36D42G
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step | wrun_01KNMHHWDR6ZZGV5585HXJBY19
  • health check (queue-based) - workflow and step endpoints respond to health check messages
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly | wrun_01KNMHJBHXQHBXCB06Q1RQ364Z
  • Calculator.calculate - static workflow method using static step methods from another class | wrun_01KNMHJHYZ7X33V0S840FX5W9Q
  • AllInOneService.processNumber - static workflow method using sibling static step methods | wrun_01KNMHJRQ8QEZG1WYA9X4NE9G4
  • ChainableService.processWithThis - static step methods using this to reference the class | wrun_01KNMHJZB674R8TQ8TN8AA026X
  • thisSerializationWorkflow - step function invoked with .call() and .apply() | wrun_01KNMHK64J28XRFGM5X10GD015
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE | wrun_01KNMHKCJH3BSFD5V6A5DJSKV8
  • instanceMethodStepWorkflow - instance methods with "use step" directive | wrun_01KNMHKJXNGX0BC6AG4EP84PH0
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context | wrun_01KNMHKW4R2DSSHKGVJXT66ZGB
  • stepFunctionAsStartArgWorkflow - step function reference passed as start() argument | wrun_01KNMHM4QSV8SW6786SA9H6NFD
  • cancelRun - cancelling a running workflow | wrun_01KNMHMC10ES9NS6ZW9MAK03E4
  • cancelRun via CLI - cancelling a running workflow | wrun_01KNMHMMSK0AGPXGJR7JK82QDR
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router
  • hookWithSleepWorkflow - hook payloads delivered correctly with concurrent sleep | wrun_01KNMHMZYT36WW88RZPBQRKBH1
  • sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration | wrun_01KNMHNKEWEEQWTPPWGB7YNWSW
  • sleepWithSequentialStepsWorkflow - sequential steps work with concurrent sleep (control) | wrun_01KNMHNY2NHRBQ53J3TY57ZGSR
  • importMetaUrlWorkflow - import.meta.url is available in step bundles | wrun_01KNMHP4PAJEEA4DPSG64JC7M6
  • metadataFromHelperWorkflow - getWorkflowMetadata/getStepMetadata work from module-level helper (#1577) | wrun_01KNMHP6N2TBYR581JBV88ESXE
  • resilient start: addTenWorkflow completes when run_created returns 500 | wrun_01KNMHP8T5FNQQ8Z6MNZH87SNG

Details by Category

❌ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro7907
✅ example7907
✅ express7907
✅ fastify7907
❌ hono7817
✅ nextjs-turbopack8402
✅ nextjs-webpack8402
✅ nitro7907
✅ nuxt7907
✅ sveltekit7907
✅ vite7907
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable72014
✅ express-stable72014
✅ fastify-stable72014
✅ hono-stable72014
✅ nextjs-turbopack-canary61025
✅ nextjs-turbopack-stable7808
✅ nextjs-webpack-canary61025
✅ nextjs-webpack-stable7808
✅ nitro-stable72014
✅ nuxt-stable72014
✅ sveltekit-stable72014
✅ vite-stable72014
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable72014
✅ express-stable72014
✅ fastify-stable72014
✅ hono-stable72014
✅ nextjs-turbopack-canary61025
✅ nextjs-turbopack-stable7808
✅ nextjs-webpack-canary61025
✅ nextjs-webpack-stable7808
✅ nitro-stable72014
✅ nuxt-stable72014
✅ sveltekit-stable72014
✅ vite-stable72014
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable72014
✅ express-stable72014
✅ fastify-stable72014
✅ hono-stable72014
✅ nextjs-turbopack-canary61025
✅ nextjs-turbopack-stable7808
✅ nextjs-webpack-canary61025
✅ nextjs-webpack-stable7808
✅ nitro-stable72014
✅ nuxt-stable72014
✅ sveltekit-stable72014
✅ vite-stable72014
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack7808
❌ 🌍 Community Worlds
AppPassedFailedSkipped
❌ mongodb-dev410
❌ redis-dev410
❌ turso-dev410
❌ turso4578
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable72014
✅ e2e-local-postgres-nest-stable72014
✅ e2e-local-prod-nest-stable72014

📋 View full workflow run

❌ Some E2E test jobs failed:

  • Vercel Prod: failure
  • Local Dev: success
  • Local Prod: success
  • Local Postgres: success
  • Windows: success

Check the workflow run for details.

@VaguelySerious@claude
Include workflowCoreVersion in health check responses
51fb2ab
Both the HTTP (?__health) and queue-based health check endpoints
now return the @workflow/core package version, allowing observability
tools to identify exactly which SDK version a deployment is running.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious
VaguelySerious merged commit a6bcea9 into mainApr 7, 2026
92 of 99 checks passed
@VaguelySerious
VaguelySerious deleted the peter/cli-specversion-probe branch April 7, 2026 18:03
@ghostghost mentioned this pull request Apr 7, 2026
Merged
VaguelySerious added a commit that referenced this pull request Apr 7, 2026
@VaguelySerious
[cli] [core] Probe deployment specVersion before CLI start (#1629)
f0d6a85
@TooTallNateTooTallNate mentioned this pull request Apr 8, 2026
Merged
7 tasks
@VaguelySeriousVaguelySerious mentioned this pull request Apr 16, 2026
Closed
3 tasks
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@TooTallNateTooTallNateTooTallNate approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@VaguelySerious@TooTallNate
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
[cli] [core] Probe deployment specVersion before CLI start - #1629
Merged
VaguelySerious merged 17 commits into
mainfrom 
peter/cli-specversion-probe
Apr 7, 2026
Merged
[cli] [core] Probe deployment specVersion before CLI start#1629
VaguelySerious merged 17 commits into
mainfrom 
peter/cli-specversion-probe
Conversation
@VaguelySerious
@VaguelySeriousVaguelySerious
commented
Apr 7, 2026

Copy link


Copy Markdown

Member
Summary
Based on #1627. CLI start command now probes the target deployment's specVersion via health check before calling start(), ensuring the correct queue transport is used.
  • Health check always uses JSON transport (specVersion: SPEC_VERSION_LEGACY) so the probe works against both old and new deployments
  • Adds deploymentId option to HealthCheckOptions for targeted health checks
  • Falls back to the existing run's specVersion if health check fails (e.g. old deployment without health check support)
Other paths that call start() without knowing specVersion
Call siteKnows specVersion?Notes
CLI startNow probedThis PR
recreateRunFromExisting (web dashboard replay)YesUses run.specVersion from original run
User code (import { start } from 'workflow')N/ARuns ON the deployment, so SPEC_VERSION_CURRENT is correct
Testing server (world-testing)NoNot production-relevant
Test plan
  • packages/core unit tests pass (580/580)
  •  Full build passes
  •  e2e: CLI start against old deployment uses JSON transport
  •  e2e: CLI start against new deployment uses CBOR transport
  •  e2e: CLI start with health check timeout falls back to run specVersion
🤖 Generated with Claude Code
VaguelySeriousand others
added 13 commits
April 6, 2026 15:56
@VaguelySerious@claude
fix: gate queue transport format on specVersion for CBOR compat
8399d51
Bump SPEC_VERSION_CURRENT to 3 and fix isLegacySpecVersion to check
against SPEC_VERSION_LEGACY instead of SPEC_VERSION_CURRENT, preventing
v2 runs from being incorrectly treated as legacy when the version bumps.
Add JsonTransport and DualTransport to world-vercel queue: the handler
uses DualTransport (CBOR-first, JSON fallback) to accept messages from
both old and new deployments, while the send path selects CBOR or JSON
based on the target run's specVersion. Pass specVersion through queue
opts from start(), reenqueueRun(), wakeUpRun(), and resumeHook().
Only include runInput in the queue payload for specVersion >= 3, creating
clean separation between old and new behavior.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
[core] [world] Gate CBOR queue transport on specVersion
b6b6dcf
Bump specVersion to 3. Use JSON transport for queue messages targeting
older deployments (specVersion < 3), CBOR for new ones. Handler uses
dual transport that deserializes both formats, so new deployments can
receive messages from old and new senders.
Fixes replay/reenqueue from the dashboard to older deployments that
expect JSON queue messages.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Use named spec version constants for feature boundaries
dd2699b
Replace SPEC_VERSION_CURRENT comparisons with named constants
(SPEC_VERSION_SUPPORTS_CBOR_QUEUE_TRANSPORT, SPEC_VERSION_SUPPORTS_EVENT_SOURCING)
so future SPEC_VERSION_CURRENT bumps don't shift existing feature gates.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Update world-postgres test to use SPEC_VERSION_CURRENT
ddc8c31
Replace hardcoded specVersion: 2 with SPEC_VERSION_CURRENT so
the test tracks spec version bumps.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Include specVersion in health check responses
cf3dd88
Both the HTTP health check endpoint (?__health) and the queue-based
health check stream now return specVersion, allowing observability
tools to query deployment capabilities.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious
Merge branch 'main' into peter/cbor-transport-compat
50407fe
@VaguelySerious
fix health check test
330d70d
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@vercel@VaguelySerious
Fix: Health check e2e test assertions are missing the endpoint fiel…
82dcbe2
…d, causing `toEqual` to fail due to exact equality mismatch.
This commit fixes the issue reported at packages/core/e2e/e2e.test.ts:1550
**Bug explanation:**
The `withHealthCheck` handler in `packages/core/src/runtime/helpers.ts` returns a JSON response with three fields: `{ healthy: true, endpoint: url.pathname, specVersion: SPEC_VERSION_CURRENT }`. However, the HTTP-based health check e2e test in `packages/core/e2e/e2e.test.ts` (lines 1549-1553 and 1567-1571) uses `toEqual` to assert against objects that only have two fields: `{ healthy: true, specVersion: SPEC_VERSION_CURRENT }`, missing the `endpoint` field.
In Vitest, `toEqual` performs exact deep equality checking. When the actual response object contains `{ healthy: true, endpoint: "/.well-known/workflow/v1/flow", specVersion: "..." }` but the expected object only has `{ healthy: true, specVersion: "..." }`, the assertion fails because the actual object has an extra `endpoint` property not present in the expected object.
This affects both the flow endpoint health check assertion and the step endpoint health check assertion.
**Fix explanation:**
Added the missing `endpoint` field to both `toEqual` assertions:
- For the flow endpoint: `endpoint: '/.well-known/workflow/v1/flow'` (the pathname portion of `/.well-known/workflow/v1/flow?__health`)
- For the step endpoint: `endpoint: '/.well-known/workflow/v1/step'` (the pathname portion of `/.well-known/workflow/v1/step?__health`)
These values match what `url.pathname` returns in the handler (the `?__health` query parameter is not part of the pathname). This makes the test assertions exactly match the actual response structure from the handler.
Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Co-authored-by: VaguelySerious <mittgfu@gmail.com>
@VaguelySerious
fix
ce9ba33
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious
fix
57cb399
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious@claude
Propagate specVersion through queue-based health check result
419de89
Update HealthCheckResult to include specVersion and parse it from the
stream response, so observability tools can query deployment capabilities
through both the HTTP and queue-based health check paths.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Fix TypeScript cast in parseHealthCheckResponse
ff8a79c
Use Record<string, unknown> instead of narrower casts that tsc
rejects as insufficient overlap.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
[cli] [core] Probe deployment specVersion before CLI start
7b42568
CLI start command now queries the deployment's health check endpoint
to determine its specVersion before calling start(). This ensures the
correct queue transport is used (JSON for old deployments, CBOR for
new). Falls back to the run's specVersion if health check fails.
Health check always uses JSON transport (specVersion: SPEC_VERSION_LEGACY)
so the probe works against both old and new deployments. Also adds
deploymentId option to HealthCheckOptions for targeted health checks.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@vercel
vercelBot
commented
Apr 7, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
The latest updates on your projects. Learn more about Vercel for GitHub.
ProjectDeploymentActionsUpdated (UTC)
example-nextjs-workflow-turbopackReadyReadyPreview, CommentApr 7, 2026 5:52pm
example-nextjs-workflow-webpackReadyReadyPreview, CommentApr 7, 2026 5:52pm
example-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-astro-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-express-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-fastify-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-hono-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-nitro-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-nuxt-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-sveltekit-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-vite-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workflow-docsReadyReadyPreview, Comment, Open in v0Apr 7, 2026 5:52pm
workflow-swc-playgroundReadyReadyPreview, CommentApr 7, 2026 5:52pm
@VaguelySerious
VaguelySerious
requested a review
from a team
as a code ownerApril 7, 2026 00:22
@changeset-bot
changeset-botBot
commented
Apr 7, 2026•

edited

Loading

Copy link


Copy Markdown

🦋 Changeset detected
Latest commit: 51fb2ab
The changes in this PR will be included in the next version bump.
This PR includes changesets to release 16 packages
NameType
@workflow/corePatch
@workflow/cliPatch
@workflow/buildersPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/vitestPatch
@workflow/web-sharedPatch
workflowPatch
@workflow/world-testingPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch
@workflow/aiPatch
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
github-actionsBot
commented
Apr 7, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
🧪 E2E Test Results
❌ Some tests failed
Summary
PassedFailedSkippedTotal
❌ ▲ Vercel Production878167946
✅ 💻 Local Development85401781032
✅ 📦 Local Production85401781032
✅ 🐘 Local Postgres85401781032
✅ 🪟 Windows780886
❌ 🌍 Community Worlds1660884
✅ 📋 Other216042258
Total3750616594470
❌ Failed Tests
▲ Vercel Production (1 failed)
hono (1 failed):
🌍 Community Worlds (60 failed)
mongodb-dev (1 failed):
  • dev e2e should rebuild on imported step dependency change
redis-dev (1 failed):
  • dev e2e should rebuild on imported step dependency change
turso-dev (1 failed):
  • dev e2e should rebuild on imported step dependency change
turso (57 failed):
  • addTenWorkflow | wrun_01KNMH5VCWZ2YQDPP365WEZTM4
  • addTenWorkflow | wrun_01KNMH5VCWZ2YQDPP365WEZTM4
  • wellKnownAgentWorkflow (.well-known/agent) | wrun_01KNMH75H1GT8X09J9WS5F6FA6
  • should work with react rendering in step
  • promiseAllWorkflow | wrun_01KNMH63YAHQKDCZQT1EPYKGX8
  • promiseRaceWorkflow | wrun_01KNMH699ZAQD55FBQV3XNHM7X
  • promiseAnyWorkflow | wrun_01KNMH6C1XSP0EZ96TT0J5E8PF
  • importedStepOnlyWorkflow | wrun_01KNMH7GSJTNP0DX1PGSPFNTZZ
  • hookWorkflow | wrun_01KNMH6S06RS6VXGS41PF3GWSB
  • hookWorkflow is not resumable via public webhook endpoint | wrun_01KNMH76KMG0ZCB7ST88V553JE
  • webhookWorkflow | wrun_01KNMH7H30FD15T64RRS74743D
  • sleepingWorkflow | wrun_01KNMH7TG251JCYH1HS6DV9PKV
  • parallelSleepWorkflow | wrun_01KNMH87BSQPDNQBW8RR8GMHVR
  • nullByteWorkflow | wrun_01KNMH8B46P0EM2F1T1T2EQT07
  • workflowAndStepMetadataWorkflow | wrun_01KNMH8DKDK9H0CTSMSMJYV7J1
  • fetchWorkflow | wrun_01KNMHBA5EJNGZ9Y10R47QQ7TS
  • promiseRaceStressTestWorkflow | wrun_01KNMHBD0VT8JK2JD5N8JDTNTX
  • 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()
  • error handling not registered WorkflowNotRegisteredError fails the run when workflow does not exist
  • error handling not registered StepNotRegisteredError fails the step but workflow can catch it
  • error handling not registered StepNotRegisteredError fails the run when not caught in workflow
  • hookCleanupTestWorkflow - hook token reuse after workflow completion | wrun_01KNMHF707573TY2VWEG6X4DNH
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously | wrun_01KNMHFWK8Q44KY5E9X4R9ASHD
  • hookDisposeTestWorkflow - hook token reuse after explicit disposal while workflow still running | wrun_01KNMHGM9JGZWZSBXT32C90R37
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars) | wrun_01KNMHHA40QC8M5BFCX3WRN9DS
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument | wrun_01KNMHHKY5FCTHAD7DQ2RGH0AW
  • closureVariableWorkflow - nested step functions with closure variables | wrun_01KNMHHT09G8K4G7EG4F36D42G
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step | wrun_01KNMHHWDR6ZZGV5585HXJBY19
  • health check (queue-based) - workflow and step endpoints respond to health check messages
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly | wrun_01KNMHJBHXQHBXCB06Q1RQ364Z
  • Calculator.calculate - static workflow method using static step methods from another class | wrun_01KNMHJHYZ7X33V0S840FX5W9Q
  • AllInOneService.processNumber - static workflow method using sibling static step methods | wrun_01KNMHJRQ8QEZG1WYA9X4NE9G4
  • ChainableService.processWithThis - static step methods using this to reference the class | wrun_01KNMHJZB674R8TQ8TN8AA026X
  • thisSerializationWorkflow - step function invoked with .call() and .apply() | wrun_01KNMHK64J28XRFGM5X10GD015
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE | wrun_01KNMHKCJH3BSFD5V6A5DJSKV8
  • instanceMethodStepWorkflow - instance methods with "use step" directive | wrun_01KNMHKJXNGX0BC6AG4EP84PH0
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context | wrun_01KNMHKW4R2DSSHKGVJXT66ZGB
  • stepFunctionAsStartArgWorkflow - step function reference passed as start() argument | wrun_01KNMHM4QSV8SW6786SA9H6NFD
  • cancelRun - cancelling a running workflow | wrun_01KNMHMC10ES9NS6ZW9MAK03E4
  • cancelRun via CLI - cancelling a running workflow | wrun_01KNMHMMSK0AGPXGJR7JK82QDR
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router
  • hookWithSleepWorkflow - hook payloads delivered correctly with concurrent sleep | wrun_01KNMHMZYT36WW88RZPBQRKBH1
  • sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration | wrun_01KNMHNKEWEEQWTPPWGB7YNWSW
  • sleepWithSequentialStepsWorkflow - sequential steps work with concurrent sleep (control) | wrun_01KNMHNY2NHRBQ53J3TY57ZGSR
  • importMetaUrlWorkflow - import.meta.url is available in step bundles | wrun_01KNMHP4PAJEEA4DPSG64JC7M6
  • metadataFromHelperWorkflow - getWorkflowMetadata/getStepMetadata work from module-level helper (#1577) | wrun_01KNMHP6N2TBYR581JBV88ESXE
  • resilient start: addTenWorkflow completes when run_created returns 500 | wrun_01KNMHP8T5FNQQ8Z6MNZH87SNG
Details by Category
❌ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro7907
✅ example7907
✅ express7907
✅ fastify7907
❌ hono7817
✅ nextjs-turbopack8402
✅ nextjs-webpack8402
✅ nitro7907
✅ nuxt7907
✅ sveltekit7907
✅ vite7907
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable72014
✅ express-stable72014
✅ fastify-stable72014
✅ hono-stable72014
✅ nextjs-turbopack-canary61025
✅ nextjs-turbopack-stable7808
✅ nextjs-webpack-canary61025
✅ nextjs-webpack-stable7808
✅ nitro-stable72014
✅ nuxt-stable72014
✅ sveltekit-stable72014
✅ vite-stable72014
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable72014
✅ express-stable72014
✅ fastify-stable72014
✅ hono-stable72014
✅ nextjs-turbopack-canary61025
✅ nextjs-turbopack-stable7808
✅ nextjs-webpack-canary61025
✅ nextjs-webpack-stable7808
✅ nitro-stable72014
✅ nuxt-stable72014
✅ sveltekit-stable72014
✅ vite-stable72014
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable72014
✅ express-stable72014
✅ fastify-stable72014
✅ hono-stable72014
✅ nextjs-turbopack-canary61025
✅ nextjs-turbopack-stable7808
✅ nextjs-webpack-canary61025
✅ nextjs-webpack-stable7808
✅ nitro-stable72014
✅ nuxt-stable72014
✅ sveltekit-stable72014
✅ vite-stable72014
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack7808
❌ 🌍 Community Worlds
AppPassedFailedSkipped
❌ mongodb-dev410
❌ redis-dev410
❌ turso-dev410
❌ turso4578
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable72014
✅ e2e-local-postgres-nest-stable72014
✅ e2e-local-prod-nest-stable72014
📋 View full workflow run
❌ Some E2E test jobs failed:
  • Vercel Prod: failure
  • Local Dev: success
  • Local Prod: success
  • Local Postgres: success
  • Windows: success
Check the workflow run for details.
@VaguelySerious@claude
Include workflowCoreVersion in health check responses
51fb2ab
Both the HTTP (?__health) and queue-based health check endpoints
now return the @workflow/core package version, allowing observability
tools to identify exactly which SDK version a deployment is running.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious
VaguelySerious
merged commit a6bcea9
into
mainApr 7, 2026

92 of 99 checks passed

@VaguelySerious
VaguelySerious
deleted the

peter/cli-specversion-probe

branch
April 7, 2026 18:03
@ghostghost
mentioned this pull request
Apr 7, 2026
 Merged

VaguelySerious added a commit
that referenced
this pull request
Apr 7, 2026
@VaguelySerious
[cli] [core] Probe deployment specVersion before CLI start (#1629)
f0d6a85
@TooTallNateTooTallNate
mentioned this pull request
Apr 8, 2026
 Merged

7 tasks
@VaguelySeriousVaguelySerious
mentioned this pull request
Apr 16, 2026
 Closed

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

Reviewers

@TooTallNateTooTallNateTooTallNate approved these changes

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@VaguelySerious@TooTallNate

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
[cli] [core] Probe deployment specVersion before CLI start - #1629
Merged
VaguelySerious merged 17 commits into
mainfrom 
peter/cli-specversion-probe
Apr 7, 2026
Merged
[cli] [core] Probe deployment specVersion before CLI start#1629
VaguelySerious merged 17 commits into
mainfrom 
peter/cli-specversion-probe
Conversation
@VaguelySerious
@VaguelySeriousVaguelySerious
commented
Apr 7, 2026

Copy link


Copy Markdown

Member
Summary
Based on #1627. CLI start command now probes the target deployment's specVersion via health check before calling start(), ensuring the correct queue transport is used.
  • Health check always uses JSON transport (specVersion: SPEC_VERSION_LEGACY) so the probe works against both old and new deployments
  • Adds deploymentId option to HealthCheckOptions for targeted health checks
  • Falls back to the existing run's specVersion if health check fails (e.g. old deployment without health check support)
Other paths that call start() without knowing specVersion
Call siteKnows specVersion?Notes
CLI startNow probedThis PR
recreateRunFromExisting (web dashboard replay)YesUses run.specVersion from original run
User code (import { start } from 'workflow')N/ARuns ON the deployment, so SPEC_VERSION_CURRENT is correct
Testing server (world-testing)NoNot production-relevant
Test plan
  • packages/core unit tests pass (580/580)
  •  Full build passes
  •  e2e: CLI start against old deployment uses JSON transport
  •  e2e: CLI start against new deployment uses CBOR transport
  •  e2e: CLI start with health check timeout falls back to run specVersion
🤖 Generated with Claude Code
VaguelySeriousand others
added 13 commits
April 6, 2026 15:56
@VaguelySerious@claude
fix: gate queue transport format on specVersion for CBOR compat
8399d51
Bump SPEC_VERSION_CURRENT to 3 and fix isLegacySpecVersion to check
against SPEC_VERSION_LEGACY instead of SPEC_VERSION_CURRENT, preventing
v2 runs from being incorrectly treated as legacy when the version bumps.
Add JsonTransport and DualTransport to world-vercel queue: the handler
uses DualTransport (CBOR-first, JSON fallback) to accept messages from
both old and new deployments, while the send path selects CBOR or JSON
based on the target run's specVersion. Pass specVersion through queue
opts from start(), reenqueueRun(), wakeUpRun(), and resumeHook().
Only include runInput in the queue payload for specVersion >= 3, creating
clean separation between old and new behavior.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
[core] [world] Gate CBOR queue transport on specVersion
b6b6dcf
Bump specVersion to 3. Use JSON transport for queue messages targeting
older deployments (specVersion < 3), CBOR for new ones. Handler uses
dual transport that deserializes both formats, so new deployments can
receive messages from old and new senders.
Fixes replay/reenqueue from the dashboard to older deployments that
expect JSON queue messages.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Use named spec version constants for feature boundaries
dd2699b
Replace SPEC_VERSION_CURRENT comparisons with named constants
(SPEC_VERSION_SUPPORTS_CBOR_QUEUE_TRANSPORT, SPEC_VERSION_SUPPORTS_EVENT_SOURCING)
so future SPEC_VERSION_CURRENT bumps don't shift existing feature gates.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Update world-postgres test to use SPEC_VERSION_CURRENT
ddc8c31
Replace hardcoded specVersion: 2 with SPEC_VERSION_CURRENT so
the test tracks spec version bumps.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Include specVersion in health check responses
cf3dd88
Both the HTTP health check endpoint (?__health) and the queue-based
health check stream now return specVersion, allowing observability
tools to query deployment capabilities.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious
Merge branch 'main' into peter/cbor-transport-compat
50407fe
@VaguelySerious
fix health check test
330d70d
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@vercel@VaguelySerious
Fix: Health check e2e test assertions are missing the endpoint fiel…
82dcbe2
…d, causing `toEqual` to fail due to exact equality mismatch.
This commit fixes the issue reported at packages/core/e2e/e2e.test.ts:1550
**Bug explanation:**
The `withHealthCheck` handler in `packages/core/src/runtime/helpers.ts` returns a JSON response with three fields: `{ healthy: true, endpoint: url.pathname, specVersion: SPEC_VERSION_CURRENT }`. However, the HTTP-based health check e2e test in `packages/core/e2e/e2e.test.ts` (lines 1549-1553 and 1567-1571) uses `toEqual` to assert against objects that only have two fields: `{ healthy: true, specVersion: SPEC_VERSION_CURRENT }`, missing the `endpoint` field.
In Vitest, `toEqual` performs exact deep equality checking. When the actual response object contains `{ healthy: true, endpoint: "/.well-known/workflow/v1/flow", specVersion: "..." }` but the expected object only has `{ healthy: true, specVersion: "..." }`, the assertion fails because the actual object has an extra `endpoint` property not present in the expected object.
This affects both the flow endpoint health check assertion and the step endpoint health check assertion.
**Fix explanation:**
Added the missing `endpoint` field to both `toEqual` assertions:
- For the flow endpoint: `endpoint: '/.well-known/workflow/v1/flow'` (the pathname portion of `/.well-known/workflow/v1/flow?__health`)
- For the step endpoint: `endpoint: '/.well-known/workflow/v1/step'` (the pathname portion of `/.well-known/workflow/v1/step?__health`)
These values match what `url.pathname` returns in the handler (the `?__health` query parameter is not part of the pathname). This makes the test assertions exactly match the actual response structure from the handler.
Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Co-authored-by: VaguelySerious <mittgfu@gmail.com>
@VaguelySerious
fix
ce9ba33
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious
fix
57cb399
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious@claude
Propagate specVersion through queue-based health check result
419de89
Update HealthCheckResult to include specVersion and parse it from the
stream response, so observability tools can query deployment capabilities
through both the HTTP and queue-based health check paths.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Fix TypeScript cast in parseHealthCheckResponse
ff8a79c
Use Record<string, unknown> instead of narrower casts that tsc
rejects as insufficient overlap.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
[cli] [core] Probe deployment specVersion before CLI start
7b42568
CLI start command now queries the deployment's health check endpoint
to determine its specVersion before calling start(). This ensures the
correct queue transport is used (JSON for old deployments, CBOR for
new). Falls back to the run's specVersion if health check fails.
Health check always uses JSON transport (specVersion: SPEC_VERSION_LEGACY)
so the probe works against both old and new deployments. Also adds
deploymentId option to HealthCheckOptions for targeted health checks.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@vercel
vercelBot
commented
Apr 7, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
The latest updates on your projects. Learn more about Vercel for GitHub.
ProjectDeploymentActionsUpdated (UTC)
example-nextjs-workflow-turbopackReadyReadyPreview, CommentApr 7, 2026 5:52pm
example-nextjs-workflow-webpackReadyReadyPreview, CommentApr 7, 2026 5:52pm
example-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-astro-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-express-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-fastify-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-hono-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-nitro-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-nuxt-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-sveltekit-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-vite-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workflow-docsReadyReadyPreview, Comment, Open in v0Apr 7, 2026 5:52pm
workflow-swc-playgroundReadyReadyPreview, CommentApr 7, 2026 5:52pm
@VaguelySerious
VaguelySerious
requested a review
from a team
as a code ownerApril 7, 2026 00:22
@changeset-bot
changeset-botBot
commented
Apr 7, 2026•

edited

Loading

Copy link


Copy Markdown

🦋 Changeset detected
Latest commit: 51fb2ab
The changes in this PR will be included in the next version bump.
This PR includes changesets to release 16 packages
NameType
@workflow/corePatch
@workflow/cliPatch
@workflow/buildersPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/vitestPatch
@workflow/web-sharedPatch
workflowPatch
@workflow/world-testingPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch
@workflow/aiPatch
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
github-actionsBot
commented
Apr 7, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
🧪 E2E Test Results
❌ Some tests failed
Summary
PassedFailedSkippedTotal
❌ ▲ Vercel Production878167946
✅ 💻 Local Development85401781032
✅ 📦 Local Production85401781032
✅ 🐘 Local Postgres85401781032
✅ 🪟 Windows780886
❌ 🌍 Community Worlds1660884
✅ 📋 Other216042258
Total3750616594470
❌ Failed Tests
▲ Vercel Production (1 failed)
hono (1 failed):
🌍 Community Worlds (60 failed)
mongodb-dev (1 failed):
  • dev e2e should rebuild on imported step dependency change
redis-dev (1 failed):
  • dev e2e should rebuild on imported step dependency change
turso-dev (1 failed):
  • dev e2e should rebuild on imported step dependency change
turso (57 failed):
  • addTenWorkflow | wrun_01KNMH5VCWZ2YQDPP365WEZTM4
  • addTenWorkflow | wrun_01KNMH5VCWZ2YQDPP365WEZTM4
  • wellKnownAgentWorkflow (.well-known/agent) | wrun_01KNMH75H1GT8X09J9WS5F6FA6
  • should work with react rendering in step
  • promiseAllWorkflow | wrun_01KNMH63YAHQKDCZQT1EPYKGX8
  • promiseRaceWorkflow | wrun_01KNMH699ZAQD55FBQV3XNHM7X
  • promiseAnyWorkflow | wrun_01KNMH6C1XSP0EZ96TT0J5E8PF
  • importedStepOnlyWorkflow | wrun_01KNMH7GSJTNP0DX1PGSPFNTZZ
  • hookWorkflow | wrun_01KNMH6S06RS6VXGS41PF3GWSB
  • hookWorkflow is not resumable via public webhook endpoint | wrun_01KNMH76KMG0ZCB7ST88V553JE
  • webhookWorkflow | wrun_01KNMH7H30FD15T64RRS74743D
  • sleepingWorkflow | wrun_01KNMH7TG251JCYH1HS6DV9PKV
  • parallelSleepWorkflow | wrun_01KNMH87BSQPDNQBW8RR8GMHVR
  • nullByteWorkflow | wrun_01KNMH8B46P0EM2F1T1T2EQT07
  • workflowAndStepMetadataWorkflow | wrun_01KNMH8DKDK9H0CTSMSMJYV7J1
  • fetchWorkflow | wrun_01KNMHBA5EJNGZ9Y10R47QQ7TS
  • promiseRaceStressTestWorkflow | wrun_01KNMHBD0VT8JK2JD5N8JDTNTX
  • 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()
  • error handling not registered WorkflowNotRegisteredError fails the run when workflow does not exist
  • error handling not registered StepNotRegisteredError fails the step but workflow can catch it
  • error handling not registered StepNotRegisteredError fails the run when not caught in workflow
  • hookCleanupTestWorkflow - hook token reuse after workflow completion | wrun_01KNMHF707573TY2VWEG6X4DNH
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously | wrun_01KNMHFWK8Q44KY5E9X4R9ASHD
  • hookDisposeTestWorkflow - hook token reuse after explicit disposal while workflow still running | wrun_01KNMHGM9JGZWZSBXT32C90R37
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars) | wrun_01KNMHHA40QC8M5BFCX3WRN9DS
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument | wrun_01KNMHHKY5FCTHAD7DQ2RGH0AW
  • closureVariableWorkflow - nested step functions with closure variables | wrun_01KNMHHT09G8K4G7EG4F36D42G
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step | wrun_01KNMHHWDR6ZZGV5585HXJBY19
  • health check (queue-based) - workflow and step endpoints respond to health check messages
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly | wrun_01KNMHJBHXQHBXCB06Q1RQ364Z
  • Calculator.calculate - static workflow method using static step methods from another class | wrun_01KNMHJHYZ7X33V0S840FX5W9Q
  • AllInOneService.processNumber - static workflow method using sibling static step methods | wrun_01KNMHJRQ8QEZG1WYA9X4NE9G4
  • ChainableService.processWithThis - static step methods using this to reference the class | wrun_01KNMHJZB674R8TQ8TN8AA026X
  • thisSerializationWorkflow - step function invoked with .call() and .apply() | wrun_01KNMHK64J28XRFGM5X10GD015
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE | wrun_01KNMHKCJH3BSFD5V6A5DJSKV8
  • instanceMethodStepWorkflow - instance methods with "use step" directive | wrun_01KNMHKJXNGX0BC6AG4EP84PH0
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context | wrun_01KNMHKW4R2DSSHKGVJXT66ZGB
  • stepFunctionAsStartArgWorkflow - step function reference passed as start() argument | wrun_01KNMHM4QSV8SW6786SA9H6NFD
  • cancelRun - cancelling a running workflow | wrun_01KNMHMC10ES9NS6ZW9MAK03E4
  • cancelRun via CLI - cancelling a running workflow | wrun_01KNMHMMSK0AGPXGJR7JK82QDR
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router
  • hookWithSleepWorkflow - hook payloads delivered correctly with concurrent sleep | wrun_01KNMHMZYT36WW88RZPBQRKBH1
  • sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration | wrun_01KNMHNKEWEEQWTPPWGB7YNWSW
  • sleepWithSequentialStepsWorkflow - sequential steps work with concurrent sleep (control) | wrun_01KNMHNY2NHRBQ53J3TY57ZGSR
  • importMetaUrlWorkflow - import.meta.url is available in step bundles | wrun_01KNMHP4PAJEEA4DPSG64JC7M6
  • metadataFromHelperWorkflow - getWorkflowMetadata/getStepMetadata work from module-level helper (#1577) | wrun_01KNMHP6N2TBYR581JBV88ESXE
  • resilient start: addTenWorkflow completes when run_created returns 500 | wrun_01KNMHP8T5FNQQ8Z6MNZH87SNG
Details by Category
❌ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro7907
✅ example7907
✅ express7907
✅ fastify7907
❌ hono7817
✅ nextjs-turbopack8402
✅ nextjs-webpack8402
✅ nitro7907
✅ nuxt7907
✅ sveltekit7907
✅ vite7907
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable72014
✅ express-stable72014
✅ fastify-stable72014
✅ hono-stable72014
✅ nextjs-turbopack-canary61025
✅ nextjs-turbopack-stable7808
✅ nextjs-webpack-canary61025
✅ nextjs-webpack-stable7808
✅ nitro-stable72014
✅ nuxt-stable72014
✅ sveltekit-stable72014
✅ vite-stable72014
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable72014
✅ express-stable72014
✅ fastify-stable72014
✅ hono-stable72014
✅ nextjs-turbopack-canary61025
✅ nextjs-turbopack-stable7808
✅ nextjs-webpack-canary61025
✅ nextjs-webpack-stable7808
✅ nitro-stable72014
✅ nuxt-stable72014
✅ sveltekit-stable72014
✅ vite-stable72014
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable72014
✅ express-stable72014
✅ fastify-stable72014
✅ hono-stable72014
✅ nextjs-turbopack-canary61025
✅ nextjs-turbopack-stable7808
✅ nextjs-webpack-canary61025
✅ nextjs-webpack-stable7808
✅ nitro-stable72014
✅ nuxt-stable72014
✅ sveltekit-stable72014
✅ vite-stable72014
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack7808
❌ 🌍 Community Worlds
AppPassedFailedSkipped
❌ mongodb-dev410
❌ redis-dev410
❌ turso-dev410
❌ turso4578
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable72014
✅ e2e-local-postgres-nest-stable72014
✅ e2e-local-prod-nest-stable72014
📋 View full workflow run
❌ Some E2E test jobs failed:
  • Vercel Prod: failure
  • Local Dev: success
  • Local Prod: success
  • Local Postgres: success
  • Windows: success
Check the workflow run for details.
@VaguelySerious@claude
Include workflowCoreVersion in health check responses
51fb2ab
Both the HTTP (?__health) and queue-based health check endpoints
now return the @workflow/core package version, allowing observability
tools to identify exactly which SDK version a deployment is running.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious
VaguelySerious
merged commit a6bcea9
into
mainApr 7, 2026

92 of 99 checks passed

@VaguelySerious
VaguelySerious
deleted the

peter/cli-specversion-probe

branch
April 7, 2026 18:03
@ghostghost
mentioned this pull request
Apr 7, 2026
 Merged

VaguelySerious added a commit
that referenced
this pull request
Apr 7, 2026
@VaguelySerious
[cli] [core] Probe deployment specVersion before CLI start (#1629)
f0d6a85
@TooTallNateTooTallNate
mentioned this pull request
Apr 8, 2026
 Merged

7 tasks
@VaguelySeriousVaguelySerious
mentioned this pull request
Apr 16, 2026
 Closed

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

Reviewers

@TooTallNateTooTallNateTooTallNate approved these changes

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@VaguelySerious@TooTallNate

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
[cli] [core] Probe deployment specVersion before CLI start - #1629
Merged
VaguelySerious merged 17 commits into
mainfrom 
peter/cli-specversion-probe
Apr 7, 2026
Merged
[cli] [core] Probe deployment specVersion before CLI start#1629
VaguelySerious merged 17 commits into
mainfrom 
peter/cli-specversion-probe
Conversation
@VaguelySerious
@VaguelySeriousVaguelySerious
commented
Apr 7, 2026

Copy link


Copy Markdown

Member
Summary
Based on #1627. CLI start command now probes the target deployment's specVersion via health check before calling start(), ensuring the correct queue transport is used.
  • Health check always uses JSON transport (specVersion: SPEC_VERSION_LEGACY) so the probe works against both old and new deployments
  • Adds deploymentId option to HealthCheckOptions for targeted health checks
  • Falls back to the existing run's specVersion if health check fails (e.g. old deployment without health check support)
Other paths that call start() without knowing specVersion
Call siteKnows specVersion?Notes
CLI startNow probedThis PR
recreateRunFromExisting (web dashboard replay)YesUses run.specVersion from original run
User code (import { start } from 'workflow')N/ARuns ON the deployment, so SPEC_VERSION_CURRENT is correct
Testing server (world-testing)NoNot production-relevant
Test plan
  • packages/core unit tests pass (580/580)
  •  Full build passes
  •  e2e: CLI start against old deployment uses JSON transport
  •  e2e: CLI start against new deployment uses CBOR transport
  •  e2e: CLI start with health check timeout falls back to run specVersion
🤖 Generated with Claude Code
VaguelySeriousand others
added 13 commits
April 6, 2026 15:56
@VaguelySerious@claude
fix: gate queue transport format on specVersion for CBOR compat
8399d51
Bump SPEC_VERSION_CURRENT to 3 and fix isLegacySpecVersion to check
against SPEC_VERSION_LEGACY instead of SPEC_VERSION_CURRENT, preventing
v2 runs from being incorrectly treated as legacy when the version bumps.
Add JsonTransport and DualTransport to world-vercel queue: the handler
uses DualTransport (CBOR-first, JSON fallback) to accept messages from
both old and new deployments, while the send path selects CBOR or JSON
based on the target run's specVersion. Pass specVersion through queue
opts from start(), reenqueueRun(), wakeUpRun(), and resumeHook().
Only include runInput in the queue payload for specVersion >= 3, creating
clean separation between old and new behavior.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
[core] [world] Gate CBOR queue transport on specVersion
b6b6dcf
Bump specVersion to 3. Use JSON transport for queue messages targeting
older deployments (specVersion < 3), CBOR for new ones. Handler uses
dual transport that deserializes both formats, so new deployments can
receive messages from old and new senders.
Fixes replay/reenqueue from the dashboard to older deployments that
expect JSON queue messages.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Use named spec version constants for feature boundaries
dd2699b
Replace SPEC_VERSION_CURRENT comparisons with named constants
(SPEC_VERSION_SUPPORTS_CBOR_QUEUE_TRANSPORT, SPEC_VERSION_SUPPORTS_EVENT_SOURCING)
so future SPEC_VERSION_CURRENT bumps don't shift existing feature gates.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Update world-postgres test to use SPEC_VERSION_CURRENT
ddc8c31
Replace hardcoded specVersion: 2 with SPEC_VERSION_CURRENT so
the test tracks spec version bumps.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Include specVersion in health check responses
cf3dd88
Both the HTTP health check endpoint (?__health) and the queue-based
health check stream now return specVersion, allowing observability
tools to query deployment capabilities.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious
Merge branch 'main' into peter/cbor-transport-compat
50407fe
@VaguelySerious
fix health check test
330d70d
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@vercel@VaguelySerious
Fix: Health check e2e test assertions are missing the endpoint fiel…
82dcbe2
…d, causing `toEqual` to fail due to exact equality mismatch.
This commit fixes the issue reported at packages/core/e2e/e2e.test.ts:1550
**Bug explanation:**
The `withHealthCheck` handler in `packages/core/src/runtime/helpers.ts` returns a JSON response with three fields: `{ healthy: true, endpoint: url.pathname, specVersion: SPEC_VERSION_CURRENT }`. However, the HTTP-based health check e2e test in `packages/core/e2e/e2e.test.ts` (lines 1549-1553 and 1567-1571) uses `toEqual` to assert against objects that only have two fields: `{ healthy: true, specVersion: SPEC_VERSION_CURRENT }`, missing the `endpoint` field.
In Vitest, `toEqual` performs exact deep equality checking. When the actual response object contains `{ healthy: true, endpoint: "/.well-known/workflow/v1/flow", specVersion: "..." }` but the expected object only has `{ healthy: true, specVersion: "..." }`, the assertion fails because the actual object has an extra `endpoint` property not present in the expected object.
This affects both the flow endpoint health check assertion and the step endpoint health check assertion.
**Fix explanation:**
Added the missing `endpoint` field to both `toEqual` assertions:
- For the flow endpoint: `endpoint: '/.well-known/workflow/v1/flow'` (the pathname portion of `/.well-known/workflow/v1/flow?__health`)
- For the step endpoint: `endpoint: '/.well-known/workflow/v1/step'` (the pathname portion of `/.well-known/workflow/v1/step?__health`)
These values match what `url.pathname` returns in the handler (the `?__health` query parameter is not part of the pathname). This makes the test assertions exactly match the actual response structure from the handler.
Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Co-authored-by: VaguelySerious <mittgfu@gmail.com>
@VaguelySerious
fix
ce9ba33
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious
fix
57cb399
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious@claude
Propagate specVersion through queue-based health check result
419de89
Update HealthCheckResult to include specVersion and parse it from the
stream response, so observability tools can query deployment capabilities
through both the HTTP and queue-based health check paths.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Fix TypeScript cast in parseHealthCheckResponse
ff8a79c
Use Record<string, unknown> instead of narrower casts that tsc
rejects as insufficient overlap.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
[cli] [core] Probe deployment specVersion before CLI start
7b42568
CLI start command now queries the deployment's health check endpoint
to determine its specVersion before calling start(). This ensures the
correct queue transport is used (JSON for old deployments, CBOR for
new). Falls back to the run's specVersion if health check fails.
Health check always uses JSON transport (specVersion: SPEC_VERSION_LEGACY)
so the probe works against both old and new deployments. Also adds
deploymentId option to HealthCheckOptions for targeted health checks.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@vercel
vercelBot
commented
Apr 7, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
The latest updates on your projects. Learn more about Vercel for GitHub.
ProjectDeploymentActionsUpdated (UTC)
example-nextjs-workflow-turbopackReadyReadyPreview, CommentApr 7, 2026 5:52pm
example-nextjs-workflow-webpackReadyReadyPreview, CommentApr 7, 2026 5:52pm
example-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-astro-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-express-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-fastify-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-hono-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-nitro-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-nuxt-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-sveltekit-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-vite-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workflow-docsReadyReadyPreview, Comment, Open in v0Apr 7, 2026 5:52pm
workflow-swc-playgroundReadyReadyPreview, CommentApr 7, 2026 5:52pm
@VaguelySerious
VaguelySerious
requested a review
from a team
as a code ownerApril 7, 2026 00:22
@changeset-bot
changeset-botBot
commented
Apr 7, 2026•

edited

Loading

Copy link


Copy Markdown

🦋 Changeset detected
Latest commit: 51fb2ab
The changes in this PR will be included in the next version bump.
This PR includes changesets to release 16 packages
NameType
@workflow/corePatch
@workflow/cliPatch
@workflow/buildersPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/vitestPatch
@workflow/web-sharedPatch
workflowPatch
@workflow/world-testingPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch
@workflow/aiPatch
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
github-actionsBot
commented
Apr 7, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
🧪 E2E Test Results
❌ Some tests failed
Summary
PassedFailedSkippedTotal
❌ ▲ Vercel Production878167946
✅ 💻 Local Development85401781032
✅ 📦 Local Production85401781032
✅ 🐘 Local Postgres85401781032
✅ 🪟 Windows780886
❌ 🌍 Community Worlds1660884
✅ 📋 Other216042258
Total3750616594470
❌ Failed Tests
▲ Vercel Production (1 failed)
hono (1 failed):
🌍 Community Worlds (60 failed)
mongodb-dev (1 failed):
  • dev e2e should rebuild on imported step dependency change
redis-dev (1 failed):
  • dev e2e should rebuild on imported step dependency change
turso-dev (1 failed):
  • dev e2e should rebuild on imported step dependency change
turso (57 failed):
  • addTenWorkflow | wrun_01KNMH5VCWZ2YQDPP365WEZTM4
  • addTenWorkflow | wrun_01KNMH5VCWZ2YQDPP365WEZTM4
  • wellKnownAgentWorkflow (.well-known/agent) | wrun_01KNMH75H1GT8X09J9WS5F6FA6
  • should work with react rendering in step
  • promiseAllWorkflow | wrun_01KNMH63YAHQKDCZQT1EPYKGX8
  • promiseRaceWorkflow | wrun_01KNMH699ZAQD55FBQV3XNHM7X
  • promiseAnyWorkflow | wrun_01KNMH6C1XSP0EZ96TT0J5E8PF
  • importedStepOnlyWorkflow | wrun_01KNMH7GSJTNP0DX1PGSPFNTZZ
  • hookWorkflow | wrun_01KNMH6S06RS6VXGS41PF3GWSB
  • hookWorkflow is not resumable via public webhook endpoint | wrun_01KNMH76KMG0ZCB7ST88V553JE
  • webhookWorkflow | wrun_01KNMH7H30FD15T64RRS74743D
  • sleepingWorkflow | wrun_01KNMH7TG251JCYH1HS6DV9PKV
  • parallelSleepWorkflow | wrun_01KNMH87BSQPDNQBW8RR8GMHVR
  • nullByteWorkflow | wrun_01KNMH8B46P0EM2F1T1T2EQT07
  • workflowAndStepMetadataWorkflow | wrun_01KNMH8DKDK9H0CTSMSMJYV7J1
  • fetchWorkflow | wrun_01KNMHBA5EJNGZ9Y10R47QQ7TS
  • promiseRaceStressTestWorkflow | wrun_01KNMHBD0VT8JK2JD5N8JDTNTX
  • 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()
  • error handling not registered WorkflowNotRegisteredError fails the run when workflow does not exist
  • error handling not registered StepNotRegisteredError fails the step but workflow can catch it
  • error handling not registered StepNotRegisteredError fails the run when not caught in workflow
  • hookCleanupTestWorkflow - hook token reuse after workflow completion | wrun_01KNMHF707573TY2VWEG6X4DNH
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously | wrun_01KNMHFWK8Q44KY5E9X4R9ASHD
  • hookDisposeTestWorkflow - hook token reuse after explicit disposal while workflow still running | wrun_01KNMHGM9JGZWZSBXT32C90R37
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars) | wrun_01KNMHHA40QC8M5BFCX3WRN9DS
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument | wrun_01KNMHHKY5FCTHAD7DQ2RGH0AW
  • closureVariableWorkflow - nested step functions with closure variables | wrun_01KNMHHT09G8K4G7EG4F36D42G
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step | wrun_01KNMHHWDR6ZZGV5585HXJBY19
  • health check (queue-based) - workflow and step endpoints respond to health check messages
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly | wrun_01KNMHJBHXQHBXCB06Q1RQ364Z
  • Calculator.calculate - static workflow method using static step methods from another class | wrun_01KNMHJHYZ7X33V0S840FX5W9Q
  • AllInOneService.processNumber - static workflow method using sibling static step methods | wrun_01KNMHJRQ8QEZG1WYA9X4NE9G4
  • ChainableService.processWithThis - static step methods using this to reference the class | wrun_01KNMHJZB674R8TQ8TN8AA026X
  • thisSerializationWorkflow - step function invoked with .call() and .apply() | wrun_01KNMHK64J28XRFGM5X10GD015
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE | wrun_01KNMHKCJH3BSFD5V6A5DJSKV8
  • instanceMethodStepWorkflow - instance methods with "use step" directive | wrun_01KNMHKJXNGX0BC6AG4EP84PH0
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context | wrun_01KNMHKW4R2DSSHKGVJXT66ZGB
  • stepFunctionAsStartArgWorkflow - step function reference passed as start() argument | wrun_01KNMHM4QSV8SW6786SA9H6NFD
  • cancelRun - cancelling a running workflow | wrun_01KNMHMC10ES9NS6ZW9MAK03E4
  • cancelRun via CLI - cancelling a running workflow | wrun_01KNMHMMSK0AGPXGJR7JK82QDR
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router
  • hookWithSleepWorkflow - hook payloads delivered correctly with concurrent sleep | wrun_01KNMHMZYT36WW88RZPBQRKBH1
  • sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration | wrun_01KNMHNKEWEEQWTPPWGB7YNWSW
  • sleepWithSequentialStepsWorkflow - sequential steps work with concurrent sleep (control) | wrun_01KNMHNY2NHRBQ53J3TY57ZGSR
  • importMetaUrlWorkflow - import.meta.url is available in step bundles | wrun_01KNMHP4PAJEEA4DPSG64JC7M6
  • metadataFromHelperWorkflow - getWorkflowMetadata/getStepMetadata work from module-level helper (#1577) | wrun_01KNMHP6N2TBYR581JBV88ESXE
  • resilient start: addTenWorkflow completes when run_created returns 500 | wrun_01KNMHP8T5FNQQ8Z6MNZH87SNG
Details by Category
❌ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro7907
✅ example7907
✅ express7907
✅ fastify7907
❌ hono7817
✅ nextjs-turbopack8402
✅ nextjs-webpack8402
✅ nitro7907
✅ nuxt7907
✅ sveltekit7907
✅ vite7907
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable72014
✅ express-stable72014
✅ fastify-stable72014
✅ hono-stable72014
✅ nextjs-turbopack-canary61025
✅ nextjs-turbopack-stable7808
✅ nextjs-webpack-canary61025
✅ nextjs-webpack-stable7808
✅ nitro-stable72014
✅ nuxt-stable72014
✅ sveltekit-stable72014
✅ vite-stable72014
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable72014
✅ express-stable72014
✅ fastify-stable72014
✅ hono-stable72014
✅ nextjs-turbopack-canary61025
✅ nextjs-turbopack-stable7808
✅ nextjs-webpack-canary61025
✅ nextjs-webpack-stable7808
✅ nitro-stable72014
✅ nuxt-stable72014
✅ sveltekit-stable72014
✅ vite-stable72014
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable72014
✅ express-stable72014
✅ fastify-stable72014
✅ hono-stable72014
✅ nextjs-turbopack-canary61025
✅ nextjs-turbopack-stable7808
✅ nextjs-webpack-canary61025
✅ nextjs-webpack-stable7808
✅ nitro-stable72014
✅ nuxt-stable72014
✅ sveltekit-stable72014
✅ vite-stable72014
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack7808
❌ 🌍 Community Worlds
AppPassedFailedSkipped
❌ mongodb-dev410
❌ redis-dev410
❌ turso-dev410
❌ turso4578
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable72014
✅ e2e-local-postgres-nest-stable72014
✅ e2e-local-prod-nest-stable72014
📋 View full workflow run
❌ Some E2E test jobs failed:
  • Vercel Prod: failure
  • Local Dev: success
  • Local Prod: success
  • Local Postgres: success
  • Windows: success
Check the workflow run for details.
@VaguelySerious@claude
Include workflowCoreVersion in health check responses
51fb2ab
Both the HTTP (?__health) and queue-based health check endpoints
now return the @workflow/core package version, allowing observability
tools to identify exactly which SDK version a deployment is running.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious
VaguelySerious
merged commit a6bcea9
into
mainApr 7, 2026

92 of 99 checks passed

@VaguelySerious
VaguelySerious
deleted the

peter/cli-specversion-probe

branch
April 7, 2026 18:03
@ghostghost
mentioned this pull request
Apr 7, 2026
 Merged

VaguelySerious added a commit
that referenced
this pull request
Apr 7, 2026
@VaguelySerious
[cli] [core] Probe deployment specVersion before CLI start (#1629)
f0d6a85
@TooTallNateTooTallNate
mentioned this pull request
Apr 8, 2026
 Merged

7 tasks
@VaguelySeriousVaguelySerious
mentioned this pull request
Apr 16, 2026
 Closed

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

Reviewers

@TooTallNateTooTallNateTooTallNate approved these changes

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@VaguelySerious@TooTallNate

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
[cli] [core] Probe deployment specVersion before CLI start - #1629
Merged
VaguelySerious merged 17 commits into
mainfrom 
peter/cli-specversion-probe
Apr 7, 2026
Merged
[cli] [core] Probe deployment specVersion before CLI start#1629
VaguelySerious merged 17 commits into
mainfrom 
peter/cli-specversion-probe
Conversation
@VaguelySerious
@VaguelySeriousVaguelySerious
commented
Apr 7, 2026

Copy link


Copy Markdown

Member
Summary
Based on #1627. CLI start command now probes the target deployment's specVersion via health check before calling start(), ensuring the correct queue transport is used.
  • Health check always uses JSON transport (specVersion: SPEC_VERSION_LEGACY) so the probe works against both old and new deployments
  • Adds deploymentId option to HealthCheckOptions for targeted health checks
  • Falls back to the existing run's specVersion if health check fails (e.g. old deployment without health check support)
Other paths that call start() without knowing specVersion
Call siteKnows specVersion?Notes
CLI startNow probedThis PR
recreateRunFromExisting (web dashboard replay)YesUses run.specVersion from original run
User code (import { start } from 'workflow')N/ARuns ON the deployment, so SPEC_VERSION_CURRENT is correct
Testing server (world-testing)NoNot production-relevant
Test plan
  • packages/core unit tests pass (580/580)
  •  Full build passes
  •  e2e: CLI start against old deployment uses JSON transport
  •  e2e: CLI start against new deployment uses CBOR transport
  •  e2e: CLI start with health check timeout falls back to run specVersion
🤖 Generated with Claude Code
VaguelySeriousand others
added 13 commits
April 6, 2026 15:56
@VaguelySerious@claude
fix: gate queue transport format on specVersion for CBOR compat
8399d51
Bump SPEC_VERSION_CURRENT to 3 and fix isLegacySpecVersion to check
against SPEC_VERSION_LEGACY instead of SPEC_VERSION_CURRENT, preventing
v2 runs from being incorrectly treated as legacy when the version bumps.
Add JsonTransport and DualTransport to world-vercel queue: the handler
uses DualTransport (CBOR-first, JSON fallback) to accept messages from
both old and new deployments, while the send path selects CBOR or JSON
based on the target run's specVersion. Pass specVersion through queue
opts from start(), reenqueueRun(), wakeUpRun(), and resumeHook().
Only include runInput in the queue payload for specVersion >= 3, creating
clean separation between old and new behavior.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
[core] [world] Gate CBOR queue transport on specVersion
b6b6dcf
Bump specVersion to 3. Use JSON transport for queue messages targeting
older deployments (specVersion < 3), CBOR for new ones. Handler uses
dual transport that deserializes both formats, so new deployments can
receive messages from old and new senders.
Fixes replay/reenqueue from the dashboard to older deployments that
expect JSON queue messages.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Use named spec version constants for feature boundaries
dd2699b
Replace SPEC_VERSION_CURRENT comparisons with named constants
(SPEC_VERSION_SUPPORTS_CBOR_QUEUE_TRANSPORT, SPEC_VERSION_SUPPORTS_EVENT_SOURCING)
so future SPEC_VERSION_CURRENT bumps don't shift existing feature gates.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Update world-postgres test to use SPEC_VERSION_CURRENT
ddc8c31
Replace hardcoded specVersion: 2 with SPEC_VERSION_CURRENT so
the test tracks spec version bumps.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Include specVersion in health check responses
cf3dd88
Both the HTTP health check endpoint (?__health) and the queue-based
health check stream now return specVersion, allowing observability
tools to query deployment capabilities.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious
Merge branch 'main' into peter/cbor-transport-compat
50407fe
@VaguelySerious
fix health check test
330d70d
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@vercel@VaguelySerious
Fix: Health check e2e test assertions are missing the endpoint fiel…
82dcbe2
…d, causing `toEqual` to fail due to exact equality mismatch.
This commit fixes the issue reported at packages/core/e2e/e2e.test.ts:1550
**Bug explanation:**
The `withHealthCheck` handler in `packages/core/src/runtime/helpers.ts` returns a JSON response with three fields: `{ healthy: true, endpoint: url.pathname, specVersion: SPEC_VERSION_CURRENT }`. However, the HTTP-based health check e2e test in `packages/core/e2e/e2e.test.ts` (lines 1549-1553 and 1567-1571) uses `toEqual` to assert against objects that only have two fields: `{ healthy: true, specVersion: SPEC_VERSION_CURRENT }`, missing the `endpoint` field.
In Vitest, `toEqual` performs exact deep equality checking. When the actual response object contains `{ healthy: true, endpoint: "/.well-known/workflow/v1/flow", specVersion: "..." }` but the expected object only has `{ healthy: true, specVersion: "..." }`, the assertion fails because the actual object has an extra `endpoint` property not present in the expected object.
This affects both the flow endpoint health check assertion and the step endpoint health check assertion.
**Fix explanation:**
Added the missing `endpoint` field to both `toEqual` assertions:
- For the flow endpoint: `endpoint: '/.well-known/workflow/v1/flow'` (the pathname portion of `/.well-known/workflow/v1/flow?__health`)
- For the step endpoint: `endpoint: '/.well-known/workflow/v1/step'` (the pathname portion of `/.well-known/workflow/v1/step?__health`)
These values match what `url.pathname` returns in the handler (the `?__health` query parameter is not part of the pathname). This makes the test assertions exactly match the actual response structure from the handler.
Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Co-authored-by: VaguelySerious <mittgfu@gmail.com>
@VaguelySerious
fix
ce9ba33
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious
fix
57cb399
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious@claude
Propagate specVersion through queue-based health check result
419de89
Update HealthCheckResult to include specVersion and parse it from the
stream response, so observability tools can query deployment capabilities
through both the HTTP and queue-based health check paths.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Fix TypeScript cast in parseHealthCheckResponse
ff8a79c
Use Record<string, unknown> instead of narrower casts that tsc
rejects as insufficient overlap.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
[cli] [core] Probe deployment specVersion before CLI start
7b42568
CLI start command now queries the deployment's health check endpoint
to determine its specVersion before calling start(). This ensures the
correct queue transport is used (JSON for old deployments, CBOR for
new). Falls back to the run's specVersion if health check fails.
Health check always uses JSON transport (specVersion: SPEC_VERSION_LEGACY)
so the probe works against both old and new deployments. Also adds
deploymentId option to HealthCheckOptions for targeted health checks.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@vercel
vercelBot
commented
Apr 7, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
The latest updates on your projects. Learn more about Vercel for GitHub.
ProjectDeploymentActionsUpdated (UTC)
example-nextjs-workflow-turbopackReadyReadyPreview, CommentApr 7, 2026 5:52pm
example-nextjs-workflow-webpackReadyReadyPreview, CommentApr 7, 2026 5:52pm
example-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-astro-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-express-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-fastify-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-hono-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-nitro-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-nuxt-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-sveltekit-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-vite-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workflow-docsReadyReadyPreview, Comment, Open in v0Apr 7, 2026 5:52pm
workflow-swc-playgroundReadyReadyPreview, CommentApr 7, 2026 5:52pm
@VaguelySerious
VaguelySerious
requested a review
from a team
as a code ownerApril 7, 2026 00:22
@changeset-bot
changeset-botBot
commented
Apr 7, 2026•

edited

Loading

Copy link


Copy Markdown

🦋 Changeset detected
Latest commit: 51fb2ab
The changes in this PR will be included in the next version bump.
This PR includes changesets to release 16 packages
NameType
@workflow/corePatch
@workflow/cliPatch
@workflow/buildersPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/vitestPatch
@workflow/web-sharedPatch
workflowPatch
@workflow/world-testingPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch
@workflow/aiPatch
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
github-actionsBot
commented
Apr 7, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
🧪 E2E Test Results
❌ Some tests failed
Summary
PassedFailedSkippedTotal
❌ ▲ Vercel Production878167946
✅ 💻 Local Development85401781032
✅ 📦 Local Production85401781032
✅ 🐘 Local Postgres85401781032
✅ 🪟 Windows780886
❌ 🌍 Community Worlds1660884
✅ 📋 Other216042258
Total3750616594470
❌ Failed Tests
▲ Vercel Production (1 failed)
hono (1 failed):
🌍 Community Worlds (60 failed)
mongodb-dev (1 failed):
  • dev e2e should rebuild on imported step dependency change
redis-dev (1 failed):
  • dev e2e should rebuild on imported step dependency change
turso-dev (1 failed):
  • dev e2e should rebuild on imported step dependency change
turso (57 failed):
  • addTenWorkflow | wrun_01KNMH5VCWZ2YQDPP365WEZTM4
  • addTenWorkflow | wrun_01KNMH5VCWZ2YQDPP365WEZTM4
  • wellKnownAgentWorkflow (.well-known/agent) | wrun_01KNMH75H1GT8X09J9WS5F6FA6
  • should work with react rendering in step
  • promiseAllWorkflow | wrun_01KNMH63YAHQKDCZQT1EPYKGX8
  • promiseRaceWorkflow | wrun_01KNMH699ZAQD55FBQV3XNHM7X
  • promiseAnyWorkflow | wrun_01KNMH6C1XSP0EZ96TT0J5E8PF
  • importedStepOnlyWorkflow | wrun_01KNMH7GSJTNP0DX1PGSPFNTZZ
  • hookWorkflow | wrun_01KNMH6S06RS6VXGS41PF3GWSB
  • hookWorkflow is not resumable via public webhook endpoint | wrun_01KNMH76KMG0ZCB7ST88V553JE
  • webhookWorkflow | wrun_01KNMH7H30FD15T64RRS74743D
  • sleepingWorkflow | wrun_01KNMH7TG251JCYH1HS6DV9PKV
  • parallelSleepWorkflow | wrun_01KNMH87BSQPDNQBW8RR8GMHVR
  • nullByteWorkflow | wrun_01KNMH8B46P0EM2F1T1T2EQT07
  • workflowAndStepMetadataWorkflow | wrun_01KNMH8DKDK9H0CTSMSMJYV7J1
  • fetchWorkflow | wrun_01KNMHBA5EJNGZ9Y10R47QQ7TS
  • promiseRaceStressTestWorkflow | wrun_01KNMHBD0VT8JK2JD5N8JDTNTX
  • 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()
  • error handling not registered WorkflowNotRegisteredError fails the run when workflow does not exist
  • error handling not registered StepNotRegisteredError fails the step but workflow can catch it
  • error handling not registered StepNotRegisteredError fails the run when not caught in workflow
  • hookCleanupTestWorkflow - hook token reuse after workflow completion | wrun_01KNMHF707573TY2VWEG6X4DNH
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously | wrun_01KNMHFWK8Q44KY5E9X4R9ASHD
  • hookDisposeTestWorkflow - hook token reuse after explicit disposal while workflow still running | wrun_01KNMHGM9JGZWZSBXT32C90R37
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars) | wrun_01KNMHHA40QC8M5BFCX3WRN9DS
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument | wrun_01KNMHHKY5FCTHAD7DQ2RGH0AW
  • closureVariableWorkflow - nested step functions with closure variables | wrun_01KNMHHT09G8K4G7EG4F36D42G
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step | wrun_01KNMHHWDR6ZZGV5585HXJBY19
  • health check (queue-based) - workflow and step endpoints respond to health check messages
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly | wrun_01KNMHJBHXQHBXCB06Q1RQ364Z
  • Calculator.calculate - static workflow method using static step methods from another class | wrun_01KNMHJHYZ7X33V0S840FX5W9Q
  • AllInOneService.processNumber - static workflow method using sibling static step methods | wrun_01KNMHJRQ8QEZG1WYA9X4NE9G4
  • ChainableService.processWithThis - static step methods using this to reference the class | wrun_01KNMHJZB674R8TQ8TN8AA026X
  • thisSerializationWorkflow - step function invoked with .call() and .apply() | wrun_01KNMHK64J28XRFGM5X10GD015
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE | wrun_01KNMHKCJH3BSFD5V6A5DJSKV8
  • instanceMethodStepWorkflow - instance methods with "use step" directive | wrun_01KNMHKJXNGX0BC6AG4EP84PH0
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context | wrun_01KNMHKW4R2DSSHKGVJXT66ZGB
  • stepFunctionAsStartArgWorkflow - step function reference passed as start() argument | wrun_01KNMHM4QSV8SW6786SA9H6NFD
  • cancelRun - cancelling a running workflow | wrun_01KNMHMC10ES9NS6ZW9MAK03E4
  • cancelRun via CLI - cancelling a running workflow | wrun_01KNMHMMSK0AGPXGJR7JK82QDR
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router
  • hookWithSleepWorkflow - hook payloads delivered correctly with concurrent sleep | wrun_01KNMHMZYT36WW88RZPBQRKBH1
  • sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration | wrun_01KNMHNKEWEEQWTPPWGB7YNWSW
  • sleepWithSequentialStepsWorkflow - sequential steps work with concurrent sleep (control) | wrun_01KNMHNY2NHRBQ53J3TY57ZGSR
  • importMetaUrlWorkflow - import.meta.url is available in step bundles | wrun_01KNMHP4PAJEEA4DPSG64JC7M6
  • metadataFromHelperWorkflow - getWorkflowMetadata/getStepMetadata work from module-level helper (#1577) | wrun_01KNMHP6N2TBYR581JBV88ESXE
  • resilient start: addTenWorkflow completes when run_created returns 500 | wrun_01KNMHP8T5FNQQ8Z6MNZH87SNG
Details by Category
❌ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro7907
✅ example7907
✅ express7907
✅ fastify7907
❌ hono7817
✅ nextjs-turbopack8402
✅ nextjs-webpack8402
✅ nitro7907
✅ nuxt7907
✅ sveltekit7907
✅ vite7907
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable72014
✅ express-stable72014
✅ fastify-stable72014
✅ hono-stable72014
✅ nextjs-turbopack-canary61025
✅ nextjs-turbopack-stable7808
✅ nextjs-webpack-canary61025
✅ nextjs-webpack-stable7808
✅ nitro-stable72014
✅ nuxt-stable72014
✅ sveltekit-stable72014
✅ vite-stable72014
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable72014
✅ express-stable72014
✅ fastify-stable72014
✅ hono-stable72014
✅ nextjs-turbopack-canary61025
✅ nextjs-turbopack-stable7808
✅ nextjs-webpack-canary61025
✅ nextjs-webpack-stable7808
✅ nitro-stable72014
✅ nuxt-stable72014
✅ sveltekit-stable72014
✅ vite-stable72014
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable72014
✅ express-stable72014
✅ fastify-stable72014
✅ hono-stable72014
✅ nextjs-turbopack-canary61025
✅ nextjs-turbopack-stable7808
✅ nextjs-webpack-canary61025
✅ nextjs-webpack-stable7808
✅ nitro-stable72014
✅ nuxt-stable72014
✅ sveltekit-stable72014
✅ vite-stable72014
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack7808
❌ 🌍 Community Worlds
AppPassedFailedSkipped
❌ mongodb-dev410
❌ redis-dev410
❌ turso-dev410
❌ turso4578
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable72014
✅ e2e-local-postgres-nest-stable72014
✅ e2e-local-prod-nest-stable72014
📋 View full workflow run
❌ Some E2E test jobs failed:
  • Vercel Prod: failure
  • Local Dev: success
  • Local Prod: success
  • Local Postgres: success
  • Windows: success
Check the workflow run for details.
@VaguelySerious@claude
Include workflowCoreVersion in health check responses
51fb2ab
Both the HTTP (?__health) and queue-based health check endpoints
now return the @workflow/core package version, allowing observability
tools to identify exactly which SDK version a deployment is running.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious
VaguelySerious
merged commit a6bcea9
into
mainApr 7, 2026

92 of 99 checks passed

@VaguelySerious
VaguelySerious
deleted the

peter/cli-specversion-probe

branch
April 7, 2026 18:03
@ghostghost
mentioned this pull request
Apr 7, 2026
 Merged

VaguelySerious added a commit
that referenced
this pull request
Apr 7, 2026
@VaguelySerious
[cli] [core] Probe deployment specVersion before CLI start (#1629)
f0d6a85
@TooTallNateTooTallNate
mentioned this pull request
Apr 8, 2026
 Merged

7 tasks
@VaguelySeriousVaguelySerious
mentioned this pull request
Apr 16, 2026
 Closed

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

Reviewers

@TooTallNateTooTallNateTooTallNate approved these changes

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@VaguelySerious@TooTallNate

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
[cli] [core] Probe deployment specVersion before CLI start - #1629
Merged
VaguelySerious merged 17 commits into
mainfrom 
peter/cli-specversion-probe
Apr 7, 2026
Merged
[cli] [core] Probe deployment specVersion before CLI start#1629
VaguelySerious merged 17 commits into
mainfrom 
peter/cli-specversion-probe
Conversation
@VaguelySerious
@VaguelySeriousVaguelySerious
commented
Apr 7, 2026

Copy link


Copy Markdown

Member
Summary
Based on #1627. CLI start command now probes the target deployment's specVersion via health check before calling start(), ensuring the correct queue transport is used.
  • Health check always uses JSON transport (specVersion: SPEC_VERSION_LEGACY) so the probe works against both old and new deployments
  • Adds deploymentId option to HealthCheckOptions for targeted health checks
  • Falls back to the existing run's specVersion if health check fails (e.g. old deployment without health check support)
Other paths that call start() without knowing specVersion
Call siteKnows specVersion?Notes
CLI startNow probedThis PR
recreateRunFromExisting (web dashboard replay)YesUses run.specVersion from original run
User code (import { start } from 'workflow')N/ARuns ON the deployment, so SPEC_VERSION_CURRENT is correct
Testing server (world-testing)NoNot production-relevant
Test plan
  • packages/core unit tests pass (580/580)
  •  Full build passes
  •  e2e: CLI start against old deployment uses JSON transport
  •  e2e: CLI start against new deployment uses CBOR transport
  •  e2e: CLI start with health check timeout falls back to run specVersion
🤖 Generated with Claude Code
VaguelySeriousand others
added 13 commits
April 6, 2026 15:56
@VaguelySerious@claude
fix: gate queue transport format on specVersion for CBOR compat
8399d51
Bump SPEC_VERSION_CURRENT to 3 and fix isLegacySpecVersion to check
against SPEC_VERSION_LEGACY instead of SPEC_VERSION_CURRENT, preventing
v2 runs from being incorrectly treated as legacy when the version bumps.
Add JsonTransport and DualTransport to world-vercel queue: the handler
uses DualTransport (CBOR-first, JSON fallback) to accept messages from
both old and new deployments, while the send path selects CBOR or JSON
based on the target run's specVersion. Pass specVersion through queue
opts from start(), reenqueueRun(), wakeUpRun(), and resumeHook().
Only include runInput in the queue payload for specVersion >= 3, creating
clean separation between old and new behavior.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
[core] [world] Gate CBOR queue transport on specVersion
b6b6dcf
Bump specVersion to 3. Use JSON transport for queue messages targeting
older deployments (specVersion < 3), CBOR for new ones. Handler uses
dual transport that deserializes both formats, so new deployments can
receive messages from old and new senders.
Fixes replay/reenqueue from the dashboard to older deployments that
expect JSON queue messages.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Use named spec version constants for feature boundaries
dd2699b
Replace SPEC_VERSION_CURRENT comparisons with named constants
(SPEC_VERSION_SUPPORTS_CBOR_QUEUE_TRANSPORT, SPEC_VERSION_SUPPORTS_EVENT_SOURCING)
so future SPEC_VERSION_CURRENT bumps don't shift existing feature gates.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Update world-postgres test to use SPEC_VERSION_CURRENT
ddc8c31
Replace hardcoded specVersion: 2 with SPEC_VERSION_CURRENT so
the test tracks spec version bumps.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Include specVersion in health check responses
cf3dd88
Both the HTTP health check endpoint (?__health) and the queue-based
health check stream now return specVersion, allowing observability
tools to query deployment capabilities.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious
Merge branch 'main' into peter/cbor-transport-compat
50407fe
@VaguelySerious
fix health check test
330d70d
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@vercel@VaguelySerious
Fix: Health check e2e test assertions are missing the endpoint fiel…
82dcbe2
…d, causing `toEqual` to fail due to exact equality mismatch.
This commit fixes the issue reported at packages/core/e2e/e2e.test.ts:1550
**Bug explanation:**
The `withHealthCheck` handler in `packages/core/src/runtime/helpers.ts` returns a JSON response with three fields: `{ healthy: true, endpoint: url.pathname, specVersion: SPEC_VERSION_CURRENT }`. However, the HTTP-based health check e2e test in `packages/core/e2e/e2e.test.ts` (lines 1549-1553 and 1567-1571) uses `toEqual` to assert against objects that only have two fields: `{ healthy: true, specVersion: SPEC_VERSION_CURRENT }`, missing the `endpoint` field.
In Vitest, `toEqual` performs exact deep equality checking. When the actual response object contains `{ healthy: true, endpoint: "/.well-known/workflow/v1/flow", specVersion: "..." }` but the expected object only has `{ healthy: true, specVersion: "..." }`, the assertion fails because the actual object has an extra `endpoint` property not present in the expected object.
This affects both the flow endpoint health check assertion and the step endpoint health check assertion.
**Fix explanation:**
Added the missing `endpoint` field to both `toEqual` assertions:
- For the flow endpoint: `endpoint: '/.well-known/workflow/v1/flow'` (the pathname portion of `/.well-known/workflow/v1/flow?__health`)
- For the step endpoint: `endpoint: '/.well-known/workflow/v1/step'` (the pathname portion of `/.well-known/workflow/v1/step?__health`)
These values match what `url.pathname` returns in the handler (the `?__health` query parameter is not part of the pathname). This makes the test assertions exactly match the actual response structure from the handler.
Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Co-authored-by: VaguelySerious <mittgfu@gmail.com>
@VaguelySerious
fix
ce9ba33
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious
fix
57cb399
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious@claude
Propagate specVersion through queue-based health check result
419de89
Update HealthCheckResult to include specVersion and parse it from the
stream response, so observability tools can query deployment capabilities
through both the HTTP and queue-based health check paths.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Fix TypeScript cast in parseHealthCheckResponse
ff8a79c
Use Record<string, unknown> instead of narrower casts that tsc
rejects as insufficient overlap.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
[cli] [core] Probe deployment specVersion before CLI start
7b42568
CLI start command now queries the deployment's health check endpoint
to determine its specVersion before calling start(). This ensures the
correct queue transport is used (JSON for old deployments, CBOR for
new). Falls back to the run's specVersion if health check fails.
Health check always uses JSON transport (specVersion: SPEC_VERSION_LEGACY)
so the probe works against both old and new deployments. Also adds
deploymentId option to HealthCheckOptions for targeted health checks.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@vercel
vercelBot
commented
Apr 7, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
The latest updates on your projects. Learn more about Vercel for GitHub.
ProjectDeploymentActionsUpdated (UTC)
example-nextjs-workflow-turbopackReadyReadyPreview, CommentApr 7, 2026 5:52pm
example-nextjs-workflow-webpackReadyReadyPreview, CommentApr 7, 2026 5:52pm
example-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-astro-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-express-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-fastify-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-hono-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-nitro-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-nuxt-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-sveltekit-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-vite-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workflow-docsReadyReadyPreview, Comment, Open in v0Apr 7, 2026 5:52pm
workflow-swc-playgroundReadyReadyPreview, CommentApr 7, 2026 5:52pm
@VaguelySerious
VaguelySerious
requested a review
from a team
as a code ownerApril 7, 2026 00:22
@changeset-bot
changeset-botBot
commented
Apr 7, 2026•

edited

Loading

Copy link


Copy Markdown

🦋 Changeset detected
Latest commit: 51fb2ab
The changes in this PR will be included in the next version bump.
This PR includes changesets to release 16 packages
NameType
@workflow/corePatch
@workflow/cliPatch
@workflow/buildersPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/vitestPatch
@workflow/web-sharedPatch
workflowPatch
@workflow/world-testingPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch
@workflow/aiPatch
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
github-actionsBot
commented
Apr 7, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
🧪 E2E Test Results
❌ Some tests failed
Summary
PassedFailedSkippedTotal
❌ ▲ Vercel Production878167946
✅ 💻 Local Development85401781032
✅ 📦 Local Production85401781032
✅ 🐘 Local Postgres85401781032
✅ 🪟 Windows780886
❌ 🌍 Community Worlds1660884
✅ 📋 Other216042258
Total3750616594470
❌ Failed Tests
▲ Vercel Production (1 failed)
hono (1 failed):
🌍 Community Worlds (60 failed)
mongodb-dev (1 failed):
  • dev e2e should rebuild on imported step dependency change
redis-dev (1 failed):
  • dev e2e should rebuild on imported step dependency change
turso-dev (1 failed):
  • dev e2e should rebuild on imported step dependency change
turso (57 failed):
  • addTenWorkflow | wrun_01KNMH5VCWZ2YQDPP365WEZTM4
  • addTenWorkflow | wrun_01KNMH5VCWZ2YQDPP365WEZTM4
  • wellKnownAgentWorkflow (.well-known/agent) | wrun_01KNMH75H1GT8X09J9WS5F6FA6
  • should work with react rendering in step
  • promiseAllWorkflow | wrun_01KNMH63YAHQKDCZQT1EPYKGX8
  • promiseRaceWorkflow | wrun_01KNMH699ZAQD55FBQV3XNHM7X
  • promiseAnyWorkflow | wrun_01KNMH6C1XSP0EZ96TT0J5E8PF
  • importedStepOnlyWorkflow | wrun_01KNMH7GSJTNP0DX1PGSPFNTZZ
  • hookWorkflow | wrun_01KNMH6S06RS6VXGS41PF3GWSB
  • hookWorkflow is not resumable via public webhook endpoint | wrun_01KNMH76KMG0ZCB7ST88V553JE
  • webhookWorkflow | wrun_01KNMH7H30FD15T64RRS74743D
  • sleepingWorkflow | wrun_01KNMH7TG251JCYH1HS6DV9PKV
  • parallelSleepWorkflow | wrun_01KNMH87BSQPDNQBW8RR8GMHVR
  • nullByteWorkflow | wrun_01KNMH8B46P0EM2F1T1T2EQT07
  • workflowAndStepMetadataWorkflow | wrun_01KNMH8DKDK9H0CTSMSMJYV7J1
  • fetchWorkflow | wrun_01KNMHBA5EJNGZ9Y10R47QQ7TS
  • promiseRaceStressTestWorkflow | wrun_01KNMHBD0VT8JK2JD5N8JDTNTX
  • 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()
  • error handling not registered WorkflowNotRegisteredError fails the run when workflow does not exist
  • error handling not registered StepNotRegisteredError fails the step but workflow can catch it
  • error handling not registered StepNotRegisteredError fails the run when not caught in workflow
  • hookCleanupTestWorkflow - hook token reuse after workflow completion | wrun_01KNMHF707573TY2VWEG6X4DNH
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously | wrun_01KNMHFWK8Q44KY5E9X4R9ASHD
  • hookDisposeTestWorkflow - hook token reuse after explicit disposal while workflow still running | wrun_01KNMHGM9JGZWZSBXT32C90R37
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars) | wrun_01KNMHHA40QC8M5BFCX3WRN9DS
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument | wrun_01KNMHHKY5FCTHAD7DQ2RGH0AW
  • closureVariableWorkflow - nested step functions with closure variables | wrun_01KNMHHT09G8K4G7EG4F36D42G
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step | wrun_01KNMHHWDR6ZZGV5585HXJBY19
  • health check (queue-based) - workflow and step endpoints respond to health check messages
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly | wrun_01KNMHJBHXQHBXCB06Q1RQ364Z
  • Calculator.calculate - static workflow method using static step methods from another class | wrun_01KNMHJHYZ7X33V0S840FX5W9Q
  • AllInOneService.processNumber - static workflow method using sibling static step methods | wrun_01KNMHJRQ8QEZG1WYA9X4NE9G4
  • ChainableService.processWithThis - static step methods using this to reference the class | wrun_01KNMHJZB674R8TQ8TN8AA026X
  • thisSerializationWorkflow - step function invoked with .call() and .apply() | wrun_01KNMHK64J28XRFGM5X10GD015
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE | wrun_01KNMHKCJH3BSFD5V6A5DJSKV8
  • instanceMethodStepWorkflow - instance methods with "use step" directive | wrun_01KNMHKJXNGX0BC6AG4EP84PH0
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context | wrun_01KNMHKW4R2DSSHKGVJXT66ZGB
  • stepFunctionAsStartArgWorkflow - step function reference passed as start() argument | wrun_01KNMHM4QSV8SW6786SA9H6NFD
  • cancelRun - cancelling a running workflow | wrun_01KNMHMC10ES9NS6ZW9MAK03E4
  • cancelRun via CLI - cancelling a running workflow | wrun_01KNMHMMSK0AGPXGJR7JK82QDR
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router
  • hookWithSleepWorkflow - hook payloads delivered correctly with concurrent sleep | wrun_01KNMHMZYT36WW88RZPBQRKBH1
  • sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration | wrun_01KNMHNKEWEEQWTPPWGB7YNWSW
  • sleepWithSequentialStepsWorkflow - sequential steps work with concurrent sleep (control) | wrun_01KNMHNY2NHRBQ53J3TY57ZGSR
  • importMetaUrlWorkflow - import.meta.url is available in step bundles | wrun_01KNMHP4PAJEEA4DPSG64JC7M6
  • metadataFromHelperWorkflow - getWorkflowMetadata/getStepMetadata work from module-level helper (#1577) | wrun_01KNMHP6N2TBYR581JBV88ESXE
  • resilient start: addTenWorkflow completes when run_created returns 500 | wrun_01KNMHP8T5FNQQ8Z6MNZH87SNG
Details by Category
❌ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro7907
✅ example7907
✅ express7907
✅ fastify7907
❌ hono7817
✅ nextjs-turbopack8402
✅ nextjs-webpack8402
✅ nitro7907
✅ nuxt7907
✅ sveltekit7907
✅ vite7907
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable72014
✅ express-stable72014
✅ fastify-stable72014
✅ hono-stable72014
✅ nextjs-turbopack-canary61025
✅ nextjs-turbopack-stable7808
✅ nextjs-webpack-canary61025
✅ nextjs-webpack-stable7808
✅ nitro-stable72014
✅ nuxt-stable72014
✅ sveltekit-stable72014
✅ vite-stable72014
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable72014
✅ express-stable72014
✅ fastify-stable72014
✅ hono-stable72014
✅ nextjs-turbopack-canary61025
✅ nextjs-turbopack-stable7808
✅ nextjs-webpack-canary61025
✅ nextjs-webpack-stable7808
✅ nitro-stable72014
✅ nuxt-stable72014
✅ sveltekit-stable72014
✅ vite-stable72014
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable72014
✅ express-stable72014
✅ fastify-stable72014
✅ hono-stable72014
✅ nextjs-turbopack-canary61025
✅ nextjs-turbopack-stable7808
✅ nextjs-webpack-canary61025
✅ nextjs-webpack-stable7808
✅ nitro-stable72014
✅ nuxt-stable72014
✅ sveltekit-stable72014
✅ vite-stable72014
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack7808
❌ 🌍 Community Worlds
AppPassedFailedSkipped
❌ mongodb-dev410
❌ redis-dev410
❌ turso-dev410
❌ turso4578
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable72014
✅ e2e-local-postgres-nest-stable72014
✅ e2e-local-prod-nest-stable72014
📋 View full workflow run
❌ Some E2E test jobs failed:
  • Vercel Prod: failure
  • Local Dev: success
  • Local Prod: success
  • Local Postgres: success
  • Windows: success
Check the workflow run for details.
@VaguelySerious@claude
Include workflowCoreVersion in health check responses
51fb2ab
Both the HTTP (?__health) and queue-based health check endpoints
now return the @workflow/core package version, allowing observability
tools to identify exactly which SDK version a deployment is running.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious
VaguelySerious
merged commit a6bcea9
into
mainApr 7, 2026

92 of 99 checks passed

@VaguelySerious
VaguelySerious
deleted the

peter/cli-specversion-probe

branch
April 7, 2026 18:03
@ghostghost
mentioned this pull request
Apr 7, 2026
 Merged

VaguelySerious added a commit
that referenced
this pull request
Apr 7, 2026
@VaguelySerious
[cli] [core] Probe deployment specVersion before CLI start (#1629)
f0d6a85
@TooTallNateTooTallNate
mentioned this pull request
Apr 8, 2026
 Merged

7 tasks
@VaguelySeriousVaguelySerious
mentioned this pull request
Apr 16, 2026
 Closed

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

Reviewers

@TooTallNateTooTallNateTooTallNate approved these changes

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@VaguelySerious@TooTallNate

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
[cli] [core] Probe deployment specVersion before CLI start - #1629
Merged
VaguelySerious merged 17 commits into
mainfrom 
peter/cli-specversion-probe
Apr 7, 2026
Merged
[cli] [core] Probe deployment specVersion before CLI start#1629
VaguelySerious merged 17 commits into
mainfrom 
peter/cli-specversion-probe
Conversation
@VaguelySerious
@VaguelySeriousVaguelySerious
commented
Apr 7, 2026

Copy link


Copy Markdown

Member
Summary
Based on #1627. CLI start command now probes the target deployment's specVersion via health check before calling start(), ensuring the correct queue transport is used.
  • Health check always uses JSON transport (specVersion: SPEC_VERSION_LEGACY) so the probe works against both old and new deployments
  • Adds deploymentId option to HealthCheckOptions for targeted health checks
  • Falls back to the existing run's specVersion if health check fails (e.g. old deployment without health check support)
Other paths that call start() without knowing specVersion
Call siteKnows specVersion?Notes
CLI startNow probedThis PR
recreateRunFromExisting (web dashboard replay)YesUses run.specVersion from original run
User code (import { start } from 'workflow')N/ARuns ON the deployment, so SPEC_VERSION_CURRENT is correct
Testing server (world-testing)NoNot production-relevant
Test plan
  • packages/core unit tests pass (580/580)
  •  Full build passes
  •  e2e: CLI start against old deployment uses JSON transport
  •  e2e: CLI start against new deployment uses CBOR transport
  •  e2e: CLI start with health check timeout falls back to run specVersion
🤖 Generated with Claude Code
VaguelySeriousand others
added 13 commits
April 6, 2026 15:56
@VaguelySerious@claude
fix: gate queue transport format on specVersion for CBOR compat
8399d51
Bump SPEC_VERSION_CURRENT to 3 and fix isLegacySpecVersion to check
against SPEC_VERSION_LEGACY instead of SPEC_VERSION_CURRENT, preventing
v2 runs from being incorrectly treated as legacy when the version bumps.
Add JsonTransport and DualTransport to world-vercel queue: the handler
uses DualTransport (CBOR-first, JSON fallback) to accept messages from
both old and new deployments, while the send path selects CBOR or JSON
based on the target run's specVersion. Pass specVersion through queue
opts from start(), reenqueueRun(), wakeUpRun(), and resumeHook().
Only include runInput in the queue payload for specVersion >= 3, creating
clean separation between old and new behavior.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
[core] [world] Gate CBOR queue transport on specVersion
b6b6dcf
Bump specVersion to 3. Use JSON transport for queue messages targeting
older deployments (specVersion < 3), CBOR for new ones. Handler uses
dual transport that deserializes both formats, so new deployments can
receive messages from old and new senders.
Fixes replay/reenqueue from the dashboard to older deployments that
expect JSON queue messages.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Use named spec version constants for feature boundaries
dd2699b
Replace SPEC_VERSION_CURRENT comparisons with named constants
(SPEC_VERSION_SUPPORTS_CBOR_QUEUE_TRANSPORT, SPEC_VERSION_SUPPORTS_EVENT_SOURCING)
so future SPEC_VERSION_CURRENT bumps don't shift existing feature gates.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Update world-postgres test to use SPEC_VERSION_CURRENT
ddc8c31
Replace hardcoded specVersion: 2 with SPEC_VERSION_CURRENT so
the test tracks spec version bumps.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Include specVersion in health check responses
cf3dd88
Both the HTTP health check endpoint (?__health) and the queue-based
health check stream now return specVersion, allowing observability
tools to query deployment capabilities.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious
Merge branch 'main' into peter/cbor-transport-compat
50407fe
@VaguelySerious
fix health check test
330d70d
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@vercel@VaguelySerious
Fix: Health check e2e test assertions are missing the endpoint fiel…
82dcbe2
…d, causing `toEqual` to fail due to exact equality mismatch.
This commit fixes the issue reported at packages/core/e2e/e2e.test.ts:1550
**Bug explanation:**
The `withHealthCheck` handler in `packages/core/src/runtime/helpers.ts` returns a JSON response with three fields: `{ healthy: true, endpoint: url.pathname, specVersion: SPEC_VERSION_CURRENT }`. However, the HTTP-based health check e2e test in `packages/core/e2e/e2e.test.ts` (lines 1549-1553 and 1567-1571) uses `toEqual` to assert against objects that only have two fields: `{ healthy: true, specVersion: SPEC_VERSION_CURRENT }`, missing the `endpoint` field.
In Vitest, `toEqual` performs exact deep equality checking. When the actual response object contains `{ healthy: true, endpoint: "/.well-known/workflow/v1/flow", specVersion: "..." }` but the expected object only has `{ healthy: true, specVersion: "..." }`, the assertion fails because the actual object has an extra `endpoint` property not present in the expected object.
This affects both the flow endpoint health check assertion and the step endpoint health check assertion.
**Fix explanation:**
Added the missing `endpoint` field to both `toEqual` assertions:
- For the flow endpoint: `endpoint: '/.well-known/workflow/v1/flow'` (the pathname portion of `/.well-known/workflow/v1/flow?__health`)
- For the step endpoint: `endpoint: '/.well-known/workflow/v1/step'` (the pathname portion of `/.well-known/workflow/v1/step?__health`)
These values match what `url.pathname` returns in the handler (the `?__health` query parameter is not part of the pathname). This makes the test assertions exactly match the actual response structure from the handler.
Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Co-authored-by: VaguelySerious <mittgfu@gmail.com>
@VaguelySerious
fix
ce9ba33
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious
fix
57cb399
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious@claude
Propagate specVersion through queue-based health check result
419de89
Update HealthCheckResult to include specVersion and parse it from the
stream response, so observability tools can query deployment capabilities
through both the HTTP and queue-based health check paths.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Fix TypeScript cast in parseHealthCheckResponse
ff8a79c
Use Record<string, unknown> instead of narrower casts that tsc
rejects as insufficient overlap.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
[cli] [core] Probe deployment specVersion before CLI start
7b42568
CLI start command now queries the deployment's health check endpoint
to determine its specVersion before calling start(). This ensures the
correct queue transport is used (JSON for old deployments, CBOR for
new). Falls back to the run's specVersion if health check fails.
Health check always uses JSON transport (specVersion: SPEC_VERSION_LEGACY)
so the probe works against both old and new deployments. Also adds
deploymentId option to HealthCheckOptions for targeted health checks.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@vercel
vercelBot
commented
Apr 7, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
The latest updates on your projects. Learn more about Vercel for GitHub.
ProjectDeploymentActionsUpdated (UTC)
example-nextjs-workflow-turbopackReadyReadyPreview, CommentApr 7, 2026 5:52pm
example-nextjs-workflow-webpackReadyReadyPreview, CommentApr 7, 2026 5:52pm
example-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-astro-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-express-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-fastify-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-hono-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-nitro-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-nuxt-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-sveltekit-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-vite-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workflow-docsReadyReadyPreview, Comment, Open in v0Apr 7, 2026 5:52pm
workflow-swc-playgroundReadyReadyPreview, CommentApr 7, 2026 5:52pm
@VaguelySerious
VaguelySerious
requested a review
from a team
as a code ownerApril 7, 2026 00:22
@changeset-bot
changeset-botBot
commented
Apr 7, 2026•

edited

Loading

Copy link


Copy Markdown

🦋 Changeset detected
Latest commit: 51fb2ab
The changes in this PR will be included in the next version bump.
This PR includes changesets to release 16 packages
NameType
@workflow/corePatch
@workflow/cliPatch
@workflow/buildersPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/vitestPatch
@workflow/web-sharedPatch
workflowPatch
@workflow/world-testingPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch
@workflow/aiPatch
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
github-actionsBot
commented
Apr 7, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
🧪 E2E Test Results
❌ Some tests failed
Summary
PassedFailedSkippedTotal
❌ ▲ Vercel Production878167946
✅ 💻 Local Development85401781032
✅ 📦 Local Production85401781032
✅ 🐘 Local Postgres85401781032
✅ 🪟 Windows780886
❌ 🌍 Community Worlds1660884
✅ 📋 Other216042258
Total3750616594470
❌ Failed Tests
▲ Vercel Production (1 failed)
hono (1 failed):
🌍 Community Worlds (60 failed)
mongodb-dev (1 failed):
  • dev e2e should rebuild on imported step dependency change
redis-dev (1 failed):
  • dev e2e should rebuild on imported step dependency change
turso-dev (1 failed):
  • dev e2e should rebuild on imported step dependency change
turso (57 failed):
  • addTenWorkflow | wrun_01KNMH5VCWZ2YQDPP365WEZTM4
  • addTenWorkflow | wrun_01KNMH5VCWZ2YQDPP365WEZTM4
  • wellKnownAgentWorkflow (.well-known/agent) | wrun_01KNMH75H1GT8X09J9WS5F6FA6
  • should work with react rendering in step
  • promiseAllWorkflow | wrun_01KNMH63YAHQKDCZQT1EPYKGX8
  • promiseRaceWorkflow | wrun_01KNMH699ZAQD55FBQV3XNHM7X
  • promiseAnyWorkflow | wrun_01KNMH6C1XSP0EZ96TT0J5E8PF
  • importedStepOnlyWorkflow | wrun_01KNMH7GSJTNP0DX1PGSPFNTZZ
  • hookWorkflow | wrun_01KNMH6S06RS6VXGS41PF3GWSB
  • hookWorkflow is not resumable via public webhook endpoint | wrun_01KNMH76KMG0ZCB7ST88V553JE
  • webhookWorkflow | wrun_01KNMH7H30FD15T64RRS74743D
  • sleepingWorkflow | wrun_01KNMH7TG251JCYH1HS6DV9PKV
  • parallelSleepWorkflow | wrun_01KNMH87BSQPDNQBW8RR8GMHVR
  • nullByteWorkflow | wrun_01KNMH8B46P0EM2F1T1T2EQT07
  • workflowAndStepMetadataWorkflow | wrun_01KNMH8DKDK9H0CTSMSMJYV7J1
  • fetchWorkflow | wrun_01KNMHBA5EJNGZ9Y10R47QQ7TS
  • promiseRaceStressTestWorkflow | wrun_01KNMHBD0VT8JK2JD5N8JDTNTX
  • 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()
  • error handling not registered WorkflowNotRegisteredError fails the run when workflow does not exist
  • error handling not registered StepNotRegisteredError fails the step but workflow can catch it
  • error handling not registered StepNotRegisteredError fails the run when not caught in workflow
  • hookCleanupTestWorkflow - hook token reuse after workflow completion | wrun_01KNMHF707573TY2VWEG6X4DNH
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously | wrun_01KNMHFWK8Q44KY5E9X4R9ASHD
  • hookDisposeTestWorkflow - hook token reuse after explicit disposal while workflow still running | wrun_01KNMHGM9JGZWZSBXT32C90R37
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars) | wrun_01KNMHHA40QC8M5BFCX3WRN9DS
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument | wrun_01KNMHHKY5FCTHAD7DQ2RGH0AW
  • closureVariableWorkflow - nested step functions with closure variables | wrun_01KNMHHT09G8K4G7EG4F36D42G
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step | wrun_01KNMHHWDR6ZZGV5585HXJBY19
  • health check (queue-based) - workflow and step endpoints respond to health check messages
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly | wrun_01KNMHJBHXQHBXCB06Q1RQ364Z
  • Calculator.calculate - static workflow method using static step methods from another class | wrun_01KNMHJHYZ7X33V0S840FX5W9Q
  • AllInOneService.processNumber - static workflow method using sibling static step methods | wrun_01KNMHJRQ8QEZG1WYA9X4NE9G4
  • ChainableService.processWithThis - static step methods using this to reference the class | wrun_01KNMHJZB674R8TQ8TN8AA026X
  • thisSerializationWorkflow - step function invoked with .call() and .apply() | wrun_01KNMHK64J28XRFGM5X10GD015
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE | wrun_01KNMHKCJH3BSFD5V6A5DJSKV8
  • instanceMethodStepWorkflow - instance methods with "use step" directive | wrun_01KNMHKJXNGX0BC6AG4EP84PH0
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context | wrun_01KNMHKW4R2DSSHKGVJXT66ZGB
  • stepFunctionAsStartArgWorkflow - step function reference passed as start() argument | wrun_01KNMHM4QSV8SW6786SA9H6NFD
  • cancelRun - cancelling a running workflow | wrun_01KNMHMC10ES9NS6ZW9MAK03E4
  • cancelRun via CLI - cancelling a running workflow | wrun_01KNMHMMSK0AGPXGJR7JK82QDR
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router
  • hookWithSleepWorkflow - hook payloads delivered correctly with concurrent sleep | wrun_01KNMHMZYT36WW88RZPBQRKBH1
  • sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration | wrun_01KNMHNKEWEEQWTPPWGB7YNWSW
  • sleepWithSequentialStepsWorkflow - sequential steps work with concurrent sleep (control) | wrun_01KNMHNY2NHRBQ53J3TY57ZGSR
  • importMetaUrlWorkflow - import.meta.url is available in step bundles | wrun_01KNMHP4PAJEEA4DPSG64JC7M6
  • metadataFromHelperWorkflow - getWorkflowMetadata/getStepMetadata work from module-level helper (#1577) | wrun_01KNMHP6N2TBYR581JBV88ESXE
  • resilient start: addTenWorkflow completes when run_created returns 500 | wrun_01KNMHP8T5FNQQ8Z6MNZH87SNG
Details by Category
❌ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro7907
✅ example7907
✅ express7907
✅ fastify7907
❌ hono7817
✅ nextjs-turbopack8402
✅ nextjs-webpack8402
✅ nitro7907
✅ nuxt7907
✅ sveltekit7907
✅ vite7907
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable72014
✅ express-stable72014
✅ fastify-stable72014
✅ hono-stable72014
✅ nextjs-turbopack-canary61025
✅ nextjs-turbopack-stable7808
✅ nextjs-webpack-canary61025
✅ nextjs-webpack-stable7808
✅ nitro-stable72014
✅ nuxt-stable72014
✅ sveltekit-stable72014
✅ vite-stable72014
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable72014
✅ express-stable72014
✅ fastify-stable72014
✅ hono-stable72014
✅ nextjs-turbopack-canary61025
✅ nextjs-turbopack-stable7808
✅ nextjs-webpack-canary61025
✅ nextjs-webpack-stable7808
✅ nitro-stable72014
✅ nuxt-stable72014
✅ sveltekit-stable72014
✅ vite-stable72014
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable72014
✅ express-stable72014
✅ fastify-stable72014
✅ hono-stable72014
✅ nextjs-turbopack-canary61025
✅ nextjs-turbopack-stable7808
✅ nextjs-webpack-canary61025
✅ nextjs-webpack-stable7808
✅ nitro-stable72014
✅ nuxt-stable72014
✅ sveltekit-stable72014
✅ vite-stable72014
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack7808
❌ 🌍 Community Worlds
AppPassedFailedSkipped
❌ mongodb-dev410
❌ redis-dev410
❌ turso-dev410
❌ turso4578
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable72014
✅ e2e-local-postgres-nest-stable72014
✅ e2e-local-prod-nest-stable72014
📋 View full workflow run
❌ Some E2E test jobs failed:
  • Vercel Prod: failure
  • Local Dev: success
  • Local Prod: success
  • Local Postgres: success
  • Windows: success
Check the workflow run for details.
@VaguelySerious@claude
Include workflowCoreVersion in health check responses
51fb2ab
Both the HTTP (?__health) and queue-based health check endpoints
now return the @workflow/core package version, allowing observability
tools to identify exactly which SDK version a deployment is running.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious
VaguelySerious
merged commit a6bcea9
into
mainApr 7, 2026

92 of 99 checks passed

@VaguelySerious
VaguelySerious
deleted the

peter/cli-specversion-probe

branch
April 7, 2026 18:03
@ghostghost
mentioned this pull request
Apr 7, 2026
 Merged

VaguelySerious added a commit
that referenced
this pull request
Apr 7, 2026
@VaguelySerious
[cli] [core] Probe deployment specVersion before CLI start (#1629)
f0d6a85
@TooTallNateTooTallNate
mentioned this pull request
Apr 8, 2026
 Merged

7 tasks
@VaguelySeriousVaguelySerious
mentioned this pull request
Apr 16, 2026
 Closed

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

Reviewers

@TooTallNateTooTallNateTooTallNate approved these changes

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@VaguelySerious@TooTallNate

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
[cli] [core] Probe deployment specVersion before CLI start - #1629
Merged
VaguelySerious merged 17 commits into
mainfrom 
peter/cli-specversion-probe
Apr 7, 2026
Merged
[cli] [core] Probe deployment specVersion before CLI start#1629
VaguelySerious merged 17 commits into
mainfrom 
peter/cli-specversion-probe
Conversation
@VaguelySerious
@VaguelySeriousVaguelySerious
commented
Apr 7, 2026

Copy link


Copy Markdown

Member
Summary
Based on #1627. CLI start command now probes the target deployment's specVersion via health check before calling start(), ensuring the correct queue transport is used.
  • Health check always uses JSON transport (specVersion: SPEC_VERSION_LEGACY) so the probe works against both old and new deployments
  • Adds deploymentId option to HealthCheckOptions for targeted health checks
  • Falls back to the existing run's specVersion if health check fails (e.g. old deployment without health check support)
Other paths that call start() without knowing specVersion
Call siteKnows specVersion?Notes
CLI startNow probedThis PR
recreateRunFromExisting (web dashboard replay)YesUses run.specVersion from original run
User code (import { start } from 'workflow')N/ARuns ON the deployment, so SPEC_VERSION_CURRENT is correct
Testing server (world-testing)NoNot production-relevant
Test plan
  • packages/core unit tests pass (580/580)
  •  Full build passes
  •  e2e: CLI start against old deployment uses JSON transport
  •  e2e: CLI start against new deployment uses CBOR transport
  •  e2e: CLI start with health check timeout falls back to run specVersion
🤖 Generated with Claude Code
VaguelySeriousand others
added 13 commits
April 6, 2026 15:56
@VaguelySerious@claude
fix: gate queue transport format on specVersion for CBOR compat
8399d51
Bump SPEC_VERSION_CURRENT to 3 and fix isLegacySpecVersion to check
against SPEC_VERSION_LEGACY instead of SPEC_VERSION_CURRENT, preventing
v2 runs from being incorrectly treated as legacy when the version bumps.
Add JsonTransport and DualTransport to world-vercel queue: the handler
uses DualTransport (CBOR-first, JSON fallback) to accept messages from
both old and new deployments, while the send path selects CBOR or JSON
based on the target run's specVersion. Pass specVersion through queue
opts from start(), reenqueueRun(), wakeUpRun(), and resumeHook().
Only include runInput in the queue payload for specVersion >= 3, creating
clean separation between old and new behavior.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
[core] [world] Gate CBOR queue transport on specVersion
b6b6dcf
Bump specVersion to 3. Use JSON transport for queue messages targeting
older deployments (specVersion < 3), CBOR for new ones. Handler uses
dual transport that deserializes both formats, so new deployments can
receive messages from old and new senders.
Fixes replay/reenqueue from the dashboard to older deployments that
expect JSON queue messages.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Use named spec version constants for feature boundaries
dd2699b
Replace SPEC_VERSION_CURRENT comparisons with named constants
(SPEC_VERSION_SUPPORTS_CBOR_QUEUE_TRANSPORT, SPEC_VERSION_SUPPORTS_EVENT_SOURCING)
so future SPEC_VERSION_CURRENT bumps don't shift existing feature gates.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Update world-postgres test to use SPEC_VERSION_CURRENT
ddc8c31
Replace hardcoded specVersion: 2 with SPEC_VERSION_CURRENT so
the test tracks spec version bumps.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Include specVersion in health check responses
cf3dd88
Both the HTTP health check endpoint (?__health) and the queue-based
health check stream now return specVersion, allowing observability
tools to query deployment capabilities.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious
Merge branch 'main' into peter/cbor-transport-compat
50407fe
@VaguelySerious
fix health check test
330d70d
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@vercel@VaguelySerious
Fix: Health check e2e test assertions are missing the endpoint fiel…
82dcbe2
…d, causing `toEqual` to fail due to exact equality mismatch.
This commit fixes the issue reported at packages/core/e2e/e2e.test.ts:1550
**Bug explanation:**
The `withHealthCheck` handler in `packages/core/src/runtime/helpers.ts` returns a JSON response with three fields: `{ healthy: true, endpoint: url.pathname, specVersion: SPEC_VERSION_CURRENT }`. However, the HTTP-based health check e2e test in `packages/core/e2e/e2e.test.ts` (lines 1549-1553 and 1567-1571) uses `toEqual` to assert against objects that only have two fields: `{ healthy: true, specVersion: SPEC_VERSION_CURRENT }`, missing the `endpoint` field.
In Vitest, `toEqual` performs exact deep equality checking. When the actual response object contains `{ healthy: true, endpoint: "/.well-known/workflow/v1/flow", specVersion: "..." }` but the expected object only has `{ healthy: true, specVersion: "..." }`, the assertion fails because the actual object has an extra `endpoint` property not present in the expected object.
This affects both the flow endpoint health check assertion and the step endpoint health check assertion.
**Fix explanation:**
Added the missing `endpoint` field to both `toEqual` assertions:
- For the flow endpoint: `endpoint: '/.well-known/workflow/v1/flow'` (the pathname portion of `/.well-known/workflow/v1/flow?__health`)
- For the step endpoint: `endpoint: '/.well-known/workflow/v1/step'` (the pathname portion of `/.well-known/workflow/v1/step?__health`)
These values match what `url.pathname` returns in the handler (the `?__health` query parameter is not part of the pathname). This makes the test assertions exactly match the actual response structure from the handler.
Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Co-authored-by: VaguelySerious <mittgfu@gmail.com>
@VaguelySerious
fix
ce9ba33
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious
fix
57cb399
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious@claude
Propagate specVersion through queue-based health check result
419de89
Update HealthCheckResult to include specVersion and parse it from the
stream response, so observability tools can query deployment capabilities
through both the HTTP and queue-based health check paths.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
Fix TypeScript cast in parseHealthCheckResponse
ff8a79c
Use Record<string, unknown> instead of narrower casts that tsc
rejects as insufficient overlap.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious@claude
[cli] [core] Probe deployment specVersion before CLI start
7b42568
CLI start command now queries the deployment's health check endpoint
to determine its specVersion before calling start(). This ensures the
correct queue transport is used (JSON for old deployments, CBOR for
new). Falls back to the run's specVersion if health check fails.
Health check always uses JSON transport (specVersion: SPEC_VERSION_LEGACY)
so the probe works against both old and new deployments. Also adds
deploymentId option to HealthCheckOptions for targeted health checks.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@vercel
vercelBot
commented
Apr 7, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
The latest updates on your projects. Learn more about Vercel for GitHub.
ProjectDeploymentActionsUpdated (UTC)
example-nextjs-workflow-turbopackReadyReadyPreview, CommentApr 7, 2026 5:52pm
example-nextjs-workflow-webpackReadyReadyPreview, CommentApr 7, 2026 5:52pm
example-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-astro-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-express-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-fastify-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-hono-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-nitro-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-nuxt-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-sveltekit-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workbench-vite-workflowReadyReadyPreview, CommentApr 7, 2026 5:52pm
workflow-docsReadyReadyPreview, Comment, Open in v0Apr 7, 2026 5:52pm
workflow-swc-playgroundReadyReadyPreview, CommentApr 7, 2026 5:52pm
@VaguelySerious
VaguelySerious
requested a review
from a team
as a code ownerApril 7, 2026 00:22
@changeset-bot
changeset-botBot
commented
Apr 7, 2026•

edited

Loading

Copy link


Copy Markdown

🦋 Changeset detected
Latest commit: 51fb2ab
The changes in this PR will be included in the next version bump.
This PR includes changesets to release 16 packages
NameType
@workflow/corePatch
@workflow/cliPatch
@workflow/buildersPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/vitestPatch
@workflow/web-sharedPatch
workflowPatch
@workflow/world-testingPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch
@workflow/aiPatch
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
github-actionsBot
commented
Apr 7, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
🧪 E2E Test Results
❌ Some tests failed
Summary
PassedFailedSkippedTotal
❌ ▲ Vercel Production878167946
✅ 💻 Local Development85401781032
✅ 📦 Local Production85401781032
✅ 🐘 Local Postgres85401781032
✅ 🪟 Windows780886
❌ 🌍 Community Worlds1660884
✅ 📋 Other216042258
Total3750616594470
❌ Failed Tests
▲ Vercel Production (1 failed)
hono (1 failed):
🌍 Community Worlds (60 failed)
mongodb-dev (1 failed):
  • dev e2e should rebuild on imported step dependency change
redis-dev (1 failed):
  • dev e2e should rebuild on imported step dependency change
turso-dev (1 failed):
  • dev e2e should rebuild on imported step dependency change
turso (57 failed):
  • addTenWorkflow | wrun_01KNMH5VCWZ2YQDPP365WEZTM4
  • addTenWorkflow | wrun_01KNMH5VCWZ2YQDPP365WEZTM4
  • wellKnownAgentWorkflow (.well-known/agent) | wrun_01KNMH75H1GT8X09J9WS5F6FA6
  • should work with react rendering in step
  • promiseAllWorkflow | wrun_01KNMH63YAHQKDCZQT1EPYKGX8
  • promiseRaceWorkflow | wrun_01KNMH699ZAQD55FBQV3XNHM7X
  • promiseAnyWorkflow | wrun_01KNMH6C1XSP0EZ96TT0J5E8PF
  • importedStepOnlyWorkflow | wrun_01KNMH7GSJTNP0DX1PGSPFNTZZ
  • hookWorkflow | wrun_01KNMH6S06RS6VXGS41PF3GWSB
  • hookWorkflow is not resumable via public webhook endpoint | wrun_01KNMH76KMG0ZCB7ST88V553JE
  • webhookWorkflow | wrun_01KNMH7H30FD15T64RRS74743D
  • sleepingWorkflow | wrun_01KNMH7TG251JCYH1HS6DV9PKV
  • parallelSleepWorkflow | wrun_01KNMH87BSQPDNQBW8RR8GMHVR
  • nullByteWorkflow | wrun_01KNMH8B46P0EM2F1T1T2EQT07
  • workflowAndStepMetadataWorkflow | wrun_01KNMH8DKDK9H0CTSMSMJYV7J1
  • fetchWorkflow | wrun_01KNMHBA5EJNGZ9Y10R47QQ7TS
  • promiseRaceStressTestWorkflow | wrun_01KNMHBD0VT8JK2JD5N8JDTNTX
  • 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()
  • error handling not registered WorkflowNotRegisteredError fails the run when workflow does not exist
  • error handling not registered StepNotRegisteredError fails the step but workflow can catch it
  • error handling not registered StepNotRegisteredError fails the run when not caught in workflow
  • hookCleanupTestWorkflow - hook token reuse after workflow completion | wrun_01KNMHF707573TY2VWEG6X4DNH
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously | wrun_01KNMHFWK8Q44KY5E9X4R9ASHD
  • hookDisposeTestWorkflow - hook token reuse after explicit disposal while workflow still running | wrun_01KNMHGM9JGZWZSBXT32C90R37
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars) | wrun_01KNMHHA40QC8M5BFCX3WRN9DS
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument | wrun_01KNMHHKY5FCTHAD7DQ2RGH0AW
  • closureVariableWorkflow - nested step functions with closure variables | wrun_01KNMHHT09G8K4G7EG4F36D42G
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step | wrun_01KNMHHWDR6ZZGV5585HXJBY19
  • health check (queue-based) - workflow and step endpoints respond to health check messages
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly | wrun_01KNMHJBHXQHBXCB06Q1RQ364Z
  • Calculator.calculate - static workflow method using static step methods from another class | wrun_01KNMHJHYZ7X33V0S840FX5W9Q
  • AllInOneService.processNumber - static workflow method using sibling static step methods | wrun_01KNMHJRQ8QEZG1WYA9X4NE9G4
  • ChainableService.processWithThis - static step methods using this to reference the class | wrun_01KNMHJZB674R8TQ8TN8AA026X
  • thisSerializationWorkflow - step function invoked with .call() and .apply() | wrun_01KNMHK64J28XRFGM5X10GD015
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE | wrun_01KNMHKCJH3BSFD5V6A5DJSKV8
  • instanceMethodStepWorkflow - instance methods with "use step" directive | wrun_01KNMHKJXNGX0BC6AG4EP84PH0
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context | wrun_01KNMHKW4R2DSSHKGVJXT66ZGB
  • stepFunctionAsStartArgWorkflow - step function reference passed as start() argument | wrun_01KNMHM4QSV8SW6786SA9H6NFD
  • cancelRun - cancelling a running workflow | wrun_01KNMHMC10ES9NS6ZW9MAK03E4
  • cancelRun via CLI - cancelling a running workflow | wrun_01KNMHMMSK0AGPXGJR7JK82QDR
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router
  • hookWithSleepWorkflow - hook payloads delivered correctly with concurrent sleep | wrun_01KNMHMZYT36WW88RZPBQRKBH1
  • sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration | wrun_01KNMHNKEWEEQWTPPWGB7YNWSW
  • sleepWithSequentialStepsWorkflow - sequential steps work with concurrent sleep (control) | wrun_01KNMHNY2NHRBQ53J3TY57ZGSR
  • importMetaUrlWorkflow - import.meta.url is available in step bundles | wrun_01KNMHP4PAJEEA4DPSG64JC7M6
  • metadataFromHelperWorkflow - getWorkflowMetadata/getStepMetadata work from module-level helper (#1577) | wrun_01KNMHP6N2TBYR581JBV88ESXE
  • resilient start: addTenWorkflow completes when run_created returns 500 | wrun_01KNMHP8T5FNQQ8Z6MNZH87SNG
Details by Category
❌ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro7907
✅ example7907
✅ express7907
✅ fastify7907
❌ hono7817
✅ nextjs-turbopack8402
✅ nextjs-webpack8402
✅ nitro7907
✅ nuxt7907
✅ sveltekit7907
✅ vite7907
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable72014
✅ express-stable72014
✅ fastify-stable72014
✅ hono-stable72014
✅ nextjs-turbopack-canary61025
✅ nextjs-turbopack-stable7808
✅ nextjs-webpack-canary61025
✅ nextjs-webpack-stable7808
✅ nitro-stable72014
✅ nuxt-stable72014
✅ sveltekit-stable72014
✅ vite-stable72014
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable72014
✅ express-stable72014
✅ fastify-stable72014
✅ hono-stable72014
✅ nextjs-turbopack-canary61025
✅ nextjs-turbopack-stable7808
✅ nextjs-webpack-canary61025
✅ nextjs-webpack-stable7808
✅ nitro-stable72014
✅ nuxt-stable72014
✅ sveltekit-stable72014
✅ vite-stable72014
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable72014
✅ express-stable72014
✅ fastify-stable72014
✅ hono-stable72014
✅ nextjs-turbopack-canary61025
✅ nextjs-turbopack-stable7808
✅ nextjs-webpack-canary61025
✅ nextjs-webpack-stable7808
✅ nitro-stable72014
✅ nuxt-stable72014
✅ sveltekit-stable72014
✅ vite-stable72014
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack7808
❌ 🌍 Community Worlds
AppPassedFailedSkipped
❌ mongodb-dev410
❌ redis-dev410
❌ turso-dev410
❌ turso4578
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable72014
✅ e2e-local-postgres-nest-stable72014
✅ e2e-local-prod-nest-stable72014
📋 View full workflow run
❌ Some E2E test jobs failed:
  • Vercel Prod: failure
  • Local Dev: success
  • Local Prod: success
  • Local Postgres: success
  • Windows: success
Check the workflow run for details.
@VaguelySerious@claude
Include workflowCoreVersion in health check responses
51fb2ab
Both the HTTP (?__health) and queue-based health check endpoints
now return the @workflow/core package version, allowing observability
tools to identify exactly which SDK version a deployment is running.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@VaguelySerious
VaguelySerious
merged commit a6bcea9
into
mainApr 7, 2026

92 of 99 checks passed

@VaguelySerious
VaguelySerious
deleted the

peter/cli-specversion-probe

branch
April 7, 2026 18:03
@ghostghost
mentioned this pull request
Apr 7, 2026
 Merged

VaguelySerious added a commit
that referenced
this pull request
Apr 7, 2026
@VaguelySerious
[cli] [core] Probe deployment specVersion before CLI start (#1629)
f0d6a85
@TooTallNateTooTallNate
mentioned this pull request
Apr 8, 2026
 Merged

7 tasks
@VaguelySeriousVaguelySerious
mentioned this pull request
Apr 16, 2026
 Closed

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

Reviewers

@TooTallNateTooTallNateTooTallNate approved these changes

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@VaguelySerious@TooTallNate