Skip to content

[skills] Resync workflow from vercel/workflow@3837f92 - #355

Merged
karthikscale3 merged 1 commit into
mainfrom
eve-drift/workflow
Nov 2, 2026
Merged

karthikscale3 merged 1 commit into
mainfrom
eve-drift/workflow

Conversation

@vercel-gh-bot-2

@vercel-gh-bot-2 vercel-gh-bot-2 Bot commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

Resyncs skills/workflow/upstream/SKILL.md from vercel/workflow@3837f92 and corrects one validate rule message in overlay.yaml.

  • Resync (upstream body): "Steps per run. Capped implicitly through the event limit." now reads "Capped separately from events, so a long sequential chain is bounded even though it stays narrow." The intro line under "Run size & concurrency" also changed. This matches https://vercel.com/docs/workflows/pricing#workflow-run-limits (last_updated 2026-09-16), whose run limits table lists "Steps per run" (10,000) as its own row, separate from "Events per run" (25,000 limit).
  • overlay.yaml validate rule (getWritable\(\)): the message said "getWritable() must only be called inside "use step" functions — workflow sandbox scope does not support it". The new message says workflow scope only obtains the stream, and you pass it to a "use step" function (or call getWritable() there) to write to it. Source: https://workflow-sdk.dev/docs/api-reference/workflow/get-writable (lastUpdated 2026-10-19): "The writable stream can be obtained in workflow functions and passed to steps, or called directly within step functions". The synced upstream body says the same thing ("getWritable() can be called in both workflow and step contexts").

Verification

run_plugin_checks: build, typecheck, validate and test all pass (1268 pass, 0 fail). The regenerated skills/workflow/SKILL.md picks up both changes.

Test updates

None.

Not changed

Opened automatically by the vercel-plugin drift agent. Review before merge.


Drift scan update 2026-10-22

Resync of skills/workflow/upstream/SKILL.md from vercel/workflow@3837f92 (skills/workflow). skills/workflow/SKILL.md was regenerated by bun run build:all.

  • The "Run size & concurrency" section said steps per run are "Capped implicitly through the event limit." The upstream copy now says steps are "Capped separately from events". It also adds "Three things to size, and all three are capped" and calls the pricing page "the only source to quote". The docs back this: https://vercel.com/docs/workflows/pricing (last_updated 2026-09-16) lists a separate run limit, "Steps per run | 10,000", next to "Events per run | 25,000 limit".

Verification

run_plugin_checks passed every step: build (0 updated, 7 unchanged, 0 errors), typecheck, validate ("PASSED — all checks OK") and test (1279 pass, 0 fail).

Test updates

None.

Not changed

  • check_links flagged https://ai-sdk.dev/v7/docs/agents/workflow-agent.**. The trailing .** is closing Markdown bold, not part of the URL. The real URL resolves and redirects to https://ai-sdk.dev/docs/agents/workflow-agent. It is in upstream content, so it was left as is.
  • https://example.com/webhook is placeholder text inside a code sample, not a docs link.
  • overlay.yaml was not touched. The DurableAgent chainTo message matches npm: workflow@latest is 5.2.3 and @ai-sdk/workflow@2.0.80 has a peer dependency on workflow ^5.1.0.

Opened automatically by the vercel-plugin drift agent. Review before merge.


Drift scan update 2026-10-26

Resync skills/workflow/upstream/SKILL.md from vercel/workflow@9d0f748 and rebuild skills/workflow/SKILL.md.

  • "Run size & concurrency" section: the plugin copy said Steps per run is "Capped implicitly through the event limit." Upstream now says steps are "Capped separately from events, so a long sequential chain is bounded even though it stays narrow." The intro line also changes: it now says all three dimensions are capped and that the pricing page is the only source to quote. This matches https://vercel.com/docs/workflows/pricing (last_updated 2026-09-16). Its Workflow run limits table lists "Steps per run" as its own row, separate from "Events per run": 10,000 steps and 25,000 events on the default Node.js runtime. The steps row says "Applies to the default Node.js runtime. Steps write events, so [QuickJS] runs that are exempt from the event cap can execute more steps."

Verification

run_plugin_checks: build, typecheck, validate, and test all passed (1279 tests pass, 0 fail). Changed files: skills/workflow/upstream/SKILL.md (resync) and skills/workflow/SKILL.md (regenerated).

Test updates

None.

Not changed

  • The ai-sdk.dev/v7/docs/agents/workflow-agent link in the upstream body is still live and redirects to https://ai-sdk.dev/docs/agents/workflow-agent. check_links only flagged it because the URL text runs into the closing .**. That text is upstream content, so it stays as is.
  • The overlay chainTo message about Workflow 5 and @ai-sdk/workflow 2.x still holds. npm workflow@latest is 5.2.3, @ai-sdk/workflow@latest 2.0.85 has peer workflow: ^5.1.0, and the AI SDK WorkflowAgent page says "@ai-sdk/workflow requires Workflow 5".

Opened automatically by the vercel-plugin drift agent. Review before merge.


Drift scan update 2026-10-29

  • Resync skills/workflow/upstream/SKILL.md from vercel/workflow@6829c26. Upstream changed the "Run size & concurrency" section: the stale claim "Steps per run. Capped implicitly through the event limit." now reads "Capped separately from events". Source: https://vercel.com/docs/workflows/pricing (last_updated 2026-09-16), which lists separate rows: "Events per run | 25,000 limit" and "Steps per run | 10,000". The intro sentence now also says "all three are capped".
  • overlay.yaml validate rule for getWritable(): the stale message "getWritable() must only be called inside "use step" functions — workflow sandbox scope does not support it" now says the stream can only be written inside steps, and workflow code should get the stream and pass it to a step. Source: https://workflow-sdk.dev/docs/api-reference/workflow/get-writable (lastUpdated 2026-10-26): "The writable stream can be obtained in workflow functions and passed to steps". The skill's own WorkflowAgent example calls getWritable<ModelCallStreamPart>() in a "use workflow" function, so the old message contradicted it.

Verification

run_plugin_checks passed every step: build, typecheck, validate, and test (1279 pass, 0 fail). SKILL.md was regenerated from the overlay and upstream.

Test updates

None.

Upstream contradictions

None found. The resynced text matches the run limits table on the pricing page.

Not changed

  • check_links flagged https://ai-sdk.dev/v7/docs/agents/workflow-agent.**. That's a false positive caused by the trailing bold markers. The URL itself resolves to https://ai-sdk.dev/docs/agents/workflow-agent, and it's upstream text in any case.
  • The other validate and chainTo messages were left as they are.

Opened automatically by the vercel-plugin drift agent. Review before merge.


Drift scan update 2026-11-02

Resync skills/workflow/upstream/SKILL.md from vercel/workflow@44d7c76 (skills/workflow), regenerating skills/workflow/SKILL.md.

  • "Steps per run. Capped implicitly through the event limit." → upstream now says steps are "Capped separately from events, so a long sequential chain is bounded even though it stays narrow." Source: https://vercel.com/docs/workflows/pricing (last_updated 2026-09-16), which lists a separate row: "Steps per run | 10,000 | Applies to the default Node.js runtime." The intro sentence of the section is also updated upstream to note that all three dimensions are capped and that the pricing page is the only source to quote.

Verification
run_plugin_checks: build, typecheck, validate, and test all passed (1279 pass, 0 fail).

Test updates
None.

Upstream contradictions

  • Upstream says "You cannot raise any of these yourself — WORKFLOW_MAX_EVENTS_OVERRIDE only clamps down". The pricing page says the experimental QuickJS runtime (WORKFLOW_VM=quickjs with snapshotting) lifts the per-run event and step caps: "Events per run and Steps per run are the defaults for the Node.js runtime, and the QuickJS runtime lifts both." Left as upstream wrote it. This needs fixing in vercel/workflow.

Not changed

  • "Vercel raises the per-run event and step limits on request": the pricing page doesn't say this, so I couldn't verify it. It's upstream text, so I left it alone.
  • The AI SDK link https://ai-sdk.dev/v7/docs/agents/workflow-agent redirects to https://ai-sdk.dev/docs/agents/workflow-agent, which is a live page. It's upstream text, so I left it alone.
  • The overlay chainTo message about Workflow 5 / @ai-sdk/workflow 2.x checks out: npm workflow@latest is 5.2.3, and @ai-sdk/workflow@2.0.91 has a peer dependency of workflow ^5.1.0.

Opened automatically by the vercel-plugin drift agent. Review before merge.

<!-- vercel-plugin-drift-agent -->
@karthikscale3
karthikscale3 merged commit 33190c3 into main Nov 2, 2026
5 checks passed
@karthikscale3
karthikscale3 deleted the eve-drift/workflow branch November 2, 2026 16:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants