Repository navigation
[skills] Resync workflow from vercel/workflow@3837f92 - #355
Merged
Merged
Conversation
vercel-gh-bot-3
Bot
force-pushed
the
eve-drift/workflow
branch
from
October 22, 2026 14:13
c2068fa to
cd746f5
Compare
pranaygp
approved these changes
Oct 22, 2026
vercel-gh-bot-2
Bot
force-pushed
the
eve-drift/workflow
branch
from
October 26, 2026 09:50
cd746f5 to
dac101d
Compare
vercel-gh-bot-3
Bot
force-pushed
the
eve-drift/workflow
branch
from
October 29, 2026 10:01
dac101d to
e036ba5
Compare
<!-- vercel-plugin-drift-agent -->
vercel-gh-bot-2
Bot
force-pushed
the
eve-drift/workflow
branch
from
November 2, 2026 09:56
e036ba5 to
b4ab6d2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resyncs
skills/workflow/upstream/SKILL.mdfrom vercel/workflow@3837f92 and corrects onevalidaterule message inoverlay.yaml.overlay.yamlvalidate 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 callgetWritable()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 regeneratedskills/workflow/SKILL.mdpicks up both changes.Test updates
None.
Not changed
check_linksflaggedhttps://ai-sdk.dev/v7/docs/agents/workflow-agent.**as a 404. The checker included the closing bold markers in the URL. The real URL https://ai-sdk.dev/v7/docs/agents/workflow-agent resolves to https://ai-sdk.dev/docs/agents/workflow-agent, and that line is upstream content.require()and nativefetch()sandbox rule messages were left as they are. They match the upstream body's sandbox limitations table.Opened automatically by the vercel-plugin drift agent. Review before merge.
Drift scan update 2026-10-22
Resync of
skills/workflow/upstream/SKILL.mdfrom vercel/workflow@3837f92 (skills/workflow).skills/workflow/SKILL.mdwas regenerated bybun run build:all.Verification
run_plugin_checkspassed 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_linksflaggedhttps://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/webhookis placeholder text inside a code sample, not a docs link.overlay.yamlwas not touched. The DurableAgent chainTo message matches npm:workflow@latestis 5.2.3 and@ai-sdk/workflow@2.0.80has a peer dependency onworkflow ^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.mdfrom vercel/workflow@9d0f748 and rebuildskills/workflow/SKILL.md.Verification
run_plugin_checks: build, typecheck, validate, and test all passed (1279 tests pass, 0 fail). Changed files:skills/workflow/upstream/SKILL.md(resync) andskills/workflow/SKILL.md(regenerated).Test updates
None.
Not changed
ai-sdk.dev/v7/docs/agents/workflow-agentlink in the upstream body is still live and redirects to https://ai-sdk.dev/docs/agents/workflow-agent.check_linksonly flagged it because the URL text runs into the closing.**. That text is upstream content, so it stays as is.chainTomessage about Workflow 5 and@ai-sdk/workflow2.x still holds. npmworkflow@latestis 5.2.3,@ai-sdk/workflow@latest2.0.85 has peerworkflow: ^5.1.0, and the AI SDK WorkflowAgent page says "@ai-sdk/workflowrequires Workflow 5".Opened automatically by the vercel-plugin drift agent. Review before merge.
Drift scan update 2026-10-29
skills/workflow/upstream/SKILL.mdfrom 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.yamlvalidate rule forgetWritable(): 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 callsgetWritable<ModelCallStreamPart>()in a"use workflow"function, so the old message contradicted it.Verification
run_plugin_checkspassed every step: build, typecheck, validate, and test (1279 pass, 0 fail).SKILL.mdwas 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_linksflaggedhttps://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.Opened automatically by the vercel-plugin drift agent. Review before merge.
Drift scan update 2026-11-02
Resync
skills/workflow/upstream/SKILL.mdfrom vercel/workflow@44d7c76 (skills/workflow), regeneratingskills/workflow/SKILL.md.Verification
run_plugin_checks: build, typecheck, validate, and test all passed (1279 pass, 0 fail).Test updates
None.
Upstream contradictions
WORKFLOW_MAX_EVENTS_OVERRIDEonly clamps down". The pricing page says the experimental QuickJS runtime (WORKFLOW_VM=quickjswith 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
https://ai-sdk.dev/v7/docs/agents/workflow-agentredirects tohttps://ai-sdk.dev/docs/agents/workflow-agent, which is a live page. It's upstream text, so I left it alone.chainTomessage about Workflow 5 /@ai-sdk/workflow2.x checks out: npmworkflow@latestis 5.2.3, and@ai-sdk/workflow@2.0.91has a peer dependency ofworkflow ^5.1.0.Opened automatically by the vercel-plugin drift agent. Review before merge.