workflow 4.2.0-beta.72 → 4.2.0-beta.73

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

@@ -160,6 +160,12 @@ Prefix for graphile-worker queue job names. Useful when sharing a database betwe
 
 Number of concurrent workers polling for jobs. Default: `10`
 
+### `WORKFLOW_POSTGRES_MAX_POOL_SIZE`
+
+Maximum size of the internal `pg.Pool` used when `createWorld()` constructs the pool. Default: `10`
+
+For higher worker concurrency, Graphile Worker recommends setting `maxPoolSize` to `10` or `queueConcurrency + 2`, whichever is larger.
+
 ### Programmatic configuration
 
 {/* @skip-typecheck: incomplete code sample */}
@@ -170,6 +176,7 @@ const world = createWorld({
   connectionString: "postgres://user:password@host:5432/database",
   jobPrefix: "myapp_",
   queueConcurrency: 20,
+  maxPoolSize: 20, // overrides WORKFLOW_POSTGRES_MAX_POOL_SIZE
 });
 ```
 

package/docs/testing/index.mdx

@@ -85,7 +85,7 @@ Unit testing works well for individual steps. A simple workflow that only calls
 For workflows that rely on runtime features like [hooks](/docs/foundations/hooks), [webhooks](/docs/foundations/hooks#understanding-webhooks), [`sleep()`](/docs/api-reference/workflow/sleep), or error retries, you need to test against a real workflow setup. The `@workflow/vitest` plugin handles everything automatically — it compiles your workflow directives, builds the runtime bundles, and executes workflows entirely in-process. No server required.
 
 <Callout type="warn">
-Inside integration tests, which run the full workflow runtime, `vi.mock()` and related calls do not work — neither for your own modules nor for third-party npm packages. All step dependencies are inlined into the compiled bundle by esbuild, bypassing Vitest's module system entirely. To test steps with mocked dependencies, use [unit tests](#unit-testing-steps) instead. Consider dependency injection or environment variable-based conditional logic for controlling behavior in integration tests.
+`vi.mock()` and related calls do _not_ work inside workflow functions, only step functions. Your workflow functions cannot import third party code that needs to be mocked. Mocking works for npm packages imported in step functions. If something needs to be mocked, it likely belongs inside a step function either way.
 </Callout>
 
 ### Vitest Configuration

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "workflow",
-  "version": "4.2.0-beta.72",
+  "version": "4.2.0-beta.73",
   "description": "Workflow DevKit - 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.46",
-    "@workflow/cli": "4.2.0-beta.72",
-    "@workflow/core": "4.2.0-beta.72",
+    "@workflow/astro": "4.0.0-beta.47",
+    "@workflow/cli": "4.2.0-beta.73",
+    "@workflow/core": "4.2.0-beta.73",
     "@workflow/errors": "4.1.0-beta.19",
     "@workflow/typescript-plugin": "4.0.1-beta.5",
     "@workflow/utils": "4.1.0-beta.13",
-    "@workflow/next": "4.0.1-beta.68",
-    "@workflow/nest": "0.0.0-beta.21",
-    "@workflow/nitro": "4.0.1-beta.67",
-    "@workflow/nuxt": "4.0.1-beta.56",
-    "@workflow/sveltekit": "4.0.0-beta.61",
-    "@workflow/rollup": "4.0.0-beta.29"
+    "@workflow/next": "4.0.1-beta.69",
+    "@workflow/nest": "0.0.0-beta.22",
+    "@workflow/nitro": "4.0.1-beta.68",
+    "@workflow/nuxt": "4.0.1-beta.57",
+    "@workflow/sveltekit": "4.0.0-beta.62",
+    "@workflow/rollup": "4.0.0-beta.30"
   },
   "devDependencies": {
     "@types/ms": "2.1.0",