Minor Changes

• #15856 4c2993b Thanks @Naapperas! - Support Workflows declared in exports on ctx.exports in local development

  A Workflow declared in a Worker's exports is now available on ctx.exports in wrangler dev, the Vite plugin and the Vitest plugin, with the same API as a Workflow binding:

  const instance = await ctx.exports.MyWorkflow.create({
    params: { name: "World" },
  });

  ctx.exports and workflows bindings with the same Workflow name share their instances, including instances created before the Workflow was declared in exports. Two Workers can't export the same Workflow name, and a binding to an exported Workflow must refer to the Worker and class that export it. getPlatformProxy() ignores Workflows declared in exports, since it doesn't run the Worker's code.

  wrangler workflows commands run with --local also work with Workflows declared only in exports, without a workflows binding.

  In the Vitest plugin, introspectWorkflow() and introspectWorkflowInstance() still need a Workflow binding, and now explain how to add one when passed a Workflow from ctx.exports. Instances created through ctx.exports are introspected too. A workflows binding whose script_name is the Worker's own name now resolves to the Worker itself again.

Patch Changes

• #15891 8dc53ae Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  @cloudflare/workers-types	^5.20260925.1	^5.20260926.1
  workerd	1.20260925.1	1.20260926.1

• Updated dependencies [8dc53ae, 4c2993b]:

  • miniflare@5.20260926.0-alpha

Minor Changes

• #15856 4c2993b Thanks @Naapperas! - Support Workflows declared in exports on ctx.exports in local development

  A Workflow declared in a Worker's exports is now available on ctx.exports in wrangler dev, the Vite plugin and the Vitest plugin, with the same API as a Workflow binding:

  const instance = await ctx.exports.MyWorkflow.create({
    params: { name: "World" },
  });

  ctx.exports and workflows bindings with the same Workflow name share their instances, including instances created before the Workflow was declared in exports. Two Workers can't export the same Workflow name, and a binding to an exported Workflow must refer to the Worker and class that export it. getPlatformProxy() ignores Workflows declared in exports, since it doesn't run the Worker's code.

  wrangler workflows commands run with --local also work with Workflows declared only in exports, without a workflows binding.

  In the Vitest plugin, introspectWorkflow() and introspectWorkflowInstance() still need a Workflow binding, and now explain how to add one when passed a Workflow from ctx.exports. Instances created through ctx.exports are introspected too. A workflows binding whose script_name is the Worker's own name now resolves to the Worker itself again.

Minor Changes

• #15856 4c2993b Thanks @Naapperas! - Support Workflows declared in exports on ctx.exports in local development

  A Workflow declared in a Worker's exports is now available on ctx.exports in wrangler dev, the Vite plugin and the Vitest plugin, with the same API as a Workflow binding:

  const instance = await ctx.exports.MyWorkflow.create({
    params: { name: "World" },
  });

  ctx.exports and workflows bindings with the same Workflow name share their instances, including instances created before the Workflow was declared in exports. Two Workers can't export the same Workflow name, and a binding to an exported Workflow must refer to the Worker and class that export it. getPlatformProxy() ignores Workflows declared in exports, since it doesn't run the Worker's code.

  wrangler workflows commands run with --local also work with Workflows declared only in exports, without a workflows binding.

  In the Vitest plugin, introspectWorkflow() and introspectWorkflowInstance() still need a Workflow binding, and now explain how to add one when passed a Workflow from ctx.exports. Instances created through ctx.exports are introspected too. A workflows binding whose script_name is the Worker's own name now resolves to the Worker itself again.

Patch Changes

• Updated dependencies [8dc53ae, 4c2993b]:
  • miniflare@5.20260926.0-alpha
  • wrangler@4.142.0

Minor Changes

• #15856 4c2993b Thanks @Naapperas! - Support Workflows declared in exports on ctx.exports in local development

  A Workflow declared in a Worker's exports is now available on ctx.exports in wrangler dev, the Vite plugin and the Vitest plugin, with the same API as a Workflow binding:

  const instance = await ctx.exports.MyWorkflow.create({
    params: { name: "World" },
  });

  ctx.exports and workflows bindings with the same Workflow name share their instances, including instances created before the Workflow was declared in exports. Two Workers can't export the same Workflow name, and a binding to an exported Workflow must refer to the Worker and class that export it. getPlatformProxy() ignores Workflows declared in exports, since it doesn't run the Worker's code.

  wrangler workflows commands run with --local also work with Workflows declared only in exports, without a workflows binding.

  In the Vitest plugin, introspectWorkflow() and introspectWorkflowInstance() still need a Workflow binding, and now explain how to add one when passed a Workflow from ctx.exports. Instances created through ctx.exports are introspected too. A workflows binding whose script_name is the Worker's own name now resolves to the Worker itself again.

Patch Changes

• Updated dependencies [8dc53ae, 4c2993b]:
  • miniflare@5.20260926.0-alpha
  • wrangler@4.142.0

Patch Changes

• Updated dependencies [8dc53ae, 4c2993b]:
  • miniflare@5.20260926.0-alpha

Patch Changes

• Updated dependencies [8dc53ae, 4c2993b]:
  • miniflare@5.20260926.0-alpha
  • @cloudflare/deploy-helpers@0.18.1
  • @cloudflare/workers-utils@0.44.0

Patch Changes

• Updated dependencies [8dc53ae, 4c2993b]:
  • miniflare@5.20260926.0-alpha

Patch Changes

• Updated dependencies [cde5d99, 8dc53ae, 77e79b2, 4c2993b]:
  • @cloudflare/config@0.20.0
  • miniflare@5.20260926.0-alpha
  • @cloudflare/containers-shared@0.20.3
  • @cloudflare/workers-utils@0.44.0

Patch Changes

• Updated dependencies [cde5d99, 77e79b2]:
  • @cloudflare/config@0.20.0
  • @cloudflare/build-output-utils@0.8.2
  • @cloudflare/workers-utils@0.44.0

Minor Changes

• #15877 cde5d99 Thanks @jamesopstad! - Add cross-Worker Workflow bindings to the experimental configuration API

  Workflow bindings can now identify a Workflow by name and reference the Worker and exported WorkflowEntrypoint class that define it.

Patch Changes

• #15880 77e79b2 Thanks @jamesopstad! - Restore configuration field documentation in define* helpers

  VS Code now displays JSDoc for fields passed to defineConfig, defineContainer, and defineWorker while retaining their exact inferred config types.