workflow 4.2.0-beta.74 → 4.2.0-beta.76

package/docs/getting-started/hono.mdx

@@ -1,6 +1,6 @@
 ---
 title: Hono
-description: This guide will walk through setting up your first workflow in a Hono app. Along the way, you'll learn more about the concepts that are fundamental to using the development kit in your own projects.
+description: This guide will walk through setting up your first workflow in a Hono app. Along the way, you'll learn more about the concepts that are fundamental to using the Workflow SDK in your own projects.
 type: guide
 summary: Set up Workflow SDK in a Hono app.
 prerequisites:

package/docs/getting-started/nestjs.mdx

@@ -9,7 +9,7 @@ related:
   - /docs/foundations/workflows-and-steps
 ---
 
-This guide will walk through setting up your first workflow in a NestJS app. Along the way, you'll learn more about the concepts that are fundamental to using the development kit in your own projects.
+This guide will walk through setting up your first workflow in a NestJS app. Along the way, you'll learn more about the concepts that are fundamental to using the Workflow SDK in your own projects.
 
 <Callout>
 NestJS integration is experimental and not yet supported for deployment to Vercel.

package/docs/getting-started/next.mdx

@@ -1,6 +1,6 @@
 ---
 title: Next.js
-description: This guide will walk through setting up your first workflow in a Next.js app. Along the way, you'll learn more about the concepts that are fundamental to using the development kit in your own projects.
+description: This guide will walk through setting up your first workflow in a Next.js app. Along the way, you'll learn more about the concepts that are fundamental to using the Workflow SDK in your own projects.
 type: guide
 summary: Set up Workflow SDK in a Next.js app.
 prerequisites:

package/docs/getting-started/nitro.mdx

@@ -1,6 +1,6 @@
 ---
 title: Nitro
-description: This guide will walk through setting up your first workflow in a Nitro v3 project. Along the way, you'll learn more about the concepts that are fundamental to using the development kit in your own projects.
+description: This guide will walk through setting up your first workflow in a Nitro v3 project. Along the way, you'll learn more about the concepts that are fundamental to using the Workflow SDK in your own projects.
 type: guide
 summary: Set up Workflow SDK in a Nitro app.
 prerequisites:

package/docs/getting-started/nuxt.mdx

@@ -1,6 +1,6 @@
 ---
 title: Nuxt
-description: This guide will walk through setting up your first workflow in a Nuxt app. Along the way, you'll learn more about the concepts that are fundamental to using the development kit in your own projects.
+description: This guide will walk through setting up your first workflow in a Nuxt app. Along the way, you'll learn more about the concepts that are fundamental to using the Workflow SDK in your own projects.
 type: guide
 summary: Set up Workflow SDK in a Nuxt app.
 prerequisites:

package/docs/getting-started/sveltekit.mdx

@@ -1,6 +1,6 @@
 ---
 title: SvelteKit
-description: This guide will walk through setting up your first workflow in a SvelteKit app. Along the way, you'll learn more about the concepts that are fundamental to using the development kit in your own projects.
+description: This guide will walk through setting up your first workflow in a SvelteKit app. Along the way, you'll learn more about the concepts that are fundamental to using the Workflow SDK in your own projects.
 type: guide
 summary: Set up Workflow SDK in a SvelteKit app.
 prerequisites:

package/docs/getting-started/vite.mdx

@@ -9,7 +9,7 @@ related:
   - /docs/foundations/workflows-and-steps
 ---
 
-This guide will walk through setting up your first workflow in a Vite app. Along the way, you'll learn more about the concepts that are fundamental to using the development kit in your own projects.
+This guide will walk through setting up your first workflow in a Vite app. Along the way, you'll learn more about the concepts that are fundamental to using the Workflow SDK in your own projects.
 
 ---
 

package/docs/how-it-works/understanding-directives.mdx

@@ -15,7 +15,7 @@ import { File, Folder, Files } from "fumadocs-ui/components/files";
 This guide explores how JavaScript directives enable the Workflow SDK's execution model. For getting started with workflows, see the [getting started](/docs/getting-started) guides for your framework.
 </Callout>
 
-The Workflow Development Kit uses JavaScript directives (`"use workflow"` and `"use step"`) as the foundation for its durable execution model. Directives provide the compile-time semantic boundary necessary for workflows to suspend, resume, and maintain deterministic behavior across replays.
+The Workflow SDK uses JavaScript directives (`"use workflow"` and `"use step"`) as the foundation for its durable execution model. Directives provide the compile-time semantic boundary necessary for workflows to suspend, resume, and maintain deterministic behavior across replays.
 
 This page explores how directives enable this execution model and the design principles that led us here.
 
@@ -339,7 +339,7 @@ This approach requires:
 - Storing/mutating class properties was not obvious (similar closure/mutation issues as the runtime-only approach)
 - Class-based syntax that doesn't feel "JavaScript native" to developers used to functional patterns
 
-As the JavaScript ecosystem has moved toward function-forward programming (exemplified by React's shift from class components to functions and hooks), requiring developers to use classes felt like a step backward and also didn't match our own personal taste as authors of the DevKit.
+As the JavaScript ecosystem has moved toward function-forward programming (exemplified by React's shift from class components to functions and hooks), requiring developers to use classes felt like a step backward and also didn't match our own personal taste as authors of the SDK.
 
 **The core problem: Presents workflows as regular runtime code**
 
@@ -615,4 +615,4 @@ As TC39 members, we at Vercel are actively working with the standards body and b
 
 Directives aren't about syntax preference, they're about expressing semantic boundaries. `"use workflow"` tells the compiler, developer, and runtime that this code is deterministic, resumable, and sandboxed.
 
-This clarity enables the Workflow Development Kit to provide durable execution with familiar JavaScript patterns, while maintaining the compile-time guarantees necessary for reliable workflow orchestration.
+This clarity enables the Workflow SDK to provide durable execution with familiar JavaScript patterns, while maintaining the compile-time guarantees necessary for reliable workflow orchestration.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "workflow",
-  "version": "4.2.0-beta.74",
+  "version": "4.2.0-beta.76",
   "description": "Workflow SDK - Build durable, resilient, and observable workflows",
   "main": "dist/typescript-plugin.cjs",
   "type": "module",
@@ -57,18 +57,18 @@
   },
   "dependencies": {
     "ms": "2.1.3",
-    "@workflow/astro": "4.0.0-beta.48",
-    "@workflow/cli": "4.2.0-beta.74",
-    "@workflow/core": "4.2.0-beta.74",
-    "@workflow/errors": "4.1.0-beta.19",
+    "@workflow/astro": "4.0.0-beta.50",
+    "@workflow/cli": "4.2.0-beta.76",
+    "@workflow/core": "4.2.0-beta.76",
+    "@workflow/errors": "4.1.0-beta.20",
     "@workflow/typescript-plugin": "4.0.1-beta.5",
     "@workflow/utils": "4.1.0-beta.13",
-    "@workflow/next": "4.0.1-beta.70",
-    "@workflow/nest": "0.0.0-beta.23",
-    "@workflow/nitro": "4.0.1-beta.69",
-    "@workflow/nuxt": "4.0.1-beta.58",
-    "@workflow/sveltekit": "4.0.0-beta.63",
-    "@workflow/rollup": "4.0.0-beta.31"
+    "@workflow/next": "4.0.1-beta.72",
+    "@workflow/nest": "0.0.0-beta.25",
+    "@workflow/nitro": "4.0.1-beta.71",
+    "@workflow/nuxt": "4.0.1-beta.60",
+    "@workflow/sveltekit": "4.0.0-beta.65",
+    "@workflow/rollup": "4.0.0-beta.33"
   },
   "devDependencies": {
     "@types/ms": "2.1.0",