docs(KNO-14878): document latest vs pinned batch workflow version mode

[cjbell]

Summary

• Documents the new batch step workflow version mode: latest (default for new steps) vs pinned (advanced).
• Updates the existing "updating workflows with batch steps" section so it no longer describes pinned-only behavior as the only option. Latest keeps an open batch across commits and continues on the latest published version; pinned still keys a batch per workflow version.
• Notes that existing batch steps without this setting stay pinned, and clarifies parallel batch-step keying for each mode.

Test plan

• Read Batch function in the preview and confirm latest vs pinned is clear
• Confirm the "Continue on latest version" toggle and workflow_version_mode field are described
• Confirm existing "updating workflows" and parallel batch-step FAQs no longer say every batch is keyed on workflow_version_id

[linear-code]

KNO-14878

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview	Aug 20, 2026 6:34pm

[cjbell]

• docs(KNO-14878): document latest vs pinned batch workflow version mode #1618 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[cursor]

Risk LOW: Documents the new batch step workflow version mode (latest vs pinned) in the existing batch function page.

Reasons

• Single MDX content file modified (content/designing-workflows/batch-function.mdx); no code, config, or sidebar changes
• No HIGH triggers: no .tsx/.ts in components/, layouts/, lib/, or styles/, and no package.json, build config, or shared component edits
• No MEDIUM triggers: no new page, sidebar update, OpenAPI spec change, cross-section edits, or new images
• Diff is 54 additions and 10 deletions in one section; does not meet the 30+/30+ substantial rewrite threshold
• Author cjbell is a known team member and repository contributor

Notes

• Verify latest vs pinned behavior matches product behavior, especially the backward-compatibility callout for existing batch steps
• Confirm the "Continue on latest version" toggle and workflow_version_mode API/CLI field names are accurate
• Check that updated batch key descriptions and parallel batch-step FAQ align with the new default latest mode

  

_{Sent by Cursor Automation: Docs PR classifier}