Four packages, start roles, and stricter checks
Published: November 16, 2026
Workflows 0.39 ships as four packages, and npx @sanity/workflows-cli codemod packages moves a project to them. Definitions can say who may start them, and deploy checks definitions more strictly. Every project needs to act, so read Before you upgrade in the release notes before you install.
Four Workflows packages
@sanity/workflows, @sanity/workflows-ui, @sanity/workflows-cli, and @sanity/workflows-test replace the @sanity/workflow-* packages. The codemod rewrites imports and dependencies and renames ten UI exports. See Move to the four Workflows packages.
Start roles
start: {roles: [...]} limits who may start a fresh instance. Studio leaves the workflow out of Start for everyone else, unless an unfinished start on the document needs completing. It needs reader model 13. See Decide who may start an instance.
References into any resource type
An engine created without resourceClients reads and writes references into other datasets, Canvases, and dashboards. It derives a client for each one from its own client with withConfig, so its token must reach those resources. See Allowed target resources.
Stricter definition checks
Deploy refuses condition and field reads that always return null. Run sanity-workflows deploy --check with the 0.39 CLI before you upgrade. See Fix condition and field reads that never hold a value.
š Notable bugfixes and improvements
- The generated heartbeat logs one summary line per run. See Check the result.
useWorkflowInstancesanduseDocumentWorkflowstake a GROQ filter. See Instance list hooks.- Studio gives object and list fields that declare their sub-fields real inputs, and a disabled action button says why.
- The start dialog submits a single assignee and lets you fill a required list field.
Related documentation
Workflows release notes
Curated overviews of recent Workflows prerelease package waves.
Upgrade Workflows packages
Take a new Workflows release without breaking in-flight instances: the lockstep set, what the reader-model literal claims, and the readers-first order.
Generate Functions from your workflow definitions
Generate the Sanity Functions your workflow definitions need, connect an effect handler, and deploy them with Blueprints.
Workflow CLI command reference
Every Workflows CLI command with its flags, selectors, JSON output, and exit behavior, for deploying definitions and driving instances.
Definitions, instances, and stages
A definition describes a process. An instance is one run of it, pinned to the definition version it started under and sitting in exactly one stage.
Global document references
Why every document pointer in a workflow carries its location, and which resources a workflow may read and write.
Reusable UI components
Add assignment, date, member, and workflow-diagram controls to a custom Workflows interface.