@voltro/cli 0.2.2 → 0.4.0

package/templates/agent-docs/testing.md

@@ -26,6 +26,7 @@ Everything in it is in-memory and synchronous-friendly — no docker, no running
 | `makeTestContext(options?)` | The request `ctx` a handler/tool sees at runtime — subject-scoped `ctx.store`, `clock`, `email`, optional `ai`. → [Unit testing](/docs/testing/unit-testing) |
 | `mockStore(seed)` | Seed rows: `makeTestContext({ store: mockStore({ todos: [...] }) })`. |
 | `MockClock` / `MockEmail` / `MockLLM` | Deterministic clock, captured email, queued LLM responses. |
+| `makeVoltroTestClient(config)` | The frontend harness — render a component against mocked `useSubscription` / `useMutation`, from the `@voltro/testing/client` subpath. → [Component testing](/docs/testing/component-testing) |
 | `makeWorkflowRunner({ ctx, workflows })` | Drive a workflow in-process and assert on its steps. → [Workflows](/docs/testing/workflows) |
 | `runDialectParity(fixture)` | Run one fixture across a SQL dialect for portability — from the `@voltro/testing/dialect` subpath. → [Dialect parity](/docs/testing/dialect-parity) |
 
@@ -34,9 +35,10 @@ Everything in it is in-memory and synchronous-friendly — no docker, no running
 Voltro's primitives are designed so the cheapest test covers the most surface. Reach for the lowest layer that proves what you need:
 
 1. **Unit — handlers, tools, mutations, queries.** Call the executor directly with a `makeTestContext()` ctx. The store is the real mixin-wrapped store, so tenant scoping, soft-delete, and audit auto-fill all behave as in production — without a database. This is 90% of your tests. See [Unit testing](/docs/testing/unit-testing).
-2. **Workflow — durable, multi-step logic.** `makeWorkflowRunner` drives a workflow end-to-end in-process and hands back the same step log the dashboard shows, including real retry counts. See [Workflows](/docs/testing/workflows).
-3. **Parity — hand-written SQL that must stay portable.** `runDialectParity` runs a fixed scenario suite against a dialect you stand up. Mostly for dialect-package authors and apps with `unsafe()` SQL. See [Dialect parity](/docs/testing/dialect-parity).
-4. **End-to-end — the running stack.** `voltro e2e` boots the api + web siblings, runs your tests against the live processes, and tears them down.
+2. **Component — the reactive frontend.** `makeVoltroTestClient` renders a component against mocked `useSubscription` / `useMutation`, so loading, empty, stream-error and failing-write branches are all assertable without a running server. See [Component testing](/docs/testing/component-testing).
+3. **Workflow — durable, multi-step logic.** `makeWorkflowRunner` drives a workflow end-to-end in-process and hands back the same step log the dashboard shows, including real retry counts. See [Workflows](/docs/testing/workflows).
+4. **Parity — hand-written SQL that must stay portable.** `runDialectParity` runs a fixed scenario suite against a dialect you stand up. Mostly for dialect-package authors and apps with `unsafe()` SQL. See [Dialect parity](/docs/testing/dialect-parity).
+5. **End-to-end — the running stack.** `voltro e2e` boots the api + web siblings, runs your tests against the live processes, and tears them down.
 
 Agents are integration tests; tools are unit tests. Don't reach for an e2e harness to assert logic a `makeTestContext` test can prove.
 
@@ -231,6 +233,178 @@ mock.reset()
 
 
 
+---
+
+<!-- source: en/testing/component-testing.md -->
+## Component testing
+
+_makeVoltroTestClient — the frontend test harness. Render a component against mocked useSubscription / useMutation, inject a loading state, a stream error or a failing write, and assert on every recorded call._
+
+## Why this exists
+
+A Voltro frontend is a **reactive-data app**. Its components don't take props and render — they call `useSubscription` for live data and `useMutation` / `useAction` to write. Without a way to render such a component against mocked hooks — and to inject a loading state, a stream error, or a failing write — a component is **structurally untestable**: there is no seam to hand it data, and nothing to assert against. That is exactly why real apps end up with zero frontend tests.
+
+`makeVoltroTestClient` closes that gap. It builds a fake api context, hands you a `Provider` to wrap the component under test, and gives you the controls to drive it.
+
+```bash
+pnpm --filter @my-app/web add -D @voltro/testing vitest jsdom react-dom
+```
+
+Import from the **`/client` subpath**, so backend-only test files never pull React:
+
+```ts
+import { makeVoltroTestClient } from '@voltro/testing/client'
+```
+
+## The surface
+
+```ts
+const harness = makeVoltroTestClient({
+  apiName:       'app',                                  // default 'app'
+  subscriptions: { 'todos.list': [{ id: '1', title: 'x' }] },
+  mutations:     { 'todos.create': (input) => ({ id: '2' }) },
+  actions:       { 'todos.export': async () => ({ url: '/x.csv' }) },
+})
+```
+
+| Config | Meaning |
+|---|---|
+| `apiName` | The api name your components pass to the hooks. Default `'app'`. Asking for a different one throws a loud, named error rather than rendering nothing. |
+| `subscriptions` | Initial data per rpc tag. A tag that is **absent stays in the loading state**. |
+| `mutations` | Handlers per tag. Throw (or reject) to exercise the failure path. |
+| `actions` | Handlers per tag, same shape. |
+
+| Returned | Use |
+|---|---|
+| `Provider` | Wrap the component under test. Takes `children`, returns an element. |
+| `setSubscription(tag, data)` | Push new data for a tag — components re-render, exactly like a server delta. |
+| `failSubscription(tag, error)` | Put a tag into the **cold-start error state** (no snapshot + an error). |
+| `resetSubscription(tag)` | Return a tag to the loading state (no snapshot yet). |
+| `calls` | Every mutation / action invoked so far, in order — `{ kind, tag, input }`. |
+
+### Absent tag = loading
+
+This is the distinction most worth testing and the easiest to get wrong. A tag with **no fixture** renders the component's loading branch; a tag whose fixture is `[]` renders the *empty* branch. Real apps routinely conflate the two and ship a skeleton that never resolves. The harness makes both states one line apart.
+
+### It is deliberately not a renderer
+
+The harness hands you a `Provider` and nothing else about rendering. It works with `react-dom/client` + `act`, with testing-library, or with your own harness, and locks you into none of them. This repo's own tests use `react-dom/client` directly — there is no `@testing-library` dependency anywhere in the framework.
+
+## A worked example
+
+Two things React needs before any of this runs: a **DOM environment** (the `// @vitest-environment jsdom` docblock, per file) and **`IS_REACT_ACT_ENVIRONMENT = true`**, without which React refuses to honour `act()` outside a runner it recognises.
+
+```tsx
+// @vitest-environment jsdom
+import { describe, expect, it } from 'vitest'
+import { act, createElement, type ReactElement } from 'react'
+import { createRoot } from 'react-dom/client'
+import { useSubscription, useMutation } from '@voltro/client'
+import { makeVoltroTestClient } from '@voltro/testing/client'
+
+// React requires this flag before it will honour act().
+;(globalThis as { IS_REACT_ACT_ENVIRONMENT?: boolean }).IS_REACT_ACT_ENVIRONMENT = true
+
+// The component under test — ordinary app code, no test seams of its own.
+const TodoList = (): ReactElement => {
+  const { data, loading, isEmpty } = useSubscription<Array<{ id: string; title: string }>>('app', 'todos.list', {})
+  const create = useMutation<{ title: string }, { id: string }>('app', 'todos.create')
+  if (loading) return <p>loading</p>
+  if (isEmpty) return <p>empty</p>
+  return (
+    <div>
+      <ul>{(data ?? []).map((t) => <li key={t.id}>{t.title}</li>)}</ul>
+      <button onClick={() => { void create.mutate({ title: 'new' }, {}) }}>add</button>
+    </div>
+  )
+}
+
+const mount = (harness: ReturnType<typeof makeVoltroTestClient>) => {
+  const host = document.createElement('div')
+  const root = createRoot(host)
+  act(() => { root.render(createElement(harness.Provider, null, createElement(TodoList))) })
+  return {
+    html: () => host.innerHTML,
+    find: <E extends Element>(selector: string): E | null => host.querySelector<E>(selector),
+    unmount: () => act(() => { root.unmount() }),
+  }
+}
+
+describe('TodoList', () => {
+  it('renders the loading state when the tag has no data yet', () => {
+    const h = makeVoltroTestClient()                       // no fixture for todos.list
+    const view = mount(h)
+    expect(view.html()).toContain('loading')
+    view.unmount()
+  })
+
+  it('distinguishes EMPTY from loading', () => {
+    const h = makeVoltroTestClient({ subscriptions: { 'todos.list': [] } })
+    const view = mount(h)
+    expect(view.html()).toContain('empty')
+    expect(view.html()).not.toContain('loading')
+    view.unmount()
+  })
+
+  it('re-renders when a server delta arrives', () => {
+    const h = makeVoltroTestClient({ subscriptions: { 'todos.list': [{ id: '1', title: 'first' }] } })
+    const view = mount(h)
+    expect(view.html()).toContain('first')
+
+    act(() => { h.setSubscription('todos.list', [{ id: '1', title: 'first' }, { id: '2', title: 'second' }]) })
+    expect(view.html()).toContain('second')
+    view.unmount()
+  })
+
+  it('handles a dead stream', () => {
+    const h = makeVoltroTestClient({ subscriptions: { 'todos.list': [{ id: '1', title: 'x' }] } })
+    const view = mount(h)
+    act(() => { h.failSubscription('todos.list', new Error('stream died')) })
+    expect(view.html()).toContain('loading')   // no snapshot → the loading branch
+    view.unmount()
+  })
+
+  it('records the write with its input', async () => {
+    const h = makeVoltroTestClient({
+      subscriptions: { 'todos.list': [{ id: '1', title: 'x' }] },
+      mutations:     { 'todos.create': () => ({ id: '2' }) },
+    })
+    const view = mount(h)
+    await act(async () => { view.find<HTMLButtonElement>('button')?.click() })
+    expect(h.calls).toEqual([{ kind: 'mutation', tag: 'todos.create', input: { title: 'new' } }])
+    view.unmount()
+  })
+})
+```
+
+## Testing the failure paths
+
+The three failure modes a reactive frontend actually ships broken:
+
+- **The infinite skeleton.** `failSubscription(tag, error)` drops the snapshot and sets an error — the cold-start case where data never arrived at all. If your component only branches on `data`, this is the test that catches it.
+- **The write that rejects.** A `mutations` handler that throws surfaces through the component's own error handling. Pass an `onError` to `mutate` and the promise resolves instead of rejecting — assert both that the handler saw the error and that the component still rendered.
+- **The wrong api.** A component asking for an api the harness wasn't built for throws a named error telling you to pass `{ apiName }`, instead of silently rendering an empty tree.
+
+```tsx
+const seen: unknown[] = []
+const h = makeVoltroTestClient({
+  subscriptions: { 'todos.list': [{ id: '1', title: 'x' }] },
+  mutations:     { 'todos.create': () => { throw new Error('nope') } },
+})
+// … click the button, with onError: (e) => { seen.push(e) } …
+expect(h.calls).toHaveLength(1)      // the write was attempted
+expect(seen).toHaveLength(1)         // handled, not an unhandled rejection
+expect(view.html()).toContain('x')   // and the component survived
+```
+
+## What NOT to do
+
+- **Don't mock `@voltro/client` yourself.** Module-mocking the hooks gives you a component that renders but proves nothing about subscription lifecycle — loading, delta, error. The harness drives the real hooks against a fake cache.
+- **Don't reach for e2e to assert a render branch.** Booting api + web to check that an empty list shows "empty" is minutes of runtime for something a `makeVoltroTestClient` test proves in milliseconds. Keep e2e for the flows that genuinely cross the wire.
+- **Don't forget the docblock.** Without `// @vitest-environment jsdom` on the file, `document` doesn't exist and the failure message points at React, not at the missing environment.
+
+
+
 ---
 
 <!-- source: en/testing/workflows.md -->

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

@@ -11,16 +11,16 @@
   "dependencies": {
     "@effect/platform": "^0.96.1",
     "@effect/rpc": "^0.75.1",
-    "@voltro/ai": "0.2.2",
-    "@voltro/cli": "0.2.2",
-    "@voltro/database": "0.2.2",
-    "@voltro/env": "0.2.2",
-    "@voltro/protocol": "0.2.2",
-    "@voltro/runtime": "0.2.2",
+    "@voltro/ai": "0.4.0",
+    "@voltro/cli": "0.4.0",
+    "@voltro/database": "0.4.0",
+    "@voltro/env": "0.4.0",
+    "@voltro/protocol": "0.4.0",
+    "@voltro/runtime": "0.4.0",
     "effect": "^3.21.2"
   },
   "devDependencies": {
-    "@voltro/testing": "0.2.2",
+    "@voltro/testing": "0.4.0",
     "typescript": "^5.7.0",
     "vitest": "^3.0.0"
   }

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

@@ -12,17 +12,17 @@
   "dependencies": {
     "@effect/platform": "^0.96.1",
     "@effect/rpc": "^0.75.1",
-    "@voltro/cli": "0.2.2",
-    "@voltro/database": "0.2.2",
-    "@voltro/env": "0.2.2",
-    "@voltro/plugin-auth": "0.2.2",
-    "@voltro/protocol": "0.2.2",
-    "@voltro/runtime": "0.2.2",
-    "@voltro/sql-postgres": "0.2.2",
+    "@voltro/cli": "0.4.0",
+    "@voltro/database": "0.4.0",
+    "@voltro/env": "0.4.0",
+    "@voltro/plugin-auth": "0.4.0",
+    "@voltro/protocol": "0.4.0",
+    "@voltro/runtime": "0.4.0",
+    "@voltro/sql-postgres": "0.4.0",
     "effect": "^3.21.2"
   },
   "devDependencies": {
-    "@voltro/testing": "0.2.2",
+    "@voltro/testing": "0.4.0",
     "typescript": "^5.7.0",
     "vitest": "^3.0.0"
   }

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

@@ -12,16 +12,16 @@
   "dependencies": {
     "@effect/platform": "^0.96.1",
     "@effect/rpc": "^0.75.1",
-    "@voltro/cli": "0.2.2",
-    "@voltro/database": "0.2.2",
-    "@voltro/env": "0.2.2",
-    "@voltro/plugin-multitenancy": "0.2.2",
-    "@voltro/protocol": "0.2.2",
-    "@voltro/runtime": "0.2.2",
+    "@voltro/cli": "0.4.0",
+    "@voltro/database": "0.4.0",
+    "@voltro/env": "0.4.0",
+    "@voltro/plugin-multitenancy": "0.4.0",
+    "@voltro/protocol": "0.4.0",
+    "@voltro/runtime": "0.4.0",
     "effect": "^3.21.2"
   },
   "devDependencies": {
-    "@voltro/testing": "0.2.2",
+    "@voltro/testing": "0.4.0",
     "typescript": "^5.7.0",
     "vitest": "^3.0.0"
   }

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

@@ -12,16 +12,16 @@
   "dependencies": {
     "@effect/platform": "^0.96.1",
     "@effect/rpc": "^0.75.1",
-    "@voltro/cli": "0.2.2",
-    "@voltro/database": "0.2.2",
-    "@voltro/env": "0.2.2",
-    "@voltro/plugin-deactivation": "0.2.2",
-    "@voltro/protocol": "0.2.2",
-    "@voltro/runtime": "0.2.2",
+    "@voltro/cli": "0.4.0",
+    "@voltro/database": "0.4.0",
+    "@voltro/env": "0.4.0",
+    "@voltro/plugin-deactivation": "0.4.0",
+    "@voltro/protocol": "0.4.0",
+    "@voltro/runtime": "0.4.0",
     "effect": "^3.21.2"
   },
   "devDependencies": {
-    "@voltro/testing": "0.2.2",
+    "@voltro/testing": "0.4.0",
     "typescript": "^5.7.0",
     "vitest": "^3.0.0"
   }

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

@@ -12,18 +12,18 @@
   "dependencies": {
     "@react-email/components": "^1.0.12",
     "@react-email/render": "^1.4.0",
-    "@voltro/cli": "0.2.2",
-    "@voltro/database": "0.2.2",
-    "@voltro/env": "0.2.2",
-    "@voltro/plugin-mail": "0.2.2",
-    "@voltro/plugin-multitenancy": "0.2.2",
-    "@voltro/protocol": "0.2.2",
-    "@voltro/runtime": "0.2.2",
+    "@voltro/cli": "0.4.0",
+    "@voltro/database": "0.4.0",
+    "@voltro/env": "0.4.0",
+    "@voltro/plugin-mail": "0.4.0",
+    "@voltro/plugin-multitenancy": "0.4.0",
+    "@voltro/protocol": "0.4.0",
+    "@voltro/runtime": "0.4.0",
     "effect": "^3.21.2",
     "react": "^19.0.0"
   },
   "devDependencies": {
-    "@voltro/testing": "0.2.2",
+    "@voltro/testing": "0.4.0",
     "typescript": "^5.7.0",
     "vitest": "^3.0.0"
   }

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

@@ -12,18 +12,18 @@
   "dependencies": {
     "@effect/platform": "^0.96.1",
     "@effect/rpc": "^0.75.1",
-    "@voltro/cli": "0.2.2",
-    "@voltro/database": "0.2.2",
-    "@voltro/env": "0.2.2",
-    "@voltro/plugin-multitenancy": "0.2.2",
-    "@voltro/plugin-storage": "0.2.2",
-    "@voltro/protocol": "0.2.2",
-    "@voltro/runtime": "0.2.2",
-    "@voltro/sql-mysql": "0.2.2",
+    "@voltro/cli": "0.4.0",
+    "@voltro/database": "0.4.0",
+    "@voltro/env": "0.4.0",
+    "@voltro/plugin-multitenancy": "0.4.0",
+    "@voltro/plugin-storage": "0.4.0",
+    "@voltro/protocol": "0.4.0",
+    "@voltro/runtime": "0.4.0",
+    "@voltro/sql-mysql": "0.4.0",
     "effect": "^3.21.2"
   },
   "devDependencies": {
-    "@voltro/testing": "0.2.2",
+    "@voltro/testing": "0.4.0",
     "typescript": "^5.7.0",
     "vitest": "^3.0.0"
   }

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

@@ -10,17 +10,17 @@
     "test": "voltro test"
   },
   "dependencies": {
-    "@voltro/cli": "0.2.2",
-    "@voltro/database": "0.2.2",
-    "@voltro/env": "0.2.2",
-    "@voltro/plugin-multitenancy": "0.2.2",
-    "@voltro/plugin-storage": "0.2.2",
-    "@voltro/protocol": "0.2.2",
-    "@voltro/runtime": "0.2.2",
+    "@voltro/cli": "0.4.0",
+    "@voltro/database": "0.4.0",
+    "@voltro/env": "0.4.0",
+    "@voltro/plugin-multitenancy": "0.4.0",
+    "@voltro/plugin-storage": "0.4.0",
+    "@voltro/protocol": "0.4.0",
+    "@voltro/runtime": "0.4.0",
     "effect": "^3.21.2"
   },
   "devDependencies": {
-    "@voltro/testing": "0.2.2",
+    "@voltro/testing": "0.4.0",
     "typescript": "^5.7.0",
     "vitest": "^3.0.0"
   }

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

@@ -11,17 +11,17 @@
   "dependencies": {
     "@effect/platform": "^0.96.1",
     "@effect/rpc": "^0.75.1",
-    "@voltro/cli": "0.2.2",
-    "@voltro/database": "0.2.2",
-    "@voltro/env": "0.2.2",
-    "@voltro/plugin-governance": "0.2.2",
-    "@voltro/plugin-multitenancy": "0.2.2",
-    "@voltro/protocol": "0.2.2",
-    "@voltro/runtime": "0.2.2",
+    "@voltro/cli": "0.4.0",
+    "@voltro/database": "0.4.0",
+    "@voltro/env": "0.4.0",
+    "@voltro/plugin-governance": "0.4.0",
+    "@voltro/plugin-multitenancy": "0.4.0",
+    "@voltro/protocol": "0.4.0",
+    "@voltro/runtime": "0.4.0",
     "effect": "^3.21.2"
   },
   "devDependencies": {
-    "@voltro/testing": "0.2.2",
+    "@voltro/testing": "0.4.0",
     "typescript": "^5.7.0",
     "vitest": "^3.0.0"
   }

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

@@ -11,17 +11,17 @@
   "dependencies": {
     "@effect/platform": "^0.96.1",
     "@effect/rpc": "^0.75.1",
-    "@voltro/cli": "0.2.2",
-    "@voltro/database": "0.2.2",
-    "@voltro/env": "0.2.2",
-    "@voltro/plugin-multitenancy": "0.2.2",
-    "@voltro/protocol": "0.2.2",
-    "@voltro/runtime": "0.2.2",
-    "@voltro/workflow": "0.2.2",
+    "@voltro/cli": "0.4.0",
+    "@voltro/database": "0.4.0",
+    "@voltro/env": "0.4.0",
+    "@voltro/plugin-multitenancy": "0.4.0",
+    "@voltro/protocol": "0.4.0",
+    "@voltro/runtime": "0.4.0",
+    "@voltro/workflow": "0.4.0",
     "effect": "^3.21.2"
   },
   "devDependencies": {
-    "@voltro/testing": "0.2.2",
+    "@voltro/testing": "0.4.0",
     "typescript": "^5.7.0",
     "vitest": "^3.0.0"
   }

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

@@ -12,18 +12,18 @@
   "dependencies": {
     "@effect/platform": "^0.96.1",
     "@effect/rpc": "^0.75.1",
-    "@voltro/cli": "0.2.2",
-    "@voltro/database": "0.2.2",
-    "@voltro/env": "0.2.2",
-    "@voltro/plugin-flags": "0.2.2",
-    "@voltro/plugin-multitenancy": "0.2.2",
-    "@voltro/protocol": "0.2.2",
-    "@voltro/runtime": "0.2.2",
-    "@voltro/sql-postgres": "0.2.2",
+    "@voltro/cli": "0.4.0",
+    "@voltro/database": "0.4.0",
+    "@voltro/env": "0.4.0",
+    "@voltro/plugin-flags": "0.4.0",
+    "@voltro/plugin-multitenancy": "0.4.0",
+    "@voltro/protocol": "0.4.0",
+    "@voltro/runtime": "0.4.0",
+    "@voltro/sql-postgres": "0.4.0",
     "effect": "^3.21.2"
   },
   "devDependencies": {
-    "@voltro/testing": "0.2.2",
+    "@voltro/testing": "0.4.0",
     "typescript": "^5.7.0",
     "vitest": "^3.0.0"
   }

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

@@ -12,17 +12,17 @@
   "dependencies": {
     "@effect/platform": "^0.96.1",
     "@effect/rpc": "^0.75.1",
-    "@voltro/cli": "0.2.2",
-    "@voltro/database": "0.2.2",
-    "@voltro/env": "0.2.2",
-    "@voltro/plugin-audit": "0.2.2",
-    "@voltro/plugin-governance": "0.2.2",
-    "@voltro/protocol": "0.2.2",
-    "@voltro/runtime": "0.2.2",
+    "@voltro/cli": "0.4.0",
+    "@voltro/database": "0.4.0",
+    "@voltro/env": "0.4.0",
+    "@voltro/plugin-audit": "0.4.0",
+    "@voltro/plugin-governance": "0.4.0",
+    "@voltro/protocol": "0.4.0",
+    "@voltro/runtime": "0.4.0",
     "effect": "^3.21.2"
   },
   "devDependencies": {
-    "@voltro/testing": "0.2.2",
+    "@voltro/testing": "0.4.0",
     "typescript": "^5.7.0",
     "vitest": "^3.0.0"
   }

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

@@ -11,17 +11,17 @@
   "dependencies": {
     "@effect/platform": "^0.96.1",
     "@effect/rpc": "^0.75.1",
-    "@voltro/cli": "0.2.2",
-    "@voltro/database": "0.2.2",
-    "@voltro/env": "0.2.2",
-    "@voltro/kv": "0.2.2",
-    "@voltro/plugin-multitenancy": "0.2.2",
-    "@voltro/protocol": "0.2.2",
-    "@voltro/runtime": "0.2.2",
+    "@voltro/cli": "0.4.0",
+    "@voltro/database": "0.4.0",
+    "@voltro/env": "0.4.0",
+    "@voltro/kv": "0.4.0",
+    "@voltro/plugin-multitenancy": "0.4.0",
+    "@voltro/protocol": "0.4.0",
+    "@voltro/runtime": "0.4.0",
     "effect": "^3.21.2"
   },
   "devDependencies": {
-    "@voltro/testing": "0.2.2",
+    "@voltro/testing": "0.4.0",
     "typescript": "^5.7.0",
     "vitest": "^3.0.0"
   }

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

@@ -12,17 +12,17 @@
   "dependencies": {
     "@effect/platform": "^0.96.1",
     "@effect/rpc": "^0.75.1",
-    "@voltro/cli": "0.2.2",
-    "@voltro/database": "0.2.2",
-    "@voltro/env": "0.2.2",
-    "@voltro/plugin-moderation": "0.2.2",
-    "@voltro/plugin-multitenancy": "0.2.2",
-    "@voltro/protocol": "0.2.2",
-    "@voltro/runtime": "0.2.2",
+    "@voltro/cli": "0.4.0",
+    "@voltro/database": "0.4.0",
+    "@voltro/env": "0.4.0",
+    "@voltro/plugin-moderation": "0.4.0",
+    "@voltro/plugin-multitenancy": "0.4.0",
+    "@voltro/protocol": "0.4.0",
+    "@voltro/runtime": "0.4.0",
     "effect": "^3.21.2"
   },
   "devDependencies": {
-    "@voltro/testing": "0.2.2",
+    "@voltro/testing": "0.4.0",
     "typescript": "^5.7.0",
     "vitest": "^3.0.0"
   }

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

@@ -12,17 +12,17 @@
   "dependencies": {
     "@effect/platform": "^0.96.1",
     "@effect/rpc": "^0.75.1",
-    "@voltro/cli": "0.2.2",
-    "@voltro/database": "0.2.2",
-    "@voltro/plugin-multitenancy": "0.2.2",
-    "@voltro/plugin-prometheus": "0.2.2",
-    "@voltro/plugin-sentry": "0.2.2",
-    "@voltro/protocol": "0.2.2",
-    "@voltro/runtime": "0.2.2",
+    "@voltro/cli": "0.4.0",
+    "@voltro/database": "0.4.0",
+    "@voltro/plugin-multitenancy": "0.4.0",
+    "@voltro/plugin-prometheus": "0.4.0",
+    "@voltro/plugin-sentry": "0.4.0",
+    "@voltro/protocol": "0.4.0",
+    "@voltro/runtime": "0.4.0",
     "effect": "^3.21.2"
   },
   "devDependencies": {
-    "@voltro/testing": "0.2.2",
+    "@voltro/testing": "0.4.0",
     "typescript": "^5.7.0",
     "vitest": "^3.0.0"
   }

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

@@ -12,17 +12,17 @@
   "dependencies": {
     "@effect/platform": "^0.96.1",
     "@effect/rpc": "^0.75.1",
-    "@voltro/cli": "0.2.2",
-    "@voltro/database": "0.2.2",
-    "@voltro/env": "0.2.2",
-    "@voltro/plugin-multitenancy": "0.2.2",
-    "@voltro/plugin-ratelimit": "0.2.2",
-    "@voltro/protocol": "0.2.2",
-    "@voltro/runtime": "0.2.2",
+    "@voltro/cli": "0.4.0",
+    "@voltro/database": "0.4.0",
+    "@voltro/env": "0.4.0",
+    "@voltro/plugin-multitenancy": "0.4.0",
+    "@voltro/plugin-ratelimit": "0.4.0",
+    "@voltro/protocol": "0.4.0",
+    "@voltro/runtime": "0.4.0",
     "effect": "^3.21.2"
   },
   "devDependencies": {
-    "@voltro/testing": "0.2.2",
+    "@voltro/testing": "0.4.0",
     "typescript": "^5.7.0",
     "vitest": "^3.0.0"
   }