workflow 4.1.0-beta.60 → 4.1.0-beta.61

package/docs/deploying/building-a-world.mdx

@@ -19,7 +19,7 @@ A **World** is the abstraction that allows workflows to run on any infrastructur
 </Callout>
 
 <Callout type="info">
-  **Reference Implementation:** The [Postgres World source code](https://github.com/vercel/workflow/tree/main/packages/world-postgres) is a production-ready example of how to implement the World interface with a database backend and pg-boss for queuing.
+  **Reference Implementation:** The [Postgres World source code](https://github.com/vercel/workflow/tree/main/packages/world-postgres) is a production-ready example of how to implement the World interface with a database backend and graphile-worker for queuing.
 </Callout>
 
 ## What is a World?
@@ -190,7 +190,7 @@ Streams are identified by a combination of `runId` and `name`. Each workflow run
 Study these implementations for guidance:
 
 - **[Local World](https://github.com/vercel/workflow/tree/main/packages/world-local)** — Filesystem-based, great for understanding the basics
-- **[Postgres World](https://github.com/vercel/workflow/tree/main/packages/world-postgres)** — Database-backed with pg-boss for queuing
+- **[Postgres World](https://github.com/vercel/workflow/tree/main/packages/world-postgres)** — Database-backed with graphile-worker for queuing
 
 ## Testing Your World
 

package/docs/deploying/world/postgres-world.mdx

@@ -1,8 +1,8 @@
 ---
 title: Postgres World
-description: Production-ready, self-hosted world using PostgreSQL for storage and pg-boss for job processing.
+description: Production-ready, self-hosted world using PostgreSQL for storage and graphile-worker for job processing.
 type: integration
-summary: Deploy workflows to your own infrastructure using PostgreSQL and pg-boss.
+summary: Deploy workflows to your own infrastructure using PostgreSQL and graphile-worker.
 prerequisites:
   - /docs/deploying
 related:
@@ -10,7 +10,7 @@ related:
   - /docs/deploying/world/vercel-world
 ---
 
-The Postgres World is a production-ready backend for self-hosted deployments. It uses PostgreSQL for durable storage and [pg-boss](https://github.com/timgit/pg-boss) for reliable job processing.
+The Postgres World is a production-ready backend for self-hosted deployments. It uses PostgreSQL for durable storage and [graphile-worker](https://github.com/graphile/worker) for reliable job processing.
 
 Use the Postgres World when you need to deploy workflows on your own infrastructure outside of Vercel - such as a Docker container, Kubernetes cluster, or any cloud that supports long-running servers.
 
@@ -41,7 +41,7 @@ The migration is idempotent and can safely be run as a post-deployment lifecycle
 
 ## Starting the World
 
-To subscribe to the pg-boss queue, your workflow app needs to start the world on server start. Here are examples for a few frameworks:
+To subscribe to the graphile-worker queue, your workflow app needs to start the world on server start. Here are examples for a few frameworks:
 
 <Tabs items={["Next.js", "SvelteKit", "Nitro"]}>
 
@@ -154,7 +154,7 @@ Default: `postgres://world:world@localhost:5432/world`
 
 ### `WORKFLOW_POSTGRES_JOB_PREFIX`
 
-Prefix for pg-boss queue job names. Useful when sharing a database between multiple applications.
+Prefix for graphile-worker queue job names. Useful when sharing a database between multiple applications.
 
 ### `WORKFLOW_POSTGRES_WORKER_CONCURRENCY`
 
@@ -178,7 +178,7 @@ const world = createWorld({
 The Postgres World uses PostgreSQL as a durable backend:
 
 - **Storage** - Workflow runs, events, steps, and hooks are stored in PostgreSQL tables
-- **Job Queue** - [pg-boss](https://github.com/timgit/pg-boss) handles reliable job processing with retries
+- **Job Queue** - [graphile-worker](https://github.com/graphile/worker) handles reliable job processing with retries
 - **Streaming** - PostgreSQL NOTIFY/LISTEN enables real-time event distribution
 
 This architecture ensures workflows survive application restarts with all state reliably persisted. For implementation details, see the [source code](https://github.com/vercel/workflow/tree/main/packages/world-postgres).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "workflow",
-  "version": "4.1.0-beta.60",
+  "version": "4.1.0-beta.61",
   "description": "Workflow DevKit - Build durable, resilient, and observable workflows",
   "main": "dist/typescript-plugin.cjs",
   "type": "module",
@@ -52,17 +52,17 @@
   },
   "dependencies": {
     "ms": "2.1.3",
-    "@workflow/astro": "4.0.0-beta.34",
-    "@workflow/cli": "4.1.0-beta.60",
+    "@workflow/astro": "4.0.0-beta.35",
+    "@workflow/cli": "4.1.0-beta.61",
+    "@workflow/core": "4.1.0-beta.61",
     "@workflow/errors": "4.1.0-beta.16",
-    "@workflow/core": "4.1.0-beta.60",
     "@workflow/typescript-plugin": "4.0.1-beta.4",
-    "@workflow/next": "4.0.1-beta.56",
-    "@workflow/nest": "0.0.0-beta.9",
-    "@workflow/nitro": "4.0.1-beta.55",
-    "@workflow/nuxt": "4.0.1-beta.44",
-    "@workflow/sveltekit": "4.0.0-beta.49",
-    "@workflow/rollup": "4.0.0-beta.17"
+    "@workflow/next": "4.0.1-beta.57",
+    "@workflow/nest": "0.0.0-beta.10",
+    "@workflow/nitro": "4.0.1-beta.56",
+    "@workflow/nuxt": "4.0.1-beta.45",
+    "@workflow/sveltekit": "4.0.0-beta.50",
+    "@workflow/rollup": "4.0.0-beta.18"
   },
   "devDependencies": {
     "@types/ms": "2.1.0",