@voltro/cli 0.23.0 → 0.24.0

package/templates/agent-docs/database/seedsdialects.md

@@ -225,6 +225,18 @@ DB_URL=file:./db.sqlite     # or `:memory:` for ephemeral
 
 The `app.config.ts` `store:` field stays as the dev-friendly shortcut (`store: 'postgres'`, `store: 'memory'`) — env always wins.
 
+### Query timeout — bound a runaway query
+
+```sh
+DB_STATEMENT_TIMEOUT_MS=30000   # cancel any single query after 30s
+```
+
+A missing index or an accidental cartesian join can run for minutes, and while it does it **pins a pooled connection**. Enough of them under load and the pool is exhausted — every other request now waits on a connection that will never free, and the whole app stalls. `DB_STATEMENT_TIMEOUT_MS` puts a ceiling on it: a query that outlasts the deadline is cancelled, its connection returns to the pool, and the caller gets a normal error instead of a hang.
+
+It applies to the **runtime query path only**. Migrations (`voltro db apply`) run legitimately long statements — backfills, index builds — and are **never** cancelled by it. (Caveat: `voltro dev`'s boot auto-migrate shares the app connection, so a very slow dev migration under a low timeout would trip it — raise the value, or run `voltro db apply` first.)
+
+**Wired for postgres today** (the default dialect), where it maps to the server-side `statement_timeout` — a real, server-enforced cancel (SQLSTATE `57014`), not a client-side disconnect that leaves the query running. Other dialects accept the variable but currently ignore it, and the reasons are honest rather than incidental: `@effect/sql-mssql` exposes only a connection-establishment timeout, not a per-request one; MySQL/MariaDB's `max_execution_time` bounds `SELECT`s only (writes stay unbounded), which would be a misleading half-guarantee; and SQLite is in-process with a single connection, so there is no pool to protect. Unset (or any non-postgres dialect) = no timeout.
+
 ## Local development — bring up all five
 
 The framework ships a docker-compose at `voltro/test/docker-compose.yml` that brings up postgres + mysql + mariadb + mssql on distinct ports so per-dialect tests can run side-by-side and the dev fixture never clashes with your starter postgres on `:5432`:

package/templates/agent-docs/deployment.md

@@ -918,6 +918,44 @@ under `NODE_ENV=production` (it refuses unless both fingerprints still match the
 reviewed plan). A Job runs **once per release** vs an `initContainer`'s once per
 replica, so it's the better fit for a multi-replica rollout.
 
+### Expand/contract — the migration that's safe while old pods still serve
+
+The pre-deploy Job applies the schema **before the new pods roll** — so during a
+rolling update, old pods (old code) run against the already-migrated schema for
+the length of the rollout. A migration that DROPS or RENAMES a column, NARROWS a
+type, or ADDS a constraint breaks those old pods mid-rollout: they 500 reading a
+column that's gone, or their writes are rejected by the new constraint. The
+migration "succeeded" and the app served errors anyway.
+
+`voltro db plan` flags these — the operations unsafe under a rolling deploy are
+listed with a `⚠`, separately from the data-safety (lossy / blocked) gate, since
+the two are orthogonal: a `dropped()` column is blessed for data loss and *still*
+breaks an old reader.
+
+```text
+⚠ 1 operation(s) UNSAFE under a rolling deploy
+  (old + new instances overlap → old code breaks against the new schema):
+    • drop-column: old instances still SELECT/INSERT "orders"."legacy_total"; …
+      → stop reading the column in code and deploy that first; drop it in a LATER deploy
+```
+
+Two ways to handle it:
+
+1. **No overlap window** — a maintenance-window or **scale-to-zero** deploy (old
+   pods gone before new ones start) has no simultaneous old code, so a single-step
+   drop/rename is fine. The advisory doesn't apply; ignore it.
+2. **Zero-downtime rollout** — split the breaking change into two releases, each
+   of which keeps *both* code versions working (**expand/contract**):
+   - **Expand** (release N): add the new shape — a nullable column, a new table,
+     a backfill, dual-write from the new code. Old code ignores it.
+   - **Cut over**: the new code reads/writes the new shape; deploy it.
+   - **Contract** (release N+1): once no pod runs the old code, drop/rename/narrow
+     the now-unused old shape. This step's `db plan` is clean.
+
+Renaming `orders.total` → `orders.amount` under zero downtime is: add `amount`
+(expand) → backfill + dual-write → cut reads over → drop `total` (contract) — three
+releases, never one, so no in-flight pod ever references a column that isn't there.
+
 ### If you DO run `voltro dev` in a cluster (dev / staging only)
 
 `voltro dev` binds a small **boot-health surface** on its own port so a probe can
@@ -1059,6 +1097,33 @@ that route to a terminating pod before k8s finishes removing it from the Service
 endpoints. With it, that window is drained. `terminationGracePeriodSeconds` must
 be larger than the sleep plus the app's own teardown, or k8s SIGKILLs mid-drain.
 
+**Bound the app's own teardown with `VOLTRO_SHUTDOWN_GRACE_MS`.** After
+`SIGTERM`, the runtime runs its finalizers (pool close, plugin `onDeactivate`,
+analytics flush, trace persist) and then exits — but installing the signal
+handler removes node's default kill, so a finalizer that *never* completes (a
+pool drain against a database that is already gone, a wedged `onDeactivate`)
+would otherwise hang the process forever. A hard deadline caps that: teardown
+gets until the deadline, then the process exits regardless. It defaults to
+**10s**; set `VOLTRO_SHUTDOWN_GRACE_MS` (clamped to 1s–5min) to sit JUST UNDER
+your `terminationGracePeriodSeconds` minus the preStop sleep — so the app drains
+and exits *cleanly on its own* before k8s SIGKILLs it mid-drain:
+
+```yaml
+spec:
+  terminationGracePeriodSeconds: 30
+  containers:
+    - name: api
+      env:
+        # preStop sleep (5s) + app teardown (≤22s) < 30s grace, with headroom.
+        - name: VOLTRO_SHUTDOWN_GRACE_MS
+          value: "22000"
+```
+
+The close is clean on the client side too: on shutdown each live WebSocket is
+closed with a proper close frame (not an abrupt socket drop), and the web
+client's supervisor reconnects on any close — so an open dashboard re-attaches
+to a healthy replica across a rolling deploy without a page reload.
+
 ## 8. Multiple replicas
 
 Cache and KV default to **in-process** (per-replica). For a shared backend across replicas:
@@ -1087,7 +1152,7 @@ Schedules and aggregates auto-coordinate via an advisory lock on SQL stores —
 - [ ] `auth.anonymousTenantRequired: true` (unless the app serves anonymous public data)
 - [ ] `OTEL_EXPORTER_OTLP_ENDPOINT` + `OTEL_SERVICE_NAME` pointed at your collector
 - [ ] `VOLTRO_LOG_FORMAT=json`; `sentryPlugin()` + `SENTRY_DSN` for errors
-- [ ] `terminationGracePeriodSeconds` generous for graceful drain
+- [ ] `terminationGracePeriodSeconds` generous for graceful drain; `VOLTRO_SHUTDOWN_GRACE_MS` set just under it (minus the preStop sleep)
 - [ ] `CACHE_BACKEND` / `KV_BACKEND` + a cross-replica change bus when running >1 replica
 
 

package/templates/agent-docs/workflows.md

@@ -474,6 +474,36 @@ Workflow starts persist the starter subject, trace id, source, parent execution
 
 Still include tenant/user ids that the business process must enforce in `payload`, validate them in the first step, and scope store reads/writes deliberately. Payload data is replay-safe and makes authorization decisions auditable across retries and deploys.
 
+## Calling an HTTP API from a step
+
+The framework's `HttpClient` is available inside a workflow executor — the same one handlers `yield*`, with the same SSRF allowlist and the same automatic `traceparent` propagation. `yield*` it in a step:
+
+```ts
+import { HttpClient, HttpClientRequest } from '@effect/platform'
+
+export const executor = defineWorkflowExecutor(syncInvoice, (payload) =>
+  Effect.gen(function* () {
+    const remote = yield* step({ name: 'fetch-invoice' }, () =>
+      Effect.gen(function* () {
+        const client = yield* HttpClient.HttpClient
+        const res = yield* client.execute(
+          HttpClientRequest.get(`https://billing.example.com/invoices/${payload.invoiceId}`),
+        )
+        return yield* res.json
+      }),
+    )
+    yield* step({ name: 'persist' }, () => database.invoices.update(payload.invoiceId, remote))
+  }),
+)
+```
+
+Two things follow from where it sits:
+
+- **Wrap the call in a `step`.** The result is then checkpointed, so a retry or a resume after a deploy replays the recorded response instead of calling the remote again. A bare `yield*` outside a step re-issues the request on every replay — which for a payment capture or an email send is the difference between once and several times.
+- **It is the SSRF-guarded client.** Requests to internal targets are refused by the same policy handlers get; a workflow is not a way around it. Configure the allowlist once in `app.config.ts` under `http` — dev and serve read the same key, so the policy cannot differ between them.
+
+Reaching for `fetch` instead loses both: no allowlist, no trace propagation, and nothing tying the call to the step that made it.
+
 ## Anti-patterns
 
 - **Using `input` in `workflow({...})`.** The current API is `payload`.

package/templates/apps/api-ai/package.json

@@ -5,22 +5,23 @@
   "type": "module",
   "scripts": {
     "dev": "voltro dev .",
+    "lint": "voltro doctor .",
     "test": "voltro test",
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
     "@effect/platform": "^0.97.0",
     "@effect/rpc": "^0.76.0",
-    "@voltro/ai": "0.23.0",
-    "@voltro/cli": "0.23.0",
-    "@voltro/database": "0.23.0",
-    "@voltro/env": "0.23.0",
-    "@voltro/protocol": "0.23.0",
-    "@voltro/runtime": "0.23.0",
+    "@voltro/ai": "0.24.0",
+    "@voltro/cli": "0.24.0",
+    "@voltro/database": "0.24.0",
+    "@voltro/env": "0.24.0",
+    "@voltro/protocol": "0.24.0",
+    "@voltro/runtime": "0.24.0",
     "effect": "^3.22.0"
   },
   "devDependencies": {
-    "@voltro/testing": "0.23.0",
+    "@voltro/testing": "0.24.0",
     "typescript": "^6.0.3",
     "vitest": "^4.1.10"
   }

package/templates/apps/api-auth/package.json

@@ -5,6 +5,7 @@
   "type": "module",
   "scripts": {
     "dev": "voltro dev .",
+    "lint": "voltro doctor .",
     "migrate": "voltro migrate",
     "test": "voltro test",
     "typecheck": "tsc --noEmit"
@@ -12,17 +13,17 @@
   "dependencies": {
     "@effect/platform": "^0.97.0",
     "@effect/rpc": "^0.76.0",
-    "@voltro/cli": "0.23.0",
-    "@voltro/database": "0.23.0",
-    "@voltro/env": "0.23.0",
-    "@voltro/plugin-auth": "0.23.0",
-    "@voltro/protocol": "0.23.0",
-    "@voltro/runtime": "0.23.0",
-    "@voltro/sql-postgres": "0.23.0",
+    "@voltro/cli": "0.24.0",
+    "@voltro/database": "0.24.0",
+    "@voltro/env": "0.24.0",
+    "@voltro/plugin-auth": "0.24.0",
+    "@voltro/protocol": "0.24.0",
+    "@voltro/runtime": "0.24.0",
+    "@voltro/sql-postgres": "0.24.0",
     "effect": "^3.22.0"
   },
   "devDependencies": {
-    "@voltro/testing": "0.23.0",
+    "@voltro/testing": "0.24.0",
     "typescript": "^6.0.3",
     "vitest": "^4.1.10"
   }

package/templates/apps/api-backend/package.json

@@ -5,6 +5,7 @@
   "type": "module",
   "scripts": {
     "dev": "voltro dev .",
+    "lint": "voltro doctor .",
     "migrate": "voltro migrate",
     "test": "voltro test",
     "typecheck": "tsc --noEmit"
@@ -12,16 +13,16 @@
   "dependencies": {
     "@effect/platform": "^0.97.0",
     "@effect/rpc": "^0.76.0",
-    "@voltro/cli": "0.23.0",
-    "@voltro/database": "0.23.0",
-    "@voltro/env": "0.23.0",
-    "@voltro/plugin-multitenancy": "0.23.0",
-    "@voltro/protocol": "0.23.0",
-    "@voltro/runtime": "0.23.0",
+    "@voltro/cli": "0.24.0",
+    "@voltro/database": "0.24.0",
+    "@voltro/env": "0.24.0",
+    "@voltro/plugin-multitenancy": "0.24.0",
+    "@voltro/protocol": "0.24.0",
+    "@voltro/runtime": "0.24.0",
     "effect": "^3.22.0"
   },
   "devDependencies": {
-    "@voltro/testing": "0.23.0",
+    "@voltro/testing": "0.24.0",
     "typescript": "^6.0.3",
     "vitest": "^4.1.10"
   }

package/templates/apps/api-backend-deactivation/package.json

@@ -5,6 +5,7 @@
   "type": "module",
   "scripts": {
     "dev": "voltro dev .",
+    "lint": "voltro doctor .",
     "migrate": "voltro migrate",
     "test": "voltro test",
     "typecheck": "tsc --noEmit"
@@ -12,16 +13,16 @@
   "dependencies": {
     "@effect/platform": "^0.97.0",
     "@effect/rpc": "^0.76.0",
-    "@voltro/cli": "0.23.0",
-    "@voltro/database": "0.23.0",
-    "@voltro/env": "0.23.0",
-    "@voltro/plugin-deactivation": "0.23.0",
-    "@voltro/protocol": "0.23.0",
-    "@voltro/runtime": "0.23.0",
+    "@voltro/cli": "0.24.0",
+    "@voltro/database": "0.24.0",
+    "@voltro/env": "0.24.0",
+    "@voltro/plugin-deactivation": "0.24.0",
+    "@voltro/protocol": "0.24.0",
+    "@voltro/runtime": "0.24.0",
     "effect": "^3.22.0"
   },
   "devDependencies": {
-    "@voltro/testing": "0.23.0",
+    "@voltro/testing": "0.24.0",
     "typescript": "^6.0.3",
     "vitest": "^4.1.10"
   }

package/templates/apps/api-backend-mail/package.json

@@ -5,6 +5,7 @@
   "type": "module",
   "scripts": {
     "dev": "voltro dev .",
+    "lint": "voltro doctor .",
     "migrate": "voltro migrate",
     "typecheck": "tsc --noEmit",
     "test": "voltro test"
@@ -12,18 +13,18 @@
   "dependencies": {
     "@react-email/components": "^1.0.12",
     "@react-email/render": "^1.4.0",
-    "@voltro/cli": "0.23.0",
-    "@voltro/database": "0.23.0",
-    "@voltro/env": "0.23.0",
-    "@voltro/plugin-mail": "0.23.0",
-    "@voltro/plugin-multitenancy": "0.23.0",
-    "@voltro/protocol": "0.23.0",
-    "@voltro/runtime": "0.23.0",
+    "@voltro/cli": "0.24.0",
+    "@voltro/database": "0.24.0",
+    "@voltro/env": "0.24.0",
+    "@voltro/plugin-mail": "0.24.0",
+    "@voltro/plugin-multitenancy": "0.24.0",
+    "@voltro/protocol": "0.24.0",
+    "@voltro/runtime": "0.24.0",
     "effect": "^3.22.0",
     "react": "^19.0.0"
   },
   "devDependencies": {
-    "@voltro/testing": "0.23.0",
+    "@voltro/testing": "0.24.0",
     "typescript": "^6.0.3",
     "vitest": "^4.1.10"
   }

package/templates/apps/api-backend-mariadb/package.json

@@ -5,6 +5,7 @@
   "type": "module",
   "scripts": {
     "dev": "voltro dev .",
+    "lint": "voltro doctor .",
     "migrate": "voltro migrate",
     "test": "voltro test",
     "typecheck": "tsc --noEmit"
@@ -12,18 +13,18 @@
   "dependencies": {
     "@effect/platform": "^0.97.0",
     "@effect/rpc": "^0.76.0",
-    "@voltro/cli": "0.23.0",
-    "@voltro/database": "0.23.0",
-    "@voltro/env": "0.23.0",
-    "@voltro/plugin-multitenancy": "0.23.0",
-    "@voltro/plugin-storage": "0.23.0",
-    "@voltro/protocol": "0.23.0",
-    "@voltro/runtime": "0.23.0",
-    "@voltro/sql-mysql": "0.23.0",
+    "@voltro/cli": "0.24.0",
+    "@voltro/database": "0.24.0",
+    "@voltro/env": "0.24.0",
+    "@voltro/plugin-multitenancy": "0.24.0",
+    "@voltro/plugin-storage": "0.24.0",
+    "@voltro/protocol": "0.24.0",
+    "@voltro/runtime": "0.24.0",
+    "@voltro/sql-mysql": "0.24.0",
     "effect": "^3.22.0"
   },
   "devDependencies": {
-    "@voltro/testing": "0.23.0",
+    "@voltro/testing": "0.24.0",
     "typescript": "^6.0.3",
     "vitest": "^4.1.10"
   }

package/templates/apps/api-backend-storage/package.json

@@ -5,22 +5,23 @@
   "type": "module",
   "scripts": {
     "dev": "voltro dev .",
+    "lint": "voltro doctor .",
     "migrate": "voltro migrate",
     "typecheck": "tsc --noEmit",
     "test": "voltro test"
   },
   "dependencies": {
-    "@voltro/cli": "0.23.0",
-    "@voltro/database": "0.23.0",
-    "@voltro/env": "0.23.0",
-    "@voltro/plugin-multitenancy": "0.23.0",
-    "@voltro/plugin-storage": "0.23.0",
-    "@voltro/protocol": "0.23.0",
-    "@voltro/runtime": "0.23.0",
+    "@voltro/cli": "0.24.0",
+    "@voltro/database": "0.24.0",
+    "@voltro/env": "0.24.0",
+    "@voltro/plugin-multitenancy": "0.24.0",
+    "@voltro/plugin-storage": "0.24.0",
+    "@voltro/protocol": "0.24.0",
+    "@voltro/runtime": "0.24.0",
     "effect": "^3.22.0"
   },
   "devDependencies": {
-    "@voltro/testing": "0.23.0",
+    "@voltro/testing": "0.24.0",
     "typescript": "^6.0.3",
     "vitest": "^4.1.10"
   }

package/templates/apps/api-data-advanced/package.json

@@ -5,23 +5,24 @@
   "type": "module",
   "scripts": {
     "dev": "voltro dev .",
+    "lint": "voltro doctor .",
     "test": "voltro test",
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
     "@effect/platform": "^0.97.0",
     "@effect/rpc": "^0.76.0",
-    "@voltro/cli": "0.23.0",
-    "@voltro/database": "0.23.0",
-    "@voltro/env": "0.23.0",
-    "@voltro/plugin-governance": "0.23.0",
-    "@voltro/plugin-multitenancy": "0.23.0",
-    "@voltro/protocol": "0.23.0",
-    "@voltro/runtime": "0.23.0",
+    "@voltro/cli": "0.24.0",
+    "@voltro/database": "0.24.0",
+    "@voltro/env": "0.24.0",
+    "@voltro/plugin-governance": "0.24.0",
+    "@voltro/plugin-multitenancy": "0.24.0",
+    "@voltro/protocol": "0.24.0",
+    "@voltro/runtime": "0.24.0",
     "effect": "^3.22.0"
   },
   "devDependencies": {
-    "@voltro/testing": "0.23.0",
+    "@voltro/testing": "0.24.0",
     "typescript": "^6.0.3",
     "vitest": "^4.1.10"
   }

package/templates/apps/api-durable/package.json

@@ -5,23 +5,24 @@
   "type": "module",
   "scripts": {
     "dev": "voltro dev .",
+    "lint": "voltro doctor .",
     "test": "voltro test",
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
     "@effect/platform": "^0.97.0",
     "@effect/rpc": "^0.76.0",
-    "@voltro/cli": "0.23.0",
-    "@voltro/database": "0.23.0",
-    "@voltro/env": "0.23.0",
-    "@voltro/plugin-multitenancy": "0.23.0",
-    "@voltro/protocol": "0.23.0",
-    "@voltro/runtime": "0.23.0",
-    "@voltro/workflow": "0.23.0",
+    "@voltro/cli": "0.24.0",
+    "@voltro/database": "0.24.0",
+    "@voltro/env": "0.24.0",
+    "@voltro/plugin-multitenancy": "0.24.0",
+    "@voltro/protocol": "0.24.0",
+    "@voltro/runtime": "0.24.0",
+    "@voltro/workflow": "0.24.0",
     "effect": "^3.22.0"
   },
   "devDependencies": {
-    "@voltro/testing": "0.23.0",
+    "@voltro/testing": "0.24.0",
     "typescript": "^6.0.3",
     "vitest": "^4.1.10"
   }

package/templates/apps/api-feature-flags/package.json

@@ -5,6 +5,7 @@
   "type": "module",
   "scripts": {
     "dev": "voltro dev .",
+    "lint": "voltro doctor .",
     "migrate": "voltro migrate",
     "test": "voltro test",
     "typecheck": "tsc --noEmit"
@@ -12,18 +13,18 @@
   "dependencies": {
     "@effect/platform": "^0.97.0",
     "@effect/rpc": "^0.76.0",
-    "@voltro/cli": "0.23.0",
-    "@voltro/database": "0.23.0",
-    "@voltro/env": "0.23.0",
-    "@voltro/plugin-flags": "0.23.0",
-    "@voltro/plugin-multitenancy": "0.23.0",
-    "@voltro/protocol": "0.23.0",
-    "@voltro/runtime": "0.23.0",
-    "@voltro/sql-postgres": "0.23.0",
+    "@voltro/cli": "0.24.0",
+    "@voltro/database": "0.24.0",
+    "@voltro/env": "0.24.0",
+    "@voltro/plugin-flags": "0.24.0",
+    "@voltro/plugin-multitenancy": "0.24.0",
+    "@voltro/protocol": "0.24.0",
+    "@voltro/runtime": "0.24.0",
+    "@voltro/sql-postgres": "0.24.0",
     "effect": "^3.22.0"
   },
   "devDependencies": {
-    "@voltro/testing": "0.23.0",
+    "@voltro/testing": "0.24.0",
     "typescript": "^6.0.3",
     "vitest": "^4.1.10"
   }

package/templates/apps/api-governance/package.json

@@ -5,6 +5,7 @@
   "type": "module",
   "scripts": {
     "dev": "voltro dev .",
+    "lint": "voltro doctor .",
     "migrate": "voltro migrate",
     "test": "voltro test",
     "typecheck": "tsc --noEmit"
@@ -12,17 +13,17 @@
   "dependencies": {
     "@effect/platform": "^0.97.0",
     "@effect/rpc": "^0.76.0",
-    "@voltro/cli": "0.23.0",
-    "@voltro/database": "0.23.0",
-    "@voltro/env": "0.23.0",
-    "@voltro/plugin-audit": "0.23.0",
-    "@voltro/plugin-governance": "0.23.0",
-    "@voltro/protocol": "0.23.0",
-    "@voltro/runtime": "0.23.0",
+    "@voltro/cli": "0.24.0",
+    "@voltro/database": "0.24.0",
+    "@voltro/env": "0.24.0",
+    "@voltro/plugin-audit": "0.24.0",
+    "@voltro/plugin-governance": "0.24.0",
+    "@voltro/protocol": "0.24.0",
+    "@voltro/runtime": "0.24.0",
     "effect": "^3.22.0"
   },
   "devDependencies": {
-    "@voltro/testing": "0.23.0",
+    "@voltro/testing": "0.24.0",
     "typescript": "^6.0.3",
     "vitest": "^4.1.10"
   }

package/templates/apps/api-kv/package.json

@@ -5,23 +5,24 @@
   "type": "module",
   "scripts": {
     "dev": "voltro dev .",
+    "lint": "voltro doctor .",
     "test": "voltro test",
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
     "@effect/platform": "^0.97.0",
     "@effect/rpc": "^0.76.0",
-    "@voltro/cli": "0.23.0",
-    "@voltro/database": "0.23.0",
-    "@voltro/env": "0.23.0",
-    "@voltro/kv": "0.23.0",
-    "@voltro/plugin-multitenancy": "0.23.0",
-    "@voltro/protocol": "0.23.0",
-    "@voltro/runtime": "0.23.0",
+    "@voltro/cli": "0.24.0",
+    "@voltro/database": "0.24.0",
+    "@voltro/env": "0.24.0",
+    "@voltro/kv": "0.24.0",
+    "@voltro/plugin-multitenancy": "0.24.0",
+    "@voltro/protocol": "0.24.0",
+    "@voltro/runtime": "0.24.0",
     "effect": "^3.22.0"
   },
   "devDependencies": {
-    "@voltro/testing": "0.23.0",
+    "@voltro/testing": "0.24.0",
     "typescript": "^6.0.3",
     "vitest": "^4.1.10"
   }

package/templates/apps/api-moderation/package.json

@@ -5,6 +5,7 @@
   "type": "module",
   "scripts": {
     "dev": "voltro dev .",
+    "lint": "voltro doctor .",
     "migrate": "voltro migrate",
     "test": "voltro test",
     "typecheck": "tsc --noEmit"
@@ -12,17 +13,17 @@
   "dependencies": {
     "@effect/platform": "^0.97.0",
     "@effect/rpc": "^0.76.0",
-    "@voltro/cli": "0.23.0",
-    "@voltro/database": "0.23.0",
-    "@voltro/env": "0.23.0",
-    "@voltro/plugin-moderation": "0.23.0",
-    "@voltro/plugin-multitenancy": "0.23.0",
-    "@voltro/protocol": "0.23.0",
-    "@voltro/runtime": "0.23.0",
+    "@voltro/cli": "0.24.0",
+    "@voltro/database": "0.24.0",
+    "@voltro/env": "0.24.0",
+    "@voltro/plugin-moderation": "0.24.0",
+    "@voltro/plugin-multitenancy": "0.24.0",
+    "@voltro/protocol": "0.24.0",
+    "@voltro/runtime": "0.24.0",
     "effect": "^3.22.0"
   },
   "devDependencies": {
-    "@voltro/testing": "0.23.0",
+    "@voltro/testing": "0.24.0",
     "typescript": "^6.0.3",
     "vitest": "^4.1.10"
   }

package/templates/apps/api-observability/package.json

@@ -5,6 +5,7 @@
   "type": "module",
   "scripts": {
     "dev": "voltro dev .",
+    "lint": "voltro doctor .",
     "migrate": "voltro migrate",
     "test": "voltro test",
     "typecheck": "tsc --noEmit"
@@ -12,17 +13,17 @@
   "dependencies": {
     "@effect/platform": "^0.97.0",
     "@effect/rpc": "^0.76.0",
-    "@voltro/cli": "0.23.0",
-    "@voltro/database": "0.23.0",
-    "@voltro/plugin-multitenancy": "0.23.0",
-    "@voltro/plugin-prometheus": "0.23.0",
-    "@voltro/plugin-sentry": "0.23.0",
-    "@voltro/protocol": "0.23.0",
-    "@voltro/runtime": "0.23.0",
+    "@voltro/cli": "0.24.0",
+    "@voltro/database": "0.24.0",
+    "@voltro/plugin-multitenancy": "0.24.0",
+    "@voltro/plugin-prometheus": "0.24.0",
+    "@voltro/plugin-sentry": "0.24.0",
+    "@voltro/protocol": "0.24.0",
+    "@voltro/runtime": "0.24.0",
     "effect": "^3.22.0"
   },
   "devDependencies": {
-    "@voltro/testing": "0.23.0",
+    "@voltro/testing": "0.24.0",
     "typescript": "^6.0.3",
     "vitest": "^4.1.10"
   }