Major-version refs like `@v2`/`@v5` resolve to mutable refs on the
upstream repos — sometimes a tag, sometimes a branch (e.g. marocchino
keeps `v1`/`v2`/`v3` as branches), and dawidd6 force-pushes the bare
`v6` tag forward outside of releases. A compromised maintainer account
could push new code that our CI picks up on the next run with
GITHUB_TOKEN (or, for changesets/action, NPM_TOKEN) in hand.
Pin all third-party `uses:` references to full commit SHAs with a
trailing version comment so the upstream release is still visible to
reviewers. Dependabot/Renovate can keep these fresh going forward.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* ci(backport): mark not-maintained-on-stable list as exhaustive and require git verification
The backport workflow's AI decision prompt only listed `docs/` (outside
`docs/content/`) and `skills/` as paths not maintained on `stable`, but
didn't flag that list as exhaustive. On at least one commit, the AI
generalized the pattern and incorrectly claimed `tarballs/` was also
not maintained on `stable` (it is) — likely because the commit subject
mentioned "preview tarball" and the changed files included a docs
preview smoke check workflow.
Tighten the prompt to:
- explicitly mark the not-maintained list as exhaustive;
- instruct the AI to run `git ls-tree origin/stable -- <path>` to
verify any other path it wants to cite as main-only;
- warn it not to infer main-only-ness from suggestive names like
"docs", "preview", "tarball", or "workflow".
* ci(backport): link to the backport job run in posted comments and PR body
Each of the comments the backport workflow posts (no-backport,
backport-created, conflict-failure) and the body of the backport PR
it opens now includes a link to the GitHub Actions run that produced
the decision. Makes it easy to jump from the comment straight to the
opencode output, prompt, and AI reasoning when the AI gets a call wrong.
The repo's enterprise `~ALL` required-signatures ruleset rejects the
unsigned commits produced by `peaceiris/actions-gh-pages@v4`, breaking
the benchmark and E2E result publishing jobs on `main`. Replace those
steps with a shared composite action that uses the GraphQL
`createCommitOnBranch` mutation — same pattern already used by
`backport.yml` — so commits are signed automatically by GitHub and
satisfy the rule.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The test server's flow handler awaited flowPOST before incrementing the
invocation counter, which races with the test polling getRun() to see
the completed status. When the workflow completed inside flowPOST and
flushed the run to the DB, the test could observe the completed state
and immediately query /_flow-invocations before the counter was bumped,
yielding a flaky 'expected 0 to be 1' assertion.
Increment the counter before awaiting flowPOST so the count is
observable as soon as the run transitions to completed.
* Forward port stale wait replay fix
* Guard V5 replay writes against stale events
* Revert "Guard V5 replay writes against stale events"
This reverts commit 22e74d3558.
* Update wait replay comments
Sets pnpm's `minimumReleaseAge` to 2 days (company-wide standard) and
excludes internal scopes from the gate.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Shiki wraps each highlighted token in its own <span>, which breaks Geist
Mono programming ligatures like `===`, `!==`, `=>`. The ligature glyph is
rendered at the advance width of a single character (~8.4px) instead of
three (~25.2px), causing it to visually overlap the preceding token.
Disable `font-variant-ligatures` inside `pre code` so each character
renders at its true monospace width.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(world-postgres): bootstrap graphile-worker schema in setup CLI
`workflow-postgres-setup` now installs the `graphile_worker` schema in
addition to the drizzle migrations so that by the time any consumer
calls `world.start()`, both schemas already exist. This eliminates the
inter-process race on graphile-worker's `installSchema` where
concurrent `CREATE SCHEMA IF NOT EXISTS` calls could both pass the
MVCC-snapshotted existence check and one would fail with
`duplicate key value violates unique constraint "pg_namespace_nspname_index"`.
Reproduced locally against a fresh postgres:18-alpine with 8 parallel
`makeWorkerUtils().migrate()` calls — 7/8 fail without the pre-bootstrap,
0/8 fail after running `workflow-postgres-setup` first.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* Apply suggestions from code review
Co-authored-by: Peter Wielander <mittgfu@gmail.com>
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
---------
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-authored-by: Nathan Rajlich <n@n8.io>
* Expose conflicting run id on hook conflicts
* Mark hook conflict run id as future required
* Address hook conflict docs review
* Address hook conflict review comments
* Fix hook conflict docs typecheck
Use Tailwind's typed arbitrary duration syntax for trace viewer zoom controls so Tailwind v3 consumers do not emit ambiguous utility warnings when scanning the package.
* drop setup-command input from reusable community-world workflows
The community-world matrix is produced by running
scripts/create-community-worlds-matrix.mjs in the fork PR's checkout,
so any field on it is attacker-controlled. Forwarding
matrix.world.setup-command into the reusable workflow and eval-ing it
let a malicious fork PR execute arbitrary shell on the runner.
Replace the pass-through with a hardcoded per-world-id case in the
reusable workflows (only turso currently needs a setup step) and drop
the setup field from the matrix generator.
* rename step to "Per-world setup"
Addresses Copilot review feedback: the step no longer executes an
arbitrary command, so the old name was misleading.
Register the Fantastic Four community world packages in the worlds manifest and show the Redis variants in the Embedded docs section.
Signed-off-by: Pranay Prakash <pranay.gp@gmail.com>
Co-authored-by: Pranay Prakash <pranay.gp@gmail.com>
The AI SDK renamed `Experimental_Agent` to `ToolLoopAgent`. Update the
"Building Durable AI Agents" page's API route snippet (v4 and v5) so it
matches the current AI SDK API.
Co-authored-by: Cursor <cursoragent@cursor.com>
Drops the label-based backport override in favor of workflow_dispatch.
The pull_request_target trigger has security concerns (it runs with
write permissions on PR-controlled events), and we already have a
manual dispatch path that covers the same use case.
* Update workflow-trace-view.tsx
* Update trace viewer layout to be in a row
Signed-off-by: Mitul Shah <mitulxshah@gmail.com>
---------
Signed-off-by: Mitul Shah <mitulxshah@gmail.com>
Large backport prompts (commit message + diff capped at 200KB) can
exceed Linux's `ARG_MAX` and cause `opencode run` to fail with
"Argument list too long" (exit 126). Redirect the prompt files into
`opencode run`'s stdin instead of passing them on the command line.
* docs: split v4/v5 content, fix version switcher end-to-end
## Content restructuring
- Split `docs/content/docs/` into `docs/content/docs/v4/` and
`docs/content/docs/v5/` so each version is a fully independent
content tree with no shared-file coupling
- v4 excludes the four pages that are v5-only (AbortController
cancellation docs and the serializable-abort-controller internal page)
- v5 retains all pages; `preRelease` frontmatter field removed (no
longer needed now that each version is its own folder)
- Removed `AbortController` / `AbortSignal` from v4 serialization page
(section moved to v5 only)
## Fumadocs source
- Added `v4docs` and `v5docs` as separate `defineDocs()` collections in
`source.config.ts`; shared `docsSchema` (no more `preRelease` field)
- `source.ts` exports both `source` (v4, `baseUrl: /docs`) and
`v5Source` (v5, same base URL)
## Version routing
- `version-source.ts` simplified: `filterPreReleaseFromNodes` and
`isPreReleaseUrl` logic removed; v4 tree uses `source`, v5 tree uses
`v5Source` + `rewriteNodeUrls`
- v4 `page.tsx`: removed `preRelease` guard (v4Source has no such pages)
- v5 `page.tsx`: uses `v5Source` for `getPage` / `generateStaticParams`
/ `generateMetadata`; `v5Link` wrapper rewrites `/docs/…` hrefs to
`/v5/docs/…` so inline MDX links stay in the v5 context
## Versioned cookbook
- Added `app/[lang]/v5/cookbook/` layout + page (mirrors v4 but uses
`v5Source`, `rewriteCookbookUrlForVersion`, and `V5CookbookLink`)
- `getCookbookTree` accepts a `versionPrefix` parameter; sidebar URLs
are prefixed accordingly (`/v5/cookbook/…`)
- `cookbook-tree.ts`: added `skipVersions?: string[]` per-recipe field
for version-specific exclusions; `distributed-abort-controller` is
marked `skipVersions: ['v5']`
## Version switcher — state & navigation
- New `VersionProvider` context (`hooks/geistdocs/use-version.tsx`)
backed by `localStorage`: URL is source of truth on versioned pages,
`localStorage` carries the preference across non-versioned pages
(cookbook overview, worlds, etc.)
- `VersionSwitcher` uses `useVersion()` context instead of URL-only
detection; now visible on all pages including cookbook
- `DesktopMenu` and `MobileMenu` use `activeVersion` from context so
the "Docs" and "Cookbook" navbar links resolve to the correct version
prefix on every page
- `buildVersionUrl` expanded to handle `/cookbook/…` paths alongside
`/docs/…`; non-versioned routes (worlds, api) return unchanged
- `switchVersion` does a `HEAD` probe before navigating; falls back to
the versioned cookbook or docs home if the target page doesn't exist
in that version (handles v4-only → v5 and v5-only → v4 cases)
## Cookbook content (v5)
- Rewrote `agent-cancellation` recipe using a single `AbortController`
pattern; removed Hard Cancellation vs Stop Signal two-approach
comparison
- Deleted `distributed-abort-controller` recipe from v5 (native
`AbortController` serialization makes it unnecessary)
- Removed references to distributed-abort-controller from
`cookbook/index.mdx` and `common-patterns/timeouts.mdx`
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(docs): use abortSignal (not signal) in DurableAgent.stream() options
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(docs): update prepack scripts to use versioned content paths
Content moved from docs/content/docs/ to docs/content/docs/v5/ on main
(pre-release channel). Stable branch will use v4/ after backport.
Co-authored-by: Cursor <cursoragent@cursor.com>
---------
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(web-shared): hydrate FatalError/RetryableError and Error subclasses in o11y
The web o11y reviver set was missing entries for the recently-added
serialization types (FatalError, RetryableError, the built-in Error
subclasses, AggregateError, DOMException), causing devalue.unflatten to
throw "Unknown type X" and the UI to surface "Failed to load resource
details" whenever a step or run failed with one of these error types.
Adds the missing revivers to getWebRevivers() and a regression test that
round-trips real values through the runtime's dehydrateStepError back
through the web reviver set.
* fix(web-shared): address review feedback on error revivers
- Pass `cause` through ErrorOptions to the subclass constructor instead of
assigning afterwards, matching `getCommonRevivers` in core. This gives
the resulting `cause` property the same engine-set, non-enumerable
semantics as a freshly thrown Error in the consumer realm.
- Guard `RetryableError.retryAfter` against missing/undefined values from
older runtime payloads — without it, `new Date(undefined)` produces an
Invalid Date rather than the property being absent. Add a defensive
test that drives the reviver directly with a payload missing the field.
* [swc-plugin] Preserve imports referenced by hoisted nested steps
Dead-code elimination ran before nested step functions were hoisted out of workflow bodies, so imports referenced only by hoisted step bodies were incorrectly stripped from the step bundle, causing a ReferenceError at runtime. Move DCE to run after hoisting in visit_mut_program.
* [swc-plugin] Namespace nested step IDs under non-exported workflow functions
Anonymous steps nested inside callback properties of a non-exported workflow function were registered with an unnamespaced step ID in step mode while the workflow-mode proxy looked them up under the workflow function name, causing a runtime 'step not found' failure. Set current_workflow_function_name in visit_mut_fn_decl for non-exported workflow functions to match the behavior in visit_mut_export_decl. Also clarify the fixture comment to distinguish step-mode and workflow-mode behavior per reviewer feedback.
* [swc-plugin] Namespace nested step IDs across all workflow declaration shapes
Extends the previous fix to cover all three non-exported workflow declaration forms (async function decl, const arrow, const fn-expr) by visiting the workflow body with workflow context before replacing it, and corrects the __internal_workflows manifest comment to report the same prefixed step IDs that are registered at runtime and looked up by the workflow-mode WORKFLOW_USE_STEP proxy. Adds a dedicated regression fixture covering all three shapes.
* Hoist AI model env, fix opencode external_directory permission, fail loud on AI infra errors
Three related fixes triggered by the failed run on #1935:
1. Hoist the AI model name to a top-level `AI_MODEL` env var
(`anthropic/claude-opus-4.7`); both `opencode run` invocations
now interpolate `vercel/${AI_MODEL}` so the model is specified in
exactly one place.
2. Switch `OPENCODE_PERMISSION` from the bare-string shortcut
`"allow"` to the explicit object form
`{"*":"allow","external_directory":"allow"}`. The shortcut
was observed not to override `external_directory` (which defaults to
"ask" and auto-rejects in non-interactive `opencode run`),
causing the conflict-resolution AI to fail when reading scratch files
it created under `/tmp/`.
3. The `Resolve conflicts with opencode` step no longer uses
`continue-on-error`, and now distinguishes two outcomes via an AI-
written outcome file (`.backport-conflict-outcome.json`):
- `{"status":"resolved"}` — the legitimate clean path; cherry-pick
continues and the backport PR is opened.
- `{"status":"unresolved", ...}` — the legitimate "AI couldn't
do it, hand off to a human" path; `resolved=false` is set and the
conflict-failure comment is posted on the source PR.
- Anything else (missing file, malformed JSON, unknown status) is
treated as an opencode/AI Gateway infra failure: the step exits
non-zero, the workflow fails red, and the misleading
"couldn't resolve" comment is suppressed.
The prompt + scratch files are also moved into the workspace so
opencode never needs `external_directory` access anyway.
* Allow manual workflow_dispatch with ref+model inputs; use AI_MODEL in PR body
Add a `workflow_dispatch` trigger to the backport workflow with two
optional inputs:
- `ref` — commit SHA on `main` to back-port (defaults to `main` HEAD)
- `model` — overrides the default AI model used by opencode for the
decision and conflict-resolution steps (defaults to the workflow's
hardcoded `AI_MODEL`)
The top-level `AI_MODEL` env var now uses
`${{ inputs.model || 'anthropic/claude-opus-4.7' }}` so manual runs
pick up the override without changing anything else.
Manual dispatch (like the `backport-stable` label) always forces a
backport regardless of any AI verdict — the operator's intent is
explicit by virtue of triggering the workflow. The PR body shows
"Triggered manually via `workflow_dispatch`." in that case.
The PR body's conflict-resolution attribution also now interpolates
`${AI_MODEL}` (e.g. "opencode with `anthropic/claude-opus-4.7`")
instead of hardcoding "Claude Opus" so the text stays accurate if the
default model is later changed.
* Address PR review: also detect leftover conflict markers in staged files
The previous `Resolve conflicts with opencode` sanity check used
`git diff --diff-filter=U` to detect unresolved cherry-pick conflicts,
which only catches unmerged index entries. That misses the case where
the AI runs `git add` on a file that still has `<<<<<<<` /
`=======` / `>>>>>>>` markers in its content — git happily stages
the broken file as a normal modification.
Add a second check using `git diff --check --cached`, which emits
`leftover conflict marker` lines when any staged content still has
the standard markers. Grep specifically for that phrase so unrelated
whitespace warnings don't trip the check. Also update the inline
comment to accurately describe what each check covers (per Copilot's
review on #1943).
* [swc-plugin] Capture lexical `this` for nested arrow step functions
When a nested arrow `"use step"` references the enclosing function/method's
`this`, plumb that `this` through the workflow runtime so the step body
sees the correct receiver.
- Workflow mode wraps the step proxy with `.bind(this)`, so invoking the
proxy captures the caller's `this` as `thisVal` on the queue item.
- Step mode hoists the body as a regular `function` (not an arrow) so the
runtime's `stepFn.apply(thisVal, args)` rebinds `this` inside the
hoisted body.
Detection only fires for arrows, since arrows inherit `this` lexically.
Nested non-arrow functions/methods/getters/setters introduce their own
`this`, so the detector stops at those boundaries.
The runtime already supported `thisVal` for instance-method steps; this
PR is purely a compiler change to feed the existing pipeline.
Caveat: capture works at runtime only when the captured value is
serializable across the workflow->step boundary (i.e. the enclosing
class implements `WORKFLOW_SERIALIZE`/`WORKFLOW_DESERIALIZE`).
Refs vercel/workflow#1865
* Address PR review: preserve step proxy metadata + tighter `this` detection
- core: Override `.bind` on step proxies so the bound function retains
`stepId` and `__closureVarsFn`. Without this, a bound proxy that flows
through workflow serialization (e.g. as a step argument) would be
treated as a non-serializable plain function by `getStepFunctionReducer`.
- swc-plugin: Detector now also walks `arrow.params` so `this` references
in default values / destructuring initializers (e.g. `(x = this.foo) =>
...`) trigger the `.bind(this)` path.
- swc-plugin: Class bodies inside the arrow body are now treated as
`this`-binding boundaries — `this` inside class field initializers,
methods, etc. is bound to the class instance, not the outer arrow. The
detector still walks `extends` clauses and computed property keys
because those are evaluated in the surrounding scope.
- spec.md: Sharpen the note about `this` in step bodies — it's
syntactically allowed but only meaningful for instance-method steps and
lexical-`this` arrow steps; other shapes compile but `this` will be
whatever the caller of the step proxy passes.
- Add `lexical-this-detector-edge-cases` fixture covering both the
default-param positive case and the inner-class false-positive guard.
- Strengthen the runtime test to assert `stepId` / `__closureVarsFn`
survive `.bind(...)`.
* [swc-plugin] Fix `arguments` closure-var capture; drop dead `this`/`arguments` checks
- Add `arguments` to `is_global_identifier` so it's not captured as a
closure variable. Previously a nested `function`-form step like
function step() { 'use step'; return arguments[0]; }
was hoisted with `const { arguments } = ...` (a strict-mode syntax
error) and the body's `arguments[0]` resolved against the destructured
binding instead of the function's intrinsic `arguments` object.
- Remove dead `ForbiddenExpression` checks for `this` and `arguments` in
`visit_mut_this_expr` / `visit_mut_ident`. The `'use step'` /
`'use workflow'` directives are stripped during the module-level
traversal before children are visited, so `in_step_function` /
`in_workflow_function` are never observed as true here in practice.
The existing `step-with-this-arguments-super` fixture explicitly
documents that all three identifiers are allowed in step bodies.
- Tighten the spec note about `arguments` accordingly: it works in
`function`-form steps (reflecting positional args) but is not captured
for arrow-form steps; use `...args` for that case.
- Add `nested-step-arguments` fixture pinning down the new behavior.
The geistdocs facelift (#1666) dropped the VERCEL_ENV-based filter on
nav items, so the "Internal" entry (preview: true) was visible on the
production docs deployment. Restore the filter in the server-rendered
Navbar and pass the filtered list to MobileMenu so both desktop and
mobile honor it.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* feat: add docs and test stubs for serializable AbortController/AbortSignal
Adds documentation and test infrastructure for making AbortController and
AbortSignal serializable across workflow and step boundaries. The feature
uses a dual hook+stream backing: hooks for deterministic replay in the
workflow context, streams for real-time propagation to running steps.
Docs:
- Cancellation guide (foundations) covering AbortSignal and run cancellation
- How Cancellation Works (how-it-works) explaining hook+stream internals
- AbortSignal.timeout() error page for the workflow VM restriction
- Updated serialization docs with AbortController/AbortSignal section
Tests (all .todo stubs for TDD):
- VM behavior: AbortController API, static methods, hook integration
- Step-side: stream reader setup, abort propagation, ops queue
- Serialization round-trips: all boundaries, encryption, nested structures
- Consistency: race conditions, partial failure, eventual convergence
- E2E workflows: timeout, parallel, step-initiated, hook-triggered, replay
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix: use correct frontmatter type for error page
Change type from "error" to "troubleshooting" to match the valid
frontmatter schema used by all other error pages.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* docs: address review feedback on cancellation docs
- abort() in workflow does not synchronously update signal.aborted;
instead it queues hook resumption and the replay handles state update
- stream name and hook token are generated at serialization time (not
deterministically in the workflow) and stored in the event log
- use throwIfAborted() instead of manual signal.aborted checks
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* docs: document runtime change for processing abort queue items on completion
The current runtime only processes invocation queue items on suspension.
When abort() is called after the last suspension point and the workflow
completes, the queue items are dropped with a warning. Document that the
runtime needs to flush abort-related items on completion/failure too.
Add test stubs for this behavior.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* docs: generalize queue processing on completion to all item types
Processing pending invocations queue items on workflow completion/failure
should apply to all queue item types (steps, hooks, waits, abort signals),
not just abort-related ones. Update docs and tests accordingly.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* docs: abort errors in steps are automatically wrapped in FatalError
When a step throws due to an abort (AbortError from fetch, throwIfAborted,
etc.), the error is wrapped in FatalError so the step skips retries. An
abort is intentional cancellation, not a transient failure.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* docs: remove contrived "aborting from within a step" example
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* docs: add meaningful step-initiated abort example (quota monitor)
Replace the contrived example with a watchdog pattern where a monitoring
step polls an external condition and aborts parallel work when triggered.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* docs: remove unnecessary "as const" from hook cancellation example
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* feat: implement serializable AbortController/AbortSignal
Core serialization layer:
- Add AbortController/AbortSignal to SerializableSpecial interface
- Add reducers for all 4 contexts (external, workflow, step, common)
- Add revivers for all 4 contexts with stream-backed propagation
- Add reviveAbortController helper for step/external contexts
- Guard instanceof checks for VMs without AbortController global
Workflow VM:
- New workflow/abort-controller.ts with createCreateAbortController factory
- WorkflowAbortSignal class with hook-backed state
- AbortSignal static methods (abort, any, timeout blocked)
- Hook integration via invocations queue and events consumer
Supporting changes:
- Add ABORT_STREAM_NAME, ABORT_HOOK_TOKEN symbols
- Add getAbortStreamId() for system stream namespace
- Add isSystem, abortRequested, abortReason to HookInvocationQueueItem
- Add isSystem to world Hook entity and events
- Wrap AbortError in FatalError in step handler (skip retries)
- Add AbortController/AbortSignal to Serializable type
- Add observability revivers for abort types
- Add isSystem to postgres schema and web-shared attribute panel
All 454 existing tests pass with no regressions.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* feat: wire up AbortController in workflow VM and process queue on completion
- Wire up AbortController/AbortSignal in workflow VM (workflow.ts)
- Add abort processing to suspension handler (hook resume + stream write)
- Process pending queue items on workflow completion (throw
WorkflowSuspension instead of warning for actionable items)
- Fix instanceof guards for non-function AbortSignal in VM
- Update test to expect WorkflowSuspension for unawaited steps
All 454 existing tests pass.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* feat: implement tests and Request.signal serialization
Tests (516 passing, 18 todo for integration tests):
- 18 VM behavior tests (abort-controller.test.ts)
- 18 step-side behavior tests (abort-controller-step.test.ts)
- 4 consistency tests + 14 integration todos (abort-consistency.test.ts)
- 14 serialization round-trip tests (serialization.test.ts)
- 7 hook integration + 4 integration todos (step.test.ts)
Request.signal serialization:
- Add signal field to SerializableSpecial Request type
- Include signal in Request reducer when present
- Pass signal through in external and step Request revivers
Fix workflow reviver for AbortController/AbortSignal:
- Use plain objects instead of prototype-based stubs
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* test: implement all remaining .todo test stubs
Convert all 27 remaining .todo stubs to real implementations:
- 14 consistency tests (race conditions, partial failures, queue processing)
- 4 hook integration tests (suspension handler, hydration, eventual consistency)
- 9 e2e tests (timeout, parallel, step-abort, hook-cancel, replay, external signal)
All 558 tests pass, 0 todos remaining.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix: address PR review comments + add changelog
PR review fixes:
- Move cancellation after streaming in foundations nav
- Fix AbortSignal reducer to detect WorkflowAbortSignal via symbol
- Guard AbortController reducer from matching AbortSignal objects
- Add e2e tests: throwIfAborted, reason types, uncaught fetch AbortError
Changelog:
- Add hidden changelog section (not in sidebar, accessible via URL)
- Add draft changelog entry for serializable AbortController/AbortSignal
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* feat: show changelog in nav for preview deployments only
- Add `preview` flag to nav items in geistdocs.tsx
- Filter preview items in Navbar (server component) based on VERCEL_ENV
- Show "Preview" badge on preview nav items in DesktopMenu
- Changelog link visible in preview deployments and local dev only
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* feat: move preview badge from home page to navbar
Move the PreviewBadge (with package tarball install modal) from the
fixed bottom-right position on the home page to the navbar, so it
appears on every page during preview deployments.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* feat: consolidate preview tools into single Internal page
Replace separate Changelog nav item and PreviewBadge with a single
"Internal" page that only appears in preview deployments:
- Rename docs/changelog/ to docs/internal/
- Internal page includes preview package install commands and draft
changelogs in one place
- Nav shows "Internal" with Preview badge in preview/dev only
- Remove PreviewBadge from navbar (now on the Internal page)
- Add callout that page is preview-only
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* feat: use real deployment URLs on internal page + exclude from indexing
- Add PreviewInstall component with copy-to-clipboard buttons using
the actual VERCEL_URL (not placeholders)
- Register PreviewInstallServer as MDX component for docs pages
- Exclude /internal/ pages from sitemap.xml, sitemap.md, and llms.mdx
- Add robots.txt Disallow for /internal/ paths
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix: add missing type declarations for docs code sample typechecking
Add declare statements and @setup/@skip-typecheck annotations for
undeclared functions in code samples (stepA, stepB, fetchData,
cancellableStep, splitIntoChunks, processChunk).
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix: add missing type declarations for all docs code samples
Fix docs typecheck CI by adding declare statements and
@skip-typecheck annotations for all undeclared function references
across cancellation docs, error page, how-it-works page, and
internal changelog.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix: only suspend on completion for abort items, not all pending items
The previous logic threw WorkflowSuspension for any pending queue item
on completion (steps, waits, hooks). This broke fire-and-forget patterns
like `void sleep('1d').then(...)` which intentionally leave a wait in
the queue without awaiting it.
Now only abort-related items (hooks with abortRequested) trigger
suspension on completion. Other pending items get the original warning
behavior — they may be intentional fire-and-forget operations.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix: all pending queue items are fire-and-forget on completion
Remove special-case suspension for abort items on workflow completion.
ALL pending queue items (steps, hooks, waits, abort signals) are now
fire-and-forget when the workflow completes — they get warned about
but don't block completion. This matches the existing behavior for
fire-and-forget patterns like `void sleep('1d').then(...)`.
Abort signals propagate through the normal suspension flow during
the workflow (not at completion time).
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix: resolve docs typecheck errors in code samples
Move declare statements before imports to avoid TypeScript overload
signature conflicts with auto-inferred imports. Add @skip-typecheck
for conceptual snippets.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix: abort() in workflow updates signal.aborted synchronously
abort() must update signal.aborted immediately so that:
1. Subsequent reads in the workflow see the correct state
2. Serialization captures aborted=true when passing signal to steps
3. Event listeners fire synchronously
The hook resumption still happens via the suspension handler for
durable event log recording. Both local state and durable state
are now updated.
Fixes e2e failures where steps received aborted=false for signals
that were aborted before being passed to the step.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* docs: update how-it-works to reflect synchronous signal.aborted update
abort() now updates signal.aborted synchronously in the workflow.
Update lifecycle diagram and remove outdated paragraph about signal
not being updated synchronously.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix: ensure abort listeners fire at deterministic point across replays
On replay, hook_received is processed during event consumer subscription
(at AbortController construction time), which is BEFORE the abort() call
in the workflow code. If listeners fired during event processing, they'd
fire at a different point than on first-run — breaking determinism.
Solution: split abort into two phases:
1. _markAbortedFromReplay(): Sets signal.aborted=true (for reads/serialization)
but does NOT fire listeners. Called by event consumer during replay.
2. abort(): Detects the replay flag and fires listeners at the call site.
On first-run, fires listeners immediately as before.
This ensures listeners fire at the abort() call site on BOTH first-run
and replay, maintaining consistent ordering of side effects.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* test: add replay ordering tests for interleaved hook scenarios
Add 3 tests validating that abort listeners fire at the abort() call
site on both first-run and replay, even when other hook events are
interleaved in the event log.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix: signal.aborted stays false until abort() is called for deterministic replay
_markAbortedFromReplay no longer sets signal.aborted = true. Both
aborted state and listener firing are fully deferred to abort().
This prevents if-checks on signal.aborted from taking different
branches on first-run vs replay.
Add deterministic branching test (unit + e2e):
const controller = new AbortController();
if (controller.signal.aborted) {
return 'was aborted'; // never taken
} else {
controller.abort();
return 'just aborted'; // always taken, both runs
}
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* test: add abort+hook ordering matrix e2e tests (4 combinations)
Test all combinations of listener registration order and event trigger
order to validate deterministic ordering across first-run and replay:
1. addEventListener first, abort() first
2. addEventListener first, resumeHook first
3. hook.then first, abort() first
4. hook.then first, resumeHook first
Each test verifies that abort-listener fires synchronously at the
abort() call site (immediately before 'after-abort' in the log),
regardless of when the hook is resumed or when listeners are registered.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix: simplify abort — event consumer calls _setAborted directly
Remove the deferred _markAbortedFromReplay approach. The event consumer
now calls _setAborted directly when hook_received is processed, which
sets signal.aborted = true AND fires listeners at that point.
This is correct because:
- Cross-execution aborts (step/external): signal.aborted SHOULD be true
on replay since the abort is a fact from a previous run. Listeners must
fire so the workflow can react to the abort.
- Same-execution aborts: abort() fires _setAborted synchronously. On
replay, the event consumer fires it first, and abort() is a no-op.
- The promiseQueue ensures listeners fire at the deterministic point
matching the hook_received event's position in the event log.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* test: skip abort+hook ordering e2e tests pending full integration
The 4 ordering matrix tests require the abort controller's internal
system hook to be fully wired through the suspension handler. The hook
creation timing interacts with the user hook lookup in getHookByToken.
Skip until the full integration is complete.
All 13 other abort e2e tests pass on CI.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* handle dangling streams
* fix postgres world
* fix abort serialization bug
* refactors
* add drizzle migration file
* fix tests
* fix tests
* replace setTimeout probe and any casts with typed abort internals
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* cover post-serialization abort and nested-in-Request reader cleanup
Two leak paths the prior fix left uncovered:
- External signal aborted after serialization: verifies the listener
attached by reduceAbortWithListener actually fires and writes the
abort packet once the caller aborts later.
- Signal nested inside a Request: exposed a real leak. The Request
constructor copies the signal to an internal AbortSignal, so the
ABORT_READER_CANCEL symbol set by reviveAbortSignal never reached
request.signal, and cancelAbortReaders' walker had no Request case
so Object.values(request) returned []. Fixed both sides:
- Request reviver copies abort-internal symbols via copyAbortInternals
- Walker descends into Request.signal explicitly
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* add v4/v5 docs switcher and pre-release gating
- Mark new abort-controller/cancellation pages with preRelease: true
(cancellation, how-it-works/cancellation, abort-signal-timeout-in-workflow,
serializable-abort-controller). preRelease is a new optional frontmatter
field declared in source.config.ts.
- lib/geistdocs/versions.ts: declarative version list (v4 Latest, v5 Pre-release)
plus getVersionFromPathname and buildVersionUrl helpers used by the switcher.
- lib/geistdocs/version-source.ts: filter preRelease pages out of the v4
sidebar tree; rewrite sidebar URLs to /v5/docs/* on v5 so links stay in
the pre-release view.
- components/geistdocs/version-switcher.tsx: dropdown at the top of the
sidebar, styled after the ai-sdk.dev pattern (label + subtitle).
- components/geistdocs/pre-release-banner.tsx: banner rendered above the
docs layout on all /v5/docs/* routes, linking back to /docs/* (Latest).
- app/[lang]/v5/docs: parallel route (layout + page) that reuses the
existing docs rendering but keeps preRelease pages visible.
- app/[lang]/docs/[[...slug]]: 404 direct access to preRelease pages on v4
so unreleased content is never reachable without the /v5 prefix.
- next.config.ts: /v5/docs -> /v5/docs/getting-started mirror of the
existing /docs -> /docs/getting-started redirect.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix version switcher URL when default locale is hidden
buildVersionUrl assumed segment 0 was the locale, but next.js i18n
middleware hides the default locale from the URL so usePathname()
returns '/docs/...' rather than '/en/docs/...'. The old logic treated
'docs' as the locale and produced '/docs/v5/getting-started' (404)
instead of '/v5/docs/getting-started'.
Detect the locale by checking whether segment 0 is a known structural
token ('docs' or 'v5') rather than by position, so the function works
for both '/docs/...' and '/<locale>/docs/...' inputs.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* match ai-sdk pre-release banner styling
Filled sparkles glyph, blue tint on the message text, and a plain
underlined "Go to ..." link in the foreground color instead of a
bordered pill. Matches the ai-sdk.dev v7 banner reference.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* match ai-sdk switcher icons and banner link color
- Switcher: colored rounded icon tile next to each version (orange tint
for pre-release, blue for latest), matching the ai-sdk.dev dropdown.
Uses a workflow glyph inside a tinted ring.
- Banner link: blue text with a softer underline by default, deeper
blue on hover. Replaces the foreground-colored link that didn't
match ai-sdk's styling.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* use exact ai-sdk icons and darker banner link
- Switcher tile: use the T-mark SVG and the bg-orange-100/border-orange-300
(pre-release) / bg-blue-100/border-blue-300 (latest) palette extracted
from the ai-sdk.dev live markup, with matching dark-mode variants.
- Pre-release banner sparkle: replaced the placeholder with the exact
three-path geist sparkle used by ai-sdk.
- Banner "Go to Latest" link: foreground color with a muted underline
by default (same weight as ai-sdk's near-black link), underline
intensifies on hover. The previous blue-600 was too light.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(docs): correct dark-mode colors for pre-release banner and version switcher
The geistcn design-system palette inverts brightness semantics in dark
mode (low indices = dim, high indices = bright) and remaps `blue-*` but
not `orange-*`, so the previous token choices rendered as dim gray-blue
text and a mid-bright blue icon inconsistent with the dropdown list.
- Banner: use `dark:text-blue-900` for icon + label and switch the "Go
to" link from `text-foreground` to the same blue (with a blue
underline) so it reads as a single colored banner.
- VersionSwitcher: move the text color onto the SVG itself so the
`DropdownMenuItem` SVG-color override no longer hijacks the T color,
and invert the dark blue palette (dark bg, light border, bright T) so
the selected/trigger icon matches the list icon.
- Active-row check icon: use green instead of `fd-primary` (which
resolves to near-white in dark mode).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix: add signal field to Request serializable type
The merge from main moved the Request type into serialization/types.ts
without carrying over the signal?: AbortSignal field, causing the
abort-related reducers/revivers in serialization.ts to fail typecheck.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* refactor: address review feedback on abort serialization
- Dedupe abort listener attach in serialization reducers via marker symbol
(prevents N-listener leak when one controller is serialized to N steps,
which would double-close the backing stream on abort).
- Replace token.replace('abrt_', '') string-surgery in suspension-handler
by storing streamName directly on HookInvocationQueueItem at the point
where it's already known (workflow/abort-controller.ts construction).
- Document the deliberate sync-vs-microtask listener divergence in the
workflow VM (replay determinism > spec parity inside the VM).
- Add changeset noting the AbortError -> FatalError behavior change.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* docs: correct cancellation docs against implementation
- Remove the contradictory paragraph claiming signal.aborted is not set
synchronously when abort() is called in the workflow. The implementation
sets it sync via _setAborted; replay re-applies via the events consumer.
- Reword the "Stream Succeeds, Hook Fails" recovery — there's no in-process
retry loop on the step-side resumeHook call; convergence comes from the
next replay re-reading the stream.
- Tighten Request.signal handling: plain non-aborted native signals are
intentionally dropped to avoid minting stream infra for auto-generated
Request signals; only already-aborted or workflow-tagged signals are
forwarded.
- Replace the wrong "Pending queue items processed on completion" bullet
with an accurate fire-and-forget note matching the warn-only behavior.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix: DOMException serialization (replace broken isNativeError guard)
DOMException is `instanceof Error` in Node but does NOT pass
`types.isNativeError()` — the existing reducer's first guard was
`isNativeError(value)`, so DOMException never matched. Devalue then
fell through to its arbitrary-POJO failure path.
This surfaced as a real bug for AbortController/AbortSignal: when
abort() is called with no argument, native AbortController synthesizes
a default DOMException as signal.reason. Returning that signal's reason
from a step (e.g. `{aborted, reason: signal.reason}`) crashed step
return-value serialization.
Replace the guard with a constructor-name check (cross-VM safe; same
pattern used elsewhere for matching Error subclasses across realms).
Also fixes 7 pre-existing DOMException tests in serialization.test.ts
that were previously failing on main.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix: drain pending queue items on workflow completion
End-of-run now goes through the same suspension handler that processes a
real suspension. Previously, items left in the invocations queue when the
workflow function returned (or threw) were dropped with an "uncommitted
operation" warning — `controller.abort()` called as the last statement of
a workflow never actually propagated.
Concretely fixes:
- Abort hooks now write hook_received + stream packet so in-flight steps
on other compute instances see signal.aborted=true and bail out.
- Unawaited hooks are created (so external callers can resume them).
- Unawaited steps and sleeps are queued (will execute / fire later).
Strengthens abortTimeoutWorkflow's test to inspect the event log for the
hook_received event — the original assertion only verified the workflow
VM's local signal.aborted, which was set synchronously by the abort()
call regardless of whether propagation actually happened. The strengthened
test fails on main and passes after this commit.
Drops the warnPendingQueueItems warning entirely. Drain failures are
swallowed so the workflow's own outcome (return value or thrown error)
remains the source of truth for the run's terminal state.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* test: cover the deserialized AbortSignal listener path with an in-flight fetch
The existing abort tests exercised either the polled `signal.aborted` read
path (longStep busy-wait) or the already-aborted-before-fetch path. Nothing
exercised the live listener path: signal starts non-aborted, step kicks off
a fetch against a slow endpoint, abort fires while fetch is awaiting the
response, and fetch's internal `signal.addEventListener('abort', …)` listener
cancels the in-flight HTTP request.
The pre-existing `fetchWithSignal` helper step was orphaned — defined but
not referenced by any workflow. Wires it into a new `abortFetchInFlightWorkflow`
that races a 30s fetch against a 2s sleep, aborts when the sleep wins, and
returns the step's catch-path result. The test asserts both `winner=timeout`
and `fetchResult.aborted=true`, which together prove fetch saw the cancellation
mid-flight (the natural-completion path would set ok=true,aborted=false).
Adds a local /api/delay endpoint to the nextjs-turbopack workbench so the test
doesn't depend on an external service. Honors the request's own AbortSignal
so cancelled connections close immediately.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* test: extend abortFromStepWorkflow to verify in-flight sibling cancellation
The original test only asserted that the workflow VM's signal saw aborted=true
after a step called controller.abort(). It didn't actually verify that another
in-flight step received the cancellation through the backing stream — those
two paths are different (workflow VM signal updates via the hook event;
sibling-step propagation runs through the live stream packet).
Restructure the workflow to run longStep (a 30s polling loop on signal.aborted)
in parallel with abortFromStep (now sleeps 1s, then aborts). The new assertion
expects longStep.result === 'aborted' — proving it exited via the abort branch
within ~1.5s, NOT ran to its 30s natural completion. Returning 'completed'
would mean realtime cross-step cancellation is broken.
abortFromStep gained an optional delayMs parameter so it can be sequenced
against a sibling without an out-of-band sleep.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix: dehydrate abort stream packets via the same machinery as hook events
The abort stream packet was being encoded with bare `JSON.stringify({reason})`
on the writer and decoded with `JSON.parse(text).reason` on the reader. That
codec drops `undefined` (so a reason-less abort wrote literally `{}` and the
observability UI showed an empty stream), and doesn't handle DOMException or
any other type the rest of the codebase serializes via devalue+reducers.
Switch all three sites — suspension-handler workflow-side write, patched
abort step-side write, and `setupAbortStreamReader` — to use
`dehydrateStepArguments`/`hydrateStepArguments`. Now the `reason` round-trips
with full type fidelity (DOMException, custom errors, encrypted payloads),
matching what the hook event payload already does. The suspension handler
literally reuses the same dehydrated bytes for the event and the stream so
they're guaranteed identical.
Encryption key threading:
- Suspension handler: `encryptionKey` was already in scope.
- Patched abort: read from `contextStorage.getStore()?.encryptionKey` (set
by the step handler before invoking the deserialize chain).
- Reader (`setupAbortStreamReader`): read from `contextStorage.getStore()?.encryptionKey`
for the same reason; falls back to `undefined` when called outside step
context (the hydrate path is key-tolerant).
On-disk verification:
- Before: chunk for `controller.abort()` (no reason) was `00 7b 7d` — 3 bytes,
the literal JSON `{}`, no reason carried at all.
- After: chunk is `00 64 65 76 6c [{"aborted":1,"reason":2},true,"test"]` —
43 bytes, devalue-flat-encoded with the reason intact.
Updated the existing stream-reader unit test to encode its mock payload
through the same dehydrate path so the reader can decode it.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* test: cover addEventListener, mid-flight throwIfAborted, and step-initiated determinism
The polled-`signal.aborted` path was the only abort consumption pattern
exercised end-to-end. Three new e2e tests fill the gaps:
- **abortListenerWorkflow** — `signal.addEventListener('abort', cb)` firing
on the deserialized step-side signal. Distinct from abortFetchInFlightWorkflow
which only proves it indirectly through fetch's internal listener; this one
verifies user-attached listeners directly. Step resolves with via:'listener'
if propagation worked, via:'timeout' on a 30s safety timeout if it didn't.
- **abortThrowIfAbortedMidFlightWorkflow** — throwIfAborted() in a polling
loop, not just at step entry. The existing abortThrowIfAbortedWorkflow
only covers the synchronous-throw case on a pre-aborted signal. This one
starts the signal non-aborted, polls throwIfAborted every 500ms, and aborts
from a sibling step after 1s. Verifies the DOMException propagates as
FatalError (no retries) when fired mid-flight.
- **abortDeterministicBranchFromStepWorkflow** — counterpart to
abortDeterministicBranchWorkflow, but with the abort source being a step
(via the patched abort() path / hook event) instead of the workflow body.
Both branch-reads MUST take the same path on every replay. Uncovered a
real semantic: signal.aborted reflects step-initiated aborts only after
the next promise-queue checkpoint (sleep, step await, etc.) since
_setAborted is chained on promiseQueue. The test inserts the required
sleep('1s') checkpoint and asserts both pre and post values.
Helper steps factored: stepWaitingOnAbortListener and stepPollingThrowIfAborted.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* test: drop signal.aborted shortcut in stepWaitingOnAbortListener
The shortcut would have masked a regression in the addEventListener-on-an-
already-aborted-signal contract. Per the AbortSignal spec, calling
addEventListener('abort', cb) on an aborted signal fires the callback (on a
microtask), so user code that subscribes via the listener path alone — the
common pattern — depends on it. Test the contract directly: rely solely on
the listener resolving the promise. If addEventListener-on-aborted ever
silently breaks, this test now reports via:'timeout' instead of paving over
it with a fast-path that reads signal.aborted directly.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix: add DOMException reviver to observabilityRevivers so the o11y UI hydrates abort reasons
The observability UI (and CLI) hydrates step IO via `observabilityRevivers`,
which had no `DOMException` entry. When a step returned a value containing
a DOMException (typically `{aborted, reason: <DOMException>}` — synthesized
by native AbortController when abort() is called with no reason), devalue's
`parse` would throw on the `["DOMException", ...]` tag, `hydrateStepIO`'s
try/catch would swallow it, and the raw devalue-flat string survived to
the UI. The user-visible result was step Output showing literal text like:
devl[{"aborted":1,"reason":2},true,["DOMException",3]...]
instead of a JSON viewer with a proper DOMException card.
Add the reviver. Reconstruct as a real DOMException when the global is
available (modern browsers + Node 18+, where the o11y consumers run),
falling back to a name-tagged Error otherwise. Preserves message/name/
stack/cause for display.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* test: cover the external-signal-aborted-in-flight propagation path
The existing abortExternalSignalWorkflow only validates a static read of
an already-aborted signal — it tells us nothing about whether an abort
that fires AFTER serialization actually propagates from the caller process,
through the listener attached at workflow-start, into the backing stream,
and out into the deserialized signals on the in-flight step compute.
Add abortExternalSignalInFlightWorkflow that takes a non-aborted signal
and runs two parallel consumption patterns against it: longStep (polling
signal.aborted) and stepWaitingOnAbortListener (addEventListener path).
The test creates a fresh AbortController, calls start() with its non-aborted
signal, and aborts the source controller 1.5s later via setTimeout — well
after both steps are mid-flight on their compute instances.
Both consumers must see the cancellation:
- pollResult === 'aborted' (NOT 'completed' — that would mean longStep ran
the full 30s without ever seeing signal.aborted=true)
- listenerResult.via === 'listener' (NOT 'timeout' — that would mean the
addEventListener callback never fired)
This exercises the longest end-to-end abort path in the codebase:
caller-process AbortController → serialization-time listener →
backing stream → step compute → deserialized signal →
(poll OR addEventListener)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(test): use httpbin.org/delay for abortFetchInFlightWorkflow
The previous setup added a /api/delay route to workbench/nextjs-turbopack
to give the test a slow endpoint to fetch against. That made the workflow
fail in CI on every other workbench (nextjs-webpack, astro, sveltekit, …)
since the route only existed on one of them — fetch returned 404 and the
test failed within 1s instead of taking the expected ~3s.
Switch to httpbin.org/delay/30, the same external-service pattern used by
other e2e workflows in this file (jsonplaceholder, example.com). Removes
the per-workbench dependency. Drops the now-unused deploymentUrl argument
from the workflow signature and test call site.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* docs: fix serialization page — drop duplicate header, move AbortController section
Two issues on the serialization foundations page:
1. `## Pass-by-Value Semantics` appeared twice. The second occurrence had no
body, which rendered as an orphaned heading just above the AbortController
section in the docs preview.
2. `## AbortController & AbortSignal` was at the bottom of the page, after
`## Custom Class Serialization`. It belongs above the custom-class section
so the standard serializable types are grouped together before the
advanced topic.
Removes the empty duplicate; relocates the AbortController section to sit
between Request & Response and Custom Class Serialization. No content
changes inside the section.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* docs: note that run.cancel() is the same as the observability Cancel button
The Run Cancellation section showed the programmatic path but didn't tie
it back to the UI. Add a callout: calling run.cancel() is the same action
as clicking the Cancel button on a run in the observability UI — both
produce identical run_cancelled events.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* test: cover AbortSignal.any in both workflow VM and step contexts
Two distinct paths: the workflow VM ships its own AbortSignal.any impl in
workflow/abort-controller.ts (composes WorkflowAbortSignals via listeners,
no stream/hook backing on the composite), while steps use the native
Node implementation over deserialized signals. Neither was tested.
abortAnyInWorkflowWorkflow exercises the VM impl directly: creates two
controllers, composes their signals via AbortSignal.any, aborts one, and
asserts the composite reflects the abort synchronously without any stream
round-trip. Also asserts the other source signal is unaffected so a
mass-abort regression would surface here.
abortAnyInStepWorkflow exercises the longest end-to-end path that uses
AbortSignal.any: source controller is aborted by a sibling step, abort
flows through the workflow's VM, then the backing stream, into the step's
deserialized signal, into the AbortSignal.any composite, into the user's
listener. Returning via:'timeout' instead of via:'listener' would mean a
break anywhere on that chain.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* Update .changeset/fix-dom-exception-serialization.md
Co-authored-by: Peter Wielander <mittgfu@gmail.com>
Signed-off-by: Pranay Prakash <pranay.gp@gmail.com>
* Update .changeset/serializable-abort-controller.md
Co-authored-by: Peter Wielander <mittgfu@gmail.com>
Signed-off-by: Pranay Prakash <pranay.gp@gmail.com>
* Update .changeset/drain-pending-queue-on-completion.md
Co-authored-by: Peter Wielander <mittgfu@gmail.com>
Signed-off-by: Pranay Prakash <pranay.gp@gmail.com>
* docs(errors): match slug-as-title convention + simplify the timeout example
Two toolbar-comment fixes on the abort-signal-timeout-in-workflow error
page:
1. The page title was Title Case ("AbortSignal.timeout() in Workflow")
while every other page in docs/content/docs/errors/ uses the kebab-case
slug as the title (e.g. timeout-in-workflow, fetch-in-workflow,
workflow-not-registered). Match the convention.
2. The recommended replacement for AbortSignal.timeout() was a
Promise.race that wrapped the abort + null sentinel + custom Error
throw. Boil it down to the much simpler:
const controller = new AbortController();
void sleep("10s").then(() => controller.abort());
return await fetchData(controller.signal);
If fetchData finishes within 10s you get the response; if not, the
timer fires controller.abort(), fetch rejects with AbortError, and
the step's failure propagates to the workflow as a FatalError (no
retries). Same observable behavior, no Promise.race scaffolding.
Adds abortVoidSleepTimeoutWorkflow + matching e2e test that exercises
this exact pattern end-to-end so the doc example is verified runnable
(not just pseudocode). Asserts the fetch is cancelled mid-flight by
the timer, returning aborted=true,ok=false from the step.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---------
Signed-off-by: Pranay Prakash <pranay.gp@gmail.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-authored-by: Karthik Kalyanaraman <karthik.kalyanaraman@vercel.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Peter Wielander <mittgfu@gmail.com>
* Warn when serverExternalPackages hides workflow-enabled packages
Add a build-time warning when packages in serverExternalPackages contain
workflow code ('use step', 'use workflow', or serialization classes).
These packages are completely invisible to the workflow compiler when
externalized, causing silent runtime failures.
The warning detects workflow patterns via two methods:
- Fast path: check package.json dependencies for @workflow/serde
- Thorough path: read the package entry file and run pattern detection
Also adds documentation in the serialization guide about the
externalization footgun for 3rd-party packages.
* Auto-remove workflow packages from serverExternalPackages
When workflow-enabled dependencies are externalized in Next.js, compiler transforms are skipped and runtime failures follow. Detect those packages in withWorkflow, remove them from serverExternalPackages for the current build, and keep a generalized externalPackages warning fallback for non-Next builders.
* Address review feedback: add entry-point limitation comment and missing test case
Pranay Prakash