@quickback-dev/cli 0.16.5 → 0.18.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +7 -3
- package/dist/commands/compile.d.ts.map +1 -1
- package/dist/commands/compile.js +12 -48
- package/dist/commands/compile.js.map +1 -1
- package/dist/commands/create.d.ts +20 -0
- package/dist/commands/create.d.ts.map +1 -1
- package/dist/commands/create.js +216 -151
- package/dist/commands/create.js.map +1 -1
- package/dist/commands/login.d.ts +4 -2
- package/dist/commands/login.d.ts.map +1 -1
- package/dist/commands/login.js +25 -17
- package/dist/commands/login.js.map +1 -1
- package/dist/commands/start.d.ts +20 -0
- package/dist/commands/start.d.ts.map +1 -0
- package/dist/commands/start.js +163 -0
- package/dist/commands/start.js.map +1 -0
- package/dist/commands/whoami.d.ts.map +1 -1
- package/dist/commands/whoami.js +5 -4
- package/dist/commands/whoami.js.map +1 -1
- package/dist/docs/content.js +42 -42
- package/dist/docs/content.js.map +1 -1
- package/dist/index.js +27 -10
- package/dist/index.js.map +1 -1
- package/dist/lib/api-client.js +1 -1
- package/dist/lib/api-client.js.map +1 -1
- package/dist/lib/api-client.test.js +15 -0
- package/dist/lib/api-client.test.js.map +1 -1
- package/dist/lib/auth.d.ts +39 -3
- package/dist/lib/auth.d.ts.map +1 -1
- package/dist/lib/auth.js +57 -3
- package/dist/lib/auth.js.map +1 -1
- package/dist/lib/drizzle-meta-routing.test.js +16 -3
- package/dist/lib/drizzle-meta-routing.test.js.map +1 -1
- package/dist/lib/file-loader.d.ts +6 -4
- package/dist/lib/file-loader.d.ts.map +1 -1
- package/dist/lib/file-loader.js +30 -27
- package/dist/lib/file-loader.js.map +1 -1
- package/dist/lib/file-loader.test.js +16 -7
- package/dist/lib/file-loader.test.js.map +1 -1
- package/dist/skill/docs/changelog.md +429 -1100
- package/dist/skill/docs/compiler/cloud-compiler/cli.md +54 -33
- package/dist/skill/docs/compiler/cloud-compiler/index.md +9 -9
- package/dist/skill/docs/compiler/config/providers.md +87 -0
- package/dist/skill/docs/compiler/config/single-tenant.md +5 -11
- package/dist/skill/docs/compiler/definitions/access.md +43 -57
- package/dist/skill/docs/compiler/definitions/feature.md +7 -11
- package/dist/skill/docs/compiler/definitions/firewall.md +2 -4
- package/dist/skill/docs/compiler/definitions/guards.md +16 -18
- package/dist/skill/docs/compiler/definitions/index.md +10 -14
- package/dist/skill/docs/compiler/definitions/masking.md +6 -6
- package/dist/skill/docs/compiler/definitions/read.md +6 -11
- package/dist/skill/docs/compiler/definitions/schema.md +18 -18
- package/dist/skill/docs/compiler/definitions/views.md +3 -5
- package/dist/skill/docs/compiler/getting-started/full-example.md +6 -8
- package/dist/skill/docs/compiler/getting-started/hand-crafted.md +3 -5
- package/dist/skill/docs/compiler/getting-started/index.md +23 -20
- package/dist/skill/docs/compiler/getting-started/patterns.md +19 -31
- package/dist/skill/docs/compiler/getting-started/template-blog.md +6 -10
- package/dist/skill/docs/compiler/getting-started/template-cloudflare.md +49 -56
- package/dist/skill/docs/compiler/getting-started/template-empty.md +3 -5
- package/dist/skill/docs/compiler/getting-started/templates.md +58 -56
- package/dist/skill/docs/compiler/targets/hono-api/using-the-api/batch-operations.md +29 -23
- package/dist/skill/docs/compiler/targets/hono-api/using-the-api/crud.md +12 -14
- package/dist/skill/docs/compiler/targets/hono-api/using-the-api/openapi.md +5 -2
- package/dist/skill/docs/compiler/targets/hono-api/using-the-api/query-params.md +5 -7
- package/dist/skill/docs/compiler/troubleshooting.md +10 -0
- package/dist/skill/docs/index.md +9 -0
- package/dist/skill/docs/stack/auth/security.md +69 -0
- package/dist/skill/docs/stack/cms/actions.md +28 -0
- package/dist/skill/docs/stack/cms/connecting.md +2 -2
- package/dist/skill/docs/stack/cms/index.md +2 -2
- package/dist/skill/docs/stack/cms/record-layouts.md +19 -19
- package/dist/skill/docs/stack/cms/schema-format.md +33 -3
- package/dist/skill/docs/stack/cms/schema-registry.md +22 -2
- package/dist/skill/docs/stack/cms/security.md +10 -12
- package/dist/skill/docs/stack/cms/table-views.md +1 -1
- package/dist/skill/docs/stack/index.md +8 -4
- package/dist/skill/docs/stack/realtime/durable-objects.md +46 -5
- package/dist/skill/docs/stack/realtime/index.md +20 -3
- package/dist/skill/docs/stack/realtime/using-realtime.md +8 -6
- package/dist/skill/docs/stack/vector/embeddings.md +7 -6
- package/package.json +1 -1
- package/src/skill/docs/changelog.md +486 -1097
- package/src/skill/docs/compiler/cloud-compiler/cli.md +54 -33
- package/src/skill/docs/compiler/cloud-compiler/index.md +9 -9
- package/src/skill/docs/compiler/config/domains.md +44 -10
- package/src/skill/docs/compiler/config/output.md +1 -1
- package/src/skill/docs/compiler/config/providers.md +87 -0
- package/src/skill/docs/compiler/config/single-tenant.md +5 -11
- package/src/skill/docs/compiler/definitions/access.md +43 -57
- package/src/skill/docs/compiler/definitions/feature.md +7 -11
- package/src/skill/docs/compiler/definitions/firewall.md +2 -4
- package/src/skill/docs/compiler/definitions/guards.md +16 -18
- package/src/skill/docs/compiler/definitions/index.md +10 -14
- package/src/skill/docs/compiler/definitions/masking.md +6 -6
- package/src/skill/docs/compiler/definitions/read.md +6 -11
- package/src/skill/docs/compiler/definitions/schema.md +18 -18
- package/src/skill/docs/compiler/definitions/views.md +3 -5
- package/src/skill/docs/compiler/getting-started/full-example.md +6 -8
- package/src/skill/docs/compiler/getting-started/hand-crafted.md +3 -5
- package/src/skill/docs/compiler/getting-started/index.md +23 -20
- package/src/skill/docs/compiler/getting-started/patterns.md +19 -31
- package/src/skill/docs/compiler/getting-started/template-blog.md +6 -10
- package/src/skill/docs/compiler/getting-started/template-cloudflare.md +49 -56
- package/src/skill/docs/compiler/getting-started/template-empty.md +3 -5
- package/src/skill/docs/compiler/getting-started/templates.md +58 -56
- package/src/skill/docs/compiler/targets/hono-api/using-the-api/batch-operations.md +29 -23
- package/src/skill/docs/compiler/targets/hono-api/using-the-api/crud.md +12 -14
- package/src/skill/docs/compiler/targets/hono-api/using-the-api/openapi.md +5 -2
- package/src/skill/docs/compiler/targets/hono-api/using-the-api/query-params.md +5 -7
- package/src/skill/docs/compiler/troubleshooting.md +10 -0
- package/src/skill/docs/index.md +9 -0
- package/src/skill/docs/stack/auth/plugins/index.md +74 -0
- package/src/skill/docs/stack/auth/security.md +69 -0
- package/src/skill/docs/stack/cms/actions.md +28 -0
- package/src/skill/docs/stack/cms/connecting.md +2 -2
- package/src/skill/docs/stack/cms/index.md +2 -2
- package/src/skill/docs/stack/cms/record-layouts.md +19 -19
- package/src/skill/docs/stack/cms/schema-format.md +33 -3
- package/src/skill/docs/stack/cms/schema-registry.md +22 -2
- package/src/skill/docs/stack/cms/security.md +10 -12
- package/src/skill/docs/stack/cms/table-views.md +1 -1
- package/src/skill/docs/stack/index.md +8 -4
- package/src/skill/docs/stack/realtime/durable-objects.md +46 -5
- package/src/skill/docs/stack/realtime/index.md +20 -3
- package/src/skill/docs/stack/realtime/using-realtime.md +8 -6
- package/src/skill/docs/stack/vector/embeddings.md +7 -6
|
@@ -4,434 +4,410 @@ Release notes for the Quickback compiler, CLI, and platform.
|
|
|
4
4
|
|
|
5
5
|
---
|
|
6
6
|
|
|
7
|
-
## v0.
|
|
7
|
+
## v0.17.1 — May 14, 2026
|
|
8
8
|
|
|
9
|
-
###
|
|
9
|
+
### `quickback start` — interactive onboarding
|
|
10
10
|
|
|
11
|
-
|
|
11
|
+
```bash
|
|
12
|
+
mkdir my-app && cd my-app
|
|
13
|
+
npx @quickback-dev/cli start
|
|
14
|
+
```
|
|
12
15
|
|
|
13
|
-
|
|
16
|
+
`start` walks new users through template selection, scaffolds the project on disk, and only prompts for an account when it's ready to compile. Cancelling at the login prompt leaves the scaffold intact — sign in and run `quickback compile` whenever you're ready.
|
|
14
17
|
|
|
15
|
-
|
|
18
|
+
The same deferred-auth flow applies to `quickback create`. Scaffolding and (optional) Cloudflare D1 setup run before authentication, so you can preview the project on disk before committing to an account.
|
|
16
19
|
|
|
17
|
-
###
|
|
20
|
+
### Named views on the free tier
|
|
18
21
|
|
|
19
|
-
|
|
22
|
+
The `todos` template now ships a `dashboard` named view, exposing a projected response at `GET /api/v1/todos/views/dashboard`. Named views support per-view access rules and per-view field selection while inheriting the table's firewall and masking — the canonical way to ship list-view payloads that are cheaper to fetch and easier to cache than a full collection read.
|
|
20
23
|
|
|
21
|
-
|
|
24
|
+
### `quickback init` removed
|
|
22
25
|
|
|
23
|
-
|
|
26
|
+
Folded into `start` and `create`. The legacy command name prints a deprecation notice pointing at its replacements.
|
|
24
27
|
|
|
25
|
-
|
|
28
|
+
### Minor
|
|
26
29
|
|
|
27
|
-
|
|
30
|
+
- `quickback whoami` reads the stored tier from your credentials.
|
|
31
|
+
- Pro upsell copy in `quickback login` is shown only when the server returns an explicit free-tier subscription.
|
|
32
|
+
- Bare scaffolds (`cloudflare`, `empty`) report accurately when there are no features to generate migrations for.
|
|
28
33
|
|
|
29
34
|
---
|
|
30
35
|
|
|
31
|
-
## v0.16.
|
|
36
|
+
## v0.16.10 — May 14, 2026
|
|
32
37
|
|
|
33
|
-
###
|
|
38
|
+
### D1-specific safety pass on generated migrations
|
|
34
39
|
|
|
35
|
-
|
|
40
|
+
The `cloudflare-d1` provider now runs a post-generation pass over every Drizzle migration directory (auth, features, webhooks, audit) before the compile finishes. Better Auth cleanup for retired managed tables is stripped from raw `DROP TABLE` statements. Drop-only cleanup migrations are reordered child-first when foreign-key dependencies require it. Every generated D1 migration directory is replayed against SQLite during compile, so a D1-breaking migration fails at compile time rather than at `wrangler d1 migrations apply`.
|
|
36
41
|
|
|
37
|
-
|
|
42
|
+
---
|
|
38
43
|
|
|
39
|
-
|
|
44
|
+
## v0.16.9 — May 13, 2026
|
|
40
45
|
|
|
41
|
-
|
|
46
|
+
### Resource-scoped realtime tickets
|
|
42
47
|
|
|
43
|
-
|
|
48
|
+
`providers.database.config.realtime` accepts an object form for projects whose WebSocket subscribers aren't org members:
|
|
44
49
|
|
|
45
|
-
|
|
50
|
+
```ts
|
|
51
|
+
realtime: {
|
|
52
|
+
wsTicket: {
|
|
53
|
+
role: "attendee",
|
|
54
|
+
requestField: "eventId",
|
|
55
|
+
scopeTable: "events",
|
|
56
|
+
},
|
|
57
|
+
}
|
|
58
|
+
```
|
|
46
59
|
|
|
47
|
-
|
|
60
|
+
The generated `/broadcast/v1/ws-ticket` route authenticates the caller, evaluates the declared relationship role against the request, and mints a short-lived WebSocket ticket scoped to the resolved resource. `realtime: true` continues to enable the org-scoped broadcaster.
|
|
48
61
|
|
|
49
|
-
|
|
62
|
+
### Unified broadcast targeting
|
|
50
63
|
|
|
51
|
-
|
|
64
|
+
The realtime helper and Broadcaster now route by `scopeKey || organizationId || userId`. String targets remain shorthand for `organizationId`; explicit targets can scope a broadcast to a resource or a single user:
|
|
52
65
|
|
|
53
|
-
|
|
66
|
+
```ts
|
|
67
|
+
await realtime.broadcast("event-page-updated", payload, { scopeKey: "events:evt_123" });
|
|
68
|
+
await realtime.broadcast("dm", payload, { userId: recipientId });
|
|
69
|
+
```
|
|
54
70
|
|
|
55
|
-
|
|
71
|
+
WebSocket tickets are Quickback-minted (signed with `BETTER_AUTH_SECRET`), not Better Auth tokens — Better Auth remains the front-door auth check; Quickback signs the upgrade ticket after authorization succeeds.
|
|
56
72
|
|
|
57
|
-
|
|
73
|
+
---
|
|
58
74
|
|
|
59
|
-
|
|
75
|
+
## v0.16.8 — May 13, 2026
|
|
60
76
|
|
|
61
|
-
|
|
77
|
+
### One auth transport per request
|
|
62
78
|
|
|
63
|
-
|
|
79
|
+
Generated middleware treats `Cookie`, `Authorization: Bearer`, and `x-api-key` as distinct auth methods and rejects mixed requests with `400 AUTH_METHOD_CONFLICT`. Query-string API keys (`?api_key=` / `?key=`) are no longer accepted. Machine-to-machine auth is explicit; precedence rules between transports are gone.
|
|
64
80
|
|
|
65
|
-
|
|
81
|
+
### Cookie-backed CSRF gate
|
|
66
82
|
|
|
67
|
-
|
|
83
|
+
Generated apps now block cross-site `POST` / `PUT` / `PATCH` / `DELETE` requests from cookie-relying callers. The middleware skips explicit `Authorization` clients, requires a trusted `Origin` or `Referer`, and blocks `Sec-Fetch-Site: cross-site`. This matters most for cross-subdomain session setups where `SameSite=None` is intentional.
|
|
68
84
|
|
|
69
|
-
|
|
85
|
+
### First-class Wrangler observability
|
|
70
86
|
|
|
71
|
-
|
|
87
|
+
`providers.runtime.config.observability` now supports nested `logs` / `traces` blocks for `headSamplingRate`, `destinations`, `persist`, and `logs.invocationLogs`, emitting matching `[observability]`, `[observability.logs]`, and `[observability.traces]` TOML.
|
|
72
88
|
|
|
73
|
-
|
|
89
|
+
---
|
|
74
90
|
|
|
75
|
-
|
|
91
|
+
## v0.16.7 — May 12, 2026
|
|
76
92
|
|
|
77
|
-
|
|
93
|
+
### Bearer wins over cookie
|
|
78
94
|
|
|
79
|
-
|
|
95
|
+
A request carrying both `Authorization` and a session `Cookie` resolves entirely from the bearer; the cookie is dropped before `getSession()` runs. All three Bearer flavors (API key, JWT, session-token) now behave consistently — no more silent cookie precedence on session-token bearers.
|
|
80
96
|
|
|
81
|
-
###
|
|
97
|
+
### Bearer plugin defaults to `requireSignature: true`
|
|
82
98
|
|
|
83
|
-
|
|
99
|
+
Better Auth's `bearer` plugin defaults to unsigned tokens; Quickback now emits `bearer({ requireSignature: true })`. Tokens emitted in the CORS-exposed `set-auth-token` header are server-signed with `BETTER_AUTH_SECRET` and verified on every request. Projects that genuinely need unsigned bearers can override via `providers.auth.config.plugins.bearer`.
|
|
84
100
|
|
|
85
|
-
|
|
101
|
+
See [Authentication Security → Bearer Tokens and Cookie Precedence](/stack/auth/security#bearer-tokens-and-cookie-precedence).
|
|
86
102
|
|
|
87
103
|
---
|
|
88
104
|
|
|
89
|
-
## v0.16.
|
|
90
|
-
|
|
91
|
-
### Agent Auth Protocol — first-class agent identity for AI callers
|
|
105
|
+
## v0.16.5 — May 12, 2026
|
|
92
106
|
|
|
93
|
-
|
|
107
|
+
### Flat write DSL
|
|
94
108
|
|
|
95
|
-
|
|
109
|
+
Resource write operations are now declared at the table level alongside `read`, replacing the nested `crud` block:
|
|
96
110
|
|
|
97
|
-
|
|
111
|
+
```ts
|
|
112
|
+
defineTable(customers, {
|
|
113
|
+
read: { ... },
|
|
114
|
+
create: { access: { roles: ["admin"] } },
|
|
115
|
+
update: { access: { roles: ["admin"] } },
|
|
116
|
+
delete: { access: { roles: ["admin"] }, mode: "soft" },
|
|
117
|
+
upsert: { access: { roles: ["admin"] } },
|
|
118
|
+
guards: { ... },
|
|
119
|
+
});
|
|
120
|
+
```
|
|
98
121
|
|
|
99
|
-
|
|
122
|
+
`crud` and top-level `put` still compile as deprecated compatibility aliases. Mixed usage on the same resource is rejected. `schema-registry.json` emits both shapes during the transition.
|
|
100
123
|
|
|
101
|
-
###
|
|
124
|
+
### CMS placement for multi-table feature actions
|
|
102
125
|
|
|
103
|
-
|
|
126
|
+
Standalone actions on multi-table features have an explicit placement model:
|
|
104
127
|
|
|
105
|
-
-
|
|
106
|
-
-
|
|
107
|
-
-
|
|
128
|
+
- `cms.placement: "feature"` shows the action on every table toolbar in the feature
|
|
129
|
+
- `cms.placement: "tables"` with `cms.tables` scopes it to specific tables
|
|
130
|
+
- `cms.hidden: true` keeps it API-only
|
|
108
131
|
|
|
109
|
-
|
|
132
|
+
Feature-root standalone actions are emitted under a new `featureActions` bucket in `schema-registry.json`. Ambiguous multi-table standalone actions without placement compile with a warning.
|
|
110
133
|
|
|
111
|
-
###
|
|
134
|
+
### `openapi.types` accepts a string array
|
|
112
135
|
|
|
113
|
-
|
|
136
|
+
One compile can write the generated types file to multiple locations, keeping colocated SPA clients in sync:
|
|
114
137
|
|
|
115
|
-
|
|
138
|
+
```ts
|
|
139
|
+
openapi: { types: ['api-types.gen.ts', 'apps/web/src/lib/api-types.gen.ts'] }
|
|
140
|
+
```
|
|
116
141
|
|
|
117
|
-
###
|
|
142
|
+
### Stable artifact ordering
|
|
118
143
|
|
|
119
|
-
|
|
144
|
+
Generated route files and `schema-registry.json` are emitted in a stable order across runs. Identical logical input produces identical artifacts.
|
|
120
145
|
|
|
121
|
-
|
|
146
|
+
---
|
|
122
147
|
|
|
123
|
-
|
|
148
|
+
## v0.16.4 — May 12, 2026
|
|
124
149
|
|
|
125
|
-
|
|
150
|
+
### Drizzle snapshot integrity
|
|
126
151
|
|
|
127
|
-
|
|
152
|
+
Drizzle metadata files (`<n>_snapshot.json`) are no longer stamped with a Quickback warning key. The warning is now journal-only. Projects whose snapshots were corrupted by an earlier release self-heal on the next compile — the stripped header is removed during staging and the rewritten snapshot is clean.
|
|
128
153
|
|
|
129
|
-
|
|
154
|
+
### `account.auth.*` drives the server, not just the SPA
|
|
130
155
|
|
|
131
|
-
|
|
156
|
+
The Account UI's auth flags (`signup`, `password`, `passkey`, `emailOTP`, `emailVerification`) now configure the Better Auth server alongside the SPA bundle. A normalizer maps them into the server config:
|
|
132
157
|
|
|
133
|
-
|
|
158
|
+
- `signup → emailAndPassword.disableSignUp` (inverted)
|
|
159
|
+
- `password → emailAndPassword.enabled`
|
|
160
|
+
- `emailVerification → emailAndPassword.requireEmailVerification`
|
|
161
|
+
- `passkey` / `emailOTP` → plugin additions
|
|
134
162
|
|
|
135
|
-
|
|
163
|
+
The SPA's `VITE_ENABLE_*` flags are derived from the same canonicalized server config, so the bundle and the server cannot drift. Two new flags ride along: `VITE_ENABLE_API_KEYS` and `VITE_ENABLE_MAGIC_LINK`.
|
|
136
164
|
|
|
137
|
-
|
|
165
|
+
**Breaking** for projects that implicitly relied on the SPA-only behaviour: `account.auth.signup: false` now actually disables `POST /auth/v1/sign-up/email` on the server. Set `providers.auth.config.emailAndPassword.disableSignUp: false` explicitly to keep server signup open while hiding the SPA screen.
|
|
138
166
|
|
|
139
167
|
---
|
|
140
168
|
|
|
141
|
-
## v0.
|
|
142
|
-
|
|
143
|
-
### Sysadmin tier — cross-tenant DB-admin role for the CMS
|
|
169
|
+
## v0.16.3 — May 9, 2026
|
|
144
170
|
|
|
145
|
-
|
|
171
|
+
### Standalone action mount order
|
|
146
172
|
|
|
147
|
-
|
|
173
|
+
Feature-level standalone action routers now register before sibling CRUD routers when both mount at the exact same prefix. A literal path like `GET /api/v1/records/today-bundle` resolves to the standalone handler instead of falling through to `GET /:id` and treating `"today-bundle"` as a record ID.
|
|
148
174
|
|
|
149
|
-
|
|
175
|
+
---
|
|
150
176
|
|
|
151
|
-
|
|
177
|
+
## v0.16.1 — May 9, 2026
|
|
152
178
|
|
|
153
|
-
###
|
|
179
|
+
### Cloudflare ASSETS canonicalization
|
|
154
180
|
|
|
155
|
-
|
|
181
|
+
Worker SPA fallbacks now request `/<dir>/` instead of `/<dir>/index.html`. Cloudflare's static-assets binding rewrites `/index.html` requests as 307 redirects to the trailing-slash path under the default `html_handling=auto-trailing-slash`, which previously caused redirect loops in SPA fallback handlers. Affects CMS, Account, admin, and the multi-domain catchall.
|
|
156
182
|
|
|
157
|
-
|
|
183
|
+
### `account.customLogin`
|
|
158
184
|
|
|
159
|
-
|
|
185
|
+
Set `account: { customLogin: true }` to drop a project-branded sign-in page in front of the bundled SPA. Place the page at `quickback/public/account/login/index.html` (as a directory) and the existing public passthrough serves it. The route registers before the `/account/*` SPA catch-all so the static handler wins; everything else under `/account/` continues to route through the bundled SPA.
|
|
160
186
|
|
|
161
|
-
|
|
187
|
+
### Project-level realtime defaults
|
|
162
188
|
|
|
163
|
-
|
|
189
|
+
`providers.database.config.realtime: true` now treats every resource as realtime-enabled by default. Per-resource `realtime: { enabled: false }` still wins.
|
|
164
190
|
|
|
165
|
-
|
|
191
|
+
### Compile-time validators
|
|
166
192
|
|
|
167
|
-
|
|
193
|
+
Two new compile-time errors over silent runtime failures:
|
|
168
194
|
|
|
169
|
-
|
|
195
|
+
- `AUTHENTICATED` + org-scoped firewall is rejected. The combination silently returned empty lists to sign-in-only callers who lacked an active org; the validator names three valid resolutions (drop the org scope, use `USER`, or split the route).
|
|
196
|
+
- `createRealtime` imports without `realtime: true` enabled in the config are rejected at compile.
|
|
170
197
|
|
|
171
|
-
|
|
198
|
+
### Drizzle metadata hardening
|
|
172
199
|
|
|
173
|
-
|
|
200
|
+
Drizzle journal files carry a "do not edit" header. The compiler warns when the journal entry count exceeds the snapshot file count (typically the trace of a hand-deleted snapshot).
|
|
174
201
|
|
|
175
|
-
|
|
176
|
-
- **Stale-cleaned.** `src/` is wiped and rewritten each compile, so files removed from `quickback/public/` disappear from `src/apps/` automatically on the next run.
|
|
177
|
-
- **Hidden entries skipped.** `.DS_Store`, `.git/`, dotfiles — none of these were intentional drops; including them would break worker asset bindings.
|
|
178
|
-
- **Collisions fail loud.** A file in `quickback/public/` whose path would shadow a compiler-emitted manifest entry — e.g. `quickback/public/cms/index.html` against the SPA shell — fails the compile with the offending paths listed, rather than silently overwriting and producing a confused-looking SPA build. Move or rename the offending file.
|
|
202
|
+
### Minor
|
|
179
203
|
|
|
180
|
-
|
|
204
|
+
- `SYSADMIN` is now recognised by the standalone-action org gate's pseudo-role matcher.
|
|
205
|
+
- Apex `/` and `/account/login` get fallback redirects to `auth.loginUrl` when neither bundled SPA is enabled.
|
|
206
|
+
- Record-based action URLs are kebab-case to match the OpenAPI spec (e.g. `/api/v1/widgets/:id/send-invite`).
|
|
181
207
|
|
|
182
208
|
---
|
|
183
209
|
|
|
184
|
-
## v0.
|
|
210
|
+
## v0.16.0 — May 9, 2026
|
|
185
211
|
|
|
186
|
-
###
|
|
212
|
+
### Agent Auth Protocol
|
|
187
213
|
|
|
188
|
-
|
|
214
|
+
Quickback ships a server implementation of the [Agent Auth Protocol](https://agentauthprotocol.com) via `@better-auth/agent-auth`. Enable with `auth.plugins.agentAuth: true` and the compiler emits the full agent-auth surface: discovery at `/.well-known/agent-configuration`, capability projection from the project's OpenAPI spec, a device-authorization approval page in the Account SPA at `/agents/approve`, and the four agent-auth tables added to the auth schema automatically.
|
|
189
215
|
|
|
190
|
-
**
|
|
216
|
+
**OpenAPI capability projection runs by default.** Every operation with an `operationId` becomes an agent capability. Default `approvalStrength` map: `GET → "session"`, `POST/PUT/PATCH/DELETE → "webauthn"`. The proxy `onExecute` makes a self-fetch with a Better Auth JWT minted for the agent session, so the inner request hits the existing JWT fast-path and runs the full firewall + access + masking pipeline. Opt out of OpenAPI projection with `agentAuth: { fromOpenAPI: false }` and wire `capabilities` + `onExecute` by hand.
|
|
191
217
|
|
|
192
|
-
|
|
218
|
+
### Bearer-only on `/mcp` and the agent-auth surface
|
|
193
219
|
|
|
194
|
-
|
|
220
|
+
`/mcp` forwards only `Authorization: Bearer …` into the inner request. Cookie and `x-api-key` forwarding are removed. Three Bearer flavors land on the same header — Better Auth session token (via the `bearer` plugin), OAuth access token (via OAuth Provider), and agent JWT (via `@better-auth/agent-auth`).
|
|
195
221
|
|
|
196
|
-
|
|
222
|
+
### Auth DSL gains first-class plugin entries
|
|
197
223
|
|
|
198
|
-
|
|
224
|
+
`bearer`, `oauthProvider`, and `agentAuth` are now typed entries in both the array-form union and the `BetterAuthPlugins` interface, with their own options shapes (`OAuthProviderOptions`, `AgentAuthOptions`). Existing `as any` casts can come out.
|
|
199
225
|
|
|
200
|
-
|
|
226
|
+
Auto-enable rule: turning on `agentAuth` force-adds `bearer` + `oauthProvider`. No useful agent-auth deployment ships without those two.
|
|
201
227
|
|
|
202
|
-
|
|
228
|
+
### `queue-consumer.ts` gating
|
|
203
229
|
|
|
204
|
-
|
|
230
|
+
The queue consumer is emitted when any of the following are true: embeddings are configured, queue handlers exist under `services/queues/*`, or `additionalQueues` is declared. Previously the third case left projects with a wrangler binding pointing at a missing handler.
|
|
205
231
|
|
|
206
|
-
|
|
207
|
-
2. **Two sign-in surfaces are harder to support.** The account SPA's `/welcome` and `/email-otp` routes only render the OTP form; the magic-link arm bypasses that UI entirely. One canonical entry point (enter the code) keeps the account flow legible.
|
|
232
|
+
---
|
|
208
233
|
|
|
209
|
-
|
|
234
|
+
## v0.15.0 — May 7, 2026
|
|
210
235
|
|
|
211
|
-
|
|
236
|
+
### Sysadmin tier for the CMS
|
|
212
237
|
|
|
213
|
-
|
|
238
|
+
A new opt-in `cms: { sysadmin: true }` flag turns the CMS into a cross-tenant DB-admin tool gated by `user.role === 'sysadmin'`. Distinct from the Better Auth `'admin'` plugin role, so user-management powers and DB-admin powers stay decoupled. Off by default.
|
|
214
239
|
|
|
215
|
-
|
|
240
|
+
When enabled, the compiler emits a `SYSADMIN` pseudo-role (a fifth marker alongside `PUBLIC` / `AUTHENTICATED` / `USER` / `ADMIN`), a firewall escape hatch that drops tenant scopes for sysadmins while preserving soft-delete, a true cross-tenant `/admin/v1/sysadmin/organizations` endpoint, and a relaxed cross-tenant guard for list routes.
|
|
216
241
|
|
|
217
|
-
|
|
242
|
+
The CMS SPA gains a two-mode design: org admins keep the existing membership-based switcher, sysadmins get an "All organizations" selector that pins tenants via `?organizationId=` on every API call.
|
|
218
243
|
|
|
219
|
-
|
|
244
|
+
### Durable Object `[[migrations]]` order is preserved
|
|
220
245
|
|
|
221
|
-
|
|
246
|
+
Cloudflare's migration list is append-only. The compiler now reads your existing `wrangler.toml` (when present) and emits auto-generated DO `[[migrations]]` blocks in two phases: deployed entries first (preserving order), net-new entries appended last. Reordering DOs in the config array no longer reshuffles deployed migrations.
|
|
222
247
|
|
|
223
|
-
|
|
248
|
+
### `quickback/public/` — static-asset passthrough
|
|
224
249
|
|
|
225
|
-
|
|
250
|
+
Anything dropped under `quickback/public/` is copied verbatim into `src/apps/` on every compile and served by the wrangler `[assets]` binding. Use for favicons, `robots.txt`, OG images, `.well-known/` files, marketing PDFs — anything that needs to ride past the compiler as bytes.
|
|
226
251
|
|
|
227
|
-
|
|
252
|
+
- Optional. Missing folder is a no-op.
|
|
253
|
+
- Stale-cleaned. Files removed from `quickback/public/` disappear on the next compile.
|
|
254
|
+
- Hidden entries (`.DS_Store`, dotfiles) are skipped.
|
|
255
|
+
- Collisions with compiler-emitted manifest paths fail the compile loudly.
|
|
228
256
|
|
|
229
|
-
|
|
257
|
+
### Minor
|
|
230
258
|
|
|
231
|
-
|
|
259
|
+
- Standalone-action wrapper skips the org gate when the access tree references any pseudo-role.
|
|
260
|
+
- Queue handler emit no longer drops the `queue` export when there are no embeddings.
|
|
232
261
|
|
|
233
|
-
|
|
262
|
+
---
|
|
234
263
|
|
|
235
|
-
|
|
264
|
+
## v0.14.7 — May 7, 2026
|
|
236
265
|
|
|
237
|
-
|
|
266
|
+
### Codegen fixes for projects with non-`id` primary keys and DO-only features
|
|
238
267
|
|
|
239
|
-
|
|
240
|
-
curl -fs -X POST https://attend.vip/mcp \
|
|
241
|
-
-H "Authorization: Bearer $TOKEN" -H 'Content-Type: application/json' \
|
|
242
|
-
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"listEvents","arguments":{}}}' \
|
|
243
|
-
| jq '.result.content[0].text | fromjson | .data | length' # > 0
|
|
244
|
-
```
|
|
268
|
+
Four surgical fixes to the generated output:
|
|
245
269
|
|
|
246
|
-
|
|
270
|
+
- Duplicate table imports in relationship-role routes are deduplicated.
|
|
271
|
+
- `db` references in single-record and bulk action handlers now resolve correctly during pre-fetch.
|
|
272
|
+
- PartyServer auth gates pass the in-scope `db` handle into firewall calls.
|
|
273
|
+
- Durable-object-only features keep their `lib/` files in the output.
|
|
247
274
|
|
|
248
|
-
|
|
275
|
+
### `emailOtp` + AWS SES is OTP-only
|
|
249
276
|
|
|
250
|
-
|
|
277
|
+
`auth.emailOtp` with the AWS SES email provider no longer auto-wires the magic-link companion. Mail-client URL prefetching can burn the one-time code before the human sees it; the Account SPA's `/email-otp` route is the single canonical entry point. Projects that explicitly want the magic-link arm can wire `sendVerificationOTP` directly.
|
|
278
|
+
|
|
279
|
+
---
|
|
251
280
|
|
|
252
|
-
|
|
281
|
+
## v0.14.6 — May 7, 2026
|
|
253
282
|
|
|
254
|
-
|
|
283
|
+
### MCP transport correctness
|
|
255
284
|
|
|
256
|
-
|
|
285
|
+
Four fixes to the MCP-over-HTTP path:
|
|
257
286
|
|
|
258
|
-
|
|
287
|
+
- `tools/call` URLs are no longer double-prefixed for action tools.
|
|
288
|
+
- Auth middleware accepts API keys via `Authorization: Bearer` in addition to `x-api-key` and query parameters — the channel MCP clients use exclusively.
|
|
289
|
+
- `auth.roleHierarchy` is expanded for runtime role checks across api-key, JWT, and session auth paths. A higher role inherits the privileges of every lower role.
|
|
290
|
+
- Team-scoped firewall predicates degrade gracefully when no team is active (org scoping continues to apply; team scoping is optional).
|
|
259
291
|
|
|
260
292
|
---
|
|
261
293
|
|
|
262
|
-
## v0.14.
|
|
294
|
+
## v0.14.5 — May 7, 2026
|
|
263
295
|
|
|
264
|
-
###
|
|
296
|
+
### MCP environment threading
|
|
265
297
|
|
|
266
|
-
The
|
|
298
|
+
The generated MCP server's `tools/call` dispatch threads `env` and `executionCtx` into the inner request, so action tools that touch Cloudflare bindings (D1, KV, R2, Queues) no longer crash with `undefined` env access.
|
|
267
299
|
|
|
268
|
-
|
|
300
|
+
---
|
|
269
301
|
|
|
270
|
-
|
|
271
|
-
2. **`buildFirewallConditions` now takes `(ctx, db)`** and the wrapper template (`WITH_FIREWALL_HELPER`) pulls `const db = c.get('db' as never) as any;` from the Hono context before invoking it. Every CRUD/action call site (single-record + batch + record-based-action) was updated to pass `db` through.
|
|
302
|
+
## v0.14.4 — May 7, 2026
|
|
272
303
|
|
|
273
|
-
|
|
304
|
+
### `via:` firewall predicates pull required imports
|
|
274
305
|
|
|
275
|
-
|
|
306
|
+
The relationship-role generator emits `inArray` and `sql` imports when the firewall has any `via:` predicate, and `buildFirewallConditions` accepts `(ctx, db)` so the relationship subquery has a Drizzle client to evaluate against. Every CRUD and action call site passes `db` through automatically.
|
|
276
307
|
|
|
277
308
|
---
|
|
278
309
|
|
|
279
310
|
## v0.14.3 — May 7, 2026
|
|
280
311
|
|
|
281
|
-
### Relationship-role
|
|
282
|
-
|
|
283
|
-
Pre-fix, the v0.14.0 relationship-role generator emitted imports like `import { eventGuests, buildFirewallConditions as buildEventGuestsFirewallConditions } from '../event-guests/event-guests.resource'` on every consuming resource — but the relationship-table's own `.resource.ts` file imported `event_guests` from `./schema` for its own use without re-exporting it. So the consuming file got `undefined` at runtime, every relationship subquery failed with `Cannot read properties of undefined`, and the whole authz layer was unreachable on real projects.
|
|
284
|
-
|
|
285
|
-
Found by AttendVIP within minutes of recompiling against v0.14.2: the moment they hit any endpoint guarded by `firewall: [{ field, via }]` or `crud.<op>.access roles: ['guest']`, the request errored before the firewall query ran.
|
|
312
|
+
### Relationship-role table re-exports
|
|
286
313
|
|
|
287
|
-
|
|
288
|
-
|
|
289
|
-
```ts
|
|
290
|
-
// generated <table>.resource.ts (after fix)
|
|
291
|
-
import { event_guests } from './schema';
|
|
292
|
-
export { event_guests }; // ← was missing
|
|
293
|
-
```
|
|
294
|
-
|
|
295
|
-
Regression test added (`authz-end-to-end.test.ts`) that asserts every `.resource` file re-exports its Drizzle binding, so this can't drift again. No user code changes required — recompile and the cross-feature relationship subqueries resolve correctly.
|
|
314
|
+
Generated `<table>.resource.ts` files now re-export their Drizzle table binding. Cross-feature relationship subqueries that import the binding from the resource file (rather than the schema) resolve correctly.
|
|
296
315
|
|
|
297
316
|
---
|
|
298
317
|
|
|
299
318
|
## v0.14.2 — May 7, 2026
|
|
300
319
|
|
|
301
|
-
###
|
|
302
|
-
|
|
303
|
-
Cloudflare requires the `[[migrations]]` list in `wrangler.toml` to be **append-only**: once a tag has been deployed, removing it on a subsequent compile causes the next deploy to fail with `Cannot apply <new|deleted|renamed|transferred>-class migration to class <X>` — CF replays the full migrations log on every push and notices the tag is gone.
|
|
320
|
+
### Historical DO `[[migrations]]` are preserved
|
|
304
321
|
|
|
305
|
-
|
|
306
|
-
|
|
307
|
-
The fix adds a new config slot — `bindings.durableObjectMigrations` — for historical entries that survive recompiles. Declared entries are emitted FIRST in the generated `wrangler.toml`'s migrations list (preserving chronological order), then the auto-generated current-class creation entries follow, deduplicated by tag so an explicit user entry wins over the auto-emit.
|
|
322
|
+
A new `bindings.durableObjectMigrations` config slot carries forward `deleted_classes`, `renamed_classes`, and `transferred_classes` lifecycle entries across recompiles. Cloudflare's migration list is append-only; entries declared here are emitted first in `wrangler.toml`, then auto-generated current-class entries follow:
|
|
308
323
|
|
|
309
324
|
```ts
|
|
310
|
-
// quickback.config.ts
|
|
311
325
|
bindings: {
|
|
312
|
-
durableObjects: [
|
|
313
|
-
{ name: 'NOTEPAD', className: 'Notepad', from: 'lib/Notepad' },
|
|
314
|
-
],
|
|
326
|
+
durableObjects: [{ name: 'NOTEPAD', className: 'Notepad', from: 'lib/Notepad' }],
|
|
315
327
|
durableObjectMigrations: [
|
|
316
|
-
|
|
317
|
-
{
|
|
318
|
-
tag: 'qb-do-deleted-legacy-notes-2026-05-05',
|
|
319
|
-
deletedClasses: ['LegacyNotes'],
|
|
320
|
-
},
|
|
328
|
+
{ tag: 'qb-do-deleted-legacy-notes-2026-05-05', deletedClasses: ['LegacyNotes'] },
|
|
321
329
|
],
|
|
322
330
|
}
|
|
323
331
|
```
|
|
324
332
|
|
|
325
|
-
All four lifecycle shapes are supported
|
|
326
|
-
|
|
327
|
-
This is a config-side fix, not a wrangler.toml-merging one — Quickback doesn't read your existing `wrangler.toml`. The discipline is the same as for any append-only log: declare lifecycle events as you make them. Auto-detection of removed classes from the schema diff is on the roadmap; for now the compiler trusts your declaration.
|
|
328
|
-
|
|
329
|
-
7 new tests covering deletion, rename, transfer, multi-entry ordering, override-via-same-tag, no-history bit-identical output, and the historical-only-no-current-DOs edge case.
|
|
333
|
+
All four lifecycle shapes are supported. User-declared entries can override auto-emit by reusing the same tag.
|
|
330
334
|
|
|
331
335
|
---
|
|
332
336
|
|
|
333
337
|
## v0.14.1 — May 7, 2026
|
|
334
338
|
|
|
335
|
-
### Bulk action variants
|
|
339
|
+
### Bulk action variants in `openapi.json`
|
|
336
340
|
|
|
337
|
-
Record-based actions with `bulkVariant: true`
|
|
341
|
+
Record-based actions with `bulkVariant: true` are now emitted as sibling operations in the OpenAPI spec, with the documented `{ ids, input, failFast? }` request shape, 200/207/400 responses, and a separate `<Resource><Action>Bulk` `operationId` so typed-client codegen distinguishes single from bulk.
|
|
338
342
|
|
|
339
|
-
|
|
343
|
+
### Cross-tenant "my events" patterns
|
|
340
344
|
|
|
341
|
-
|
|
342
|
-
|
|
343
|
-
### Cross-tenant "my events" pattern documented with a worked example
|
|
344
|
-
|
|
345
|
-
The v0.14.0 docs noted that relationship-roles do **not** solve cross-tenant aggregation ("a guest's view of events across all tenants they were invited to") and pointed at function-form access as the workaround, but didn't show what that looked like in practice. The access docs now carry a full standalone-action example for `GET /my-events` — the canonical attendee-dashboard pattern — including the two security guardrails (always filter by `ctx.userId`; the action takes responsibility for soft-delete and other invariants the firewall would otherwise apply). Standalone actions are already mandatorily audit-logged in the runtime, so the cross-tenant traversal is recorded automatically.
|
|
346
|
-
|
|
347
|
-
See [Access → Cross-tenant "my events" dashboards](/compiler/definitions/access#cross-tenant-my-events-dashboards-are-not-this).
|
|
345
|
+
The access docs now include a worked example for the cross-tenant aggregation pattern (e.g. `GET /my-events` returning resources across all tenants a caller is invited to). See [Access → Cross-tenant dashboards](/compiler/definitions/access#cross-tenant-my-events-dashboards-are-not-this).
|
|
348
346
|
|
|
349
347
|
---
|
|
350
348
|
|
|
351
349
|
## v0.14.0 — May 7, 2026
|
|
352
350
|
|
|
353
|
-
### Relationship-based authorization
|
|
351
|
+
### Relationship-based authorization
|
|
354
352
|
|
|
355
|
-
|
|
356
|
-
|
|
357
|
-
Declare the relationship once in `quickback.config.ts`, then reference it from `firewall:` or `access.roles:`:
|
|
353
|
+
Roles can now be bound to a domain-table membership ("user is a confirmed guest of this event") rather than an org membership or a pseudo-role. Declare the relationship once and reference it from `firewall:` or `access.roles:`:
|
|
358
354
|
|
|
359
355
|
```ts
|
|
360
|
-
// quickback.config.ts
|
|
361
356
|
authz: {
|
|
362
357
|
relationships: {
|
|
363
358
|
guestOf: {
|
|
364
|
-
from: 'event_guests',
|
|
365
|
-
subject: { column: 'userId', equals: 'ctx.userId' },
|
|
366
|
-
resource: { column: 'eventId' },
|
|
367
|
-
where: { status: 'confirmed' },
|
|
359
|
+
from: 'event_guests',
|
|
360
|
+
subject: { column: 'userId', equals: 'ctx.userId' },
|
|
361
|
+
resource: { column: 'eventId' },
|
|
362
|
+
where: { status: 'confirmed' },
|
|
368
363
|
},
|
|
369
364
|
},
|
|
370
365
|
roles: {
|
|
371
366
|
guest: { via: 'guestOf' },
|
|
372
|
-
eventStaff: {
|
|
373
|
-
or: [{ via: 'guestOf' }, { roles: ['admin', 'owner'] }],
|
|
374
|
-
},
|
|
367
|
+
eventStaff: { or: [{ via: 'guestOf' }, { roles: ['admin', 'owner'] }] },
|
|
375
368
|
},
|
|
376
369
|
}
|
|
377
370
|
|
|
378
371
|
// features/sessions/sessions.ts
|
|
379
372
|
firewall: [
|
|
380
373
|
{ field: 'organizationId', equals: 'ctx.activeOrgId' },
|
|
381
|
-
{ field: 'eventId', via: 'guestOf' },
|
|
374
|
+
{ field: 'eventId', via: 'guestOf' },
|
|
382
375
|
],
|
|
383
|
-
read: { access: { roles: ['admin', 'member', 'guest'] } },
|
|
384
|
-
|
|
385
|
-
|
|
386
|
-
update: { access: { roles: ['admin'] } },
|
|
387
|
-
}
|
|
376
|
+
read: { access: { roles: ['admin', 'member', 'guest'] } },
|
|
377
|
+
create: { access: { roles: ['admin', 'guest'] } },
|
|
378
|
+
update: { access: { roles: ['admin'] } },
|
|
388
379
|
```
|
|
389
380
|
|
|
390
|
-
The compiler emits an inline Drizzle subquery against the relationship table and AND-composes it as the outermost firewall clause. The relationship table's own
|
|
391
|
-
|
|
392
|
-
What works in v0.14.0:
|
|
393
|
-
|
|
394
|
-
| Surface | Status |
|
|
395
|
-
|---|---|
|
|
396
|
-
| `firewall: [{ field, via }]` row-level scoping | Full |
|
|
397
|
-
| `crud.<op>.access` `roles: ['guest']` (inline emission) | Full |
|
|
398
|
-
| `read.access` and `read.views.*.access` | Full |
|
|
399
|
-
| `masking.<f>.show` `roles: ['guest']` | Compile-refused (workaround pointer) |
|
|
400
|
-
| `actions.<n>.access` `roles: ['guest']` | Compile-refused (workaround pointer) |
|
|
401
|
-
|
|
402
|
-
The runtime evaluator fails closed on relationship arms regardless of which surface you hit, so silent grants are impossible everywhere. The two refused surfaces have clear compile-time errors pointing to the working pattern (gate the row at the firewall layer with `via:`, gate the role at the access layer with BA roles).
|
|
381
|
+
The compiler emits an inline Drizzle subquery against the relationship table and AND-composes it as the outermost firewall clause. The relationship table's own firewall (tenant scope, soft-delete) is honored inside the subquery; cross-tenant grants are impossible because the resource's tenant filter sits outermost.
|
|
403
382
|
|
|
404
|
-
|
|
383
|
+
Supported surfaces: row-level scoping via `firewall: [{ field, via }]`, role gates on writes and reads, view access. Masking and action access reject relationship-roles at compile time with pointers to the working pattern (gate the row at the firewall layer, gate the role at the access layer).
|
|
405
384
|
|
|
406
|
-
Cross-tenant
|
|
385
|
+
Cross-tenant aggregation dashboards aren't solved by relationship-roles — the tenant firewall remains the outermost AND. For that pattern, use a user-scoped firewall or function-form access on a dedicated route.
|
|
407
386
|
|
|
408
|
-
|
|
387
|
+
See [Firewall → Relationship-based scoping](/compiler/definitions/firewall#relationship-based-scoping-via) and [Access → Relationship-based authorization](/compiler/definitions/access#relationship-based-authorization).
|
|
409
388
|
|
|
410
|
-
### Bulk variants
|
|
389
|
+
### Bulk variants on record-based actions
|
|
411
390
|
|
|
412
|
-
|
|
391
|
+
`defineAction({ bulkVariant: true })` emits `POST /:resource/batch/{action}` alongside the per-record route. The bulk handler loops the same access + transition + execute pipeline over a `{ ids, input, failFast? }` body:
|
|
413
392
|
|
|
414
393
|
```ts
|
|
415
|
-
// features/applications/actions/advance.ts
|
|
416
394
|
export default defineAction({
|
|
417
395
|
description: "Move an application forward in the pipeline.",
|
|
418
396
|
input: z.object({ nextStatus: z.enum(["screening", "interview", "offer"]) }),
|
|
419
397
|
access: { roles: ["owner", "admin"] },
|
|
420
|
-
bulkVariant: true,
|
|
398
|
+
bulkVariant: true,
|
|
421
399
|
transition: { field: "status", via: "nextStatus", fromTo: { /* ... */ } },
|
|
422
400
|
async execute({ db, record, input, whereTransition }) {
|
|
423
|
-
// exact same body
|
|
401
|
+
// exact same body — runs once per id
|
|
424
402
|
},
|
|
425
403
|
});
|
|
426
404
|
```
|
|
427
405
|
|
|
428
|
-
Per-record outcomes return as 207 Multi-Status
|
|
429
|
-
|
|
430
|
-
Compile-time refusals: `bulkVariant: true` is rejected on standalone actions (no record context to loop over) and on actions that declare `unsafe` (cross-tenant per-record audit not yet wired). Method is forced to POST regardless of the action's `method` setting — the one-row-to-many-rows asymmetry makes inheriting GET/DELETE confusing. Max batch size is 100 ids per request, mirroring the CRUD batch endpoints. See [Actions → Bulk variant](/compiler/definitions/actions#bulk-variant).
|
|
406
|
+
Per-record outcomes return as 207 Multi-Status. `failFast: true` aborts on the first failure and wraps the loop in `db.transaction()` on tx-supporting providers; D1 fails fast without rollback. Max 100 IDs per request. Rejected on standalone actions and `unsafe` actions.
|
|
431
407
|
|
|
432
408
|
### Aggregations on read views
|
|
433
409
|
|
|
434
|
-
Read views can
|
|
410
|
+
Read views can declare pre-computed metrics that surface alongside the row payload:
|
|
435
411
|
|
|
436
412
|
```ts
|
|
437
413
|
read: {
|
|
@@ -447,51 +423,29 @@ read: {
|
|
|
447
423
|
}
|
|
448
424
|
```
|
|
449
425
|
|
|
450
|
-
|
|
451
|
-
|
|
452
|
-
```json
|
|
453
|
-
{
|
|
454
|
-
"data": [/* paginated rows */],
|
|
455
|
-
"view": "pipeline",
|
|
456
|
-
"pagination": { "count": 50, "page": 1, "pageSize": 50, "hasMore": true },
|
|
457
|
-
"aggregations": {
|
|
458
|
-
"totalApplications": 173,
|
|
459
|
-
"byStatus": { "applied": 102, "screening": 41, "interview": 18, "offer": 7, "rejected": 5 }
|
|
460
|
-
}
|
|
461
|
-
}
|
|
462
|
-
```
|
|
463
|
-
|
|
464
|
-
Aggregations always run over the **same firewalled, filtered set** as the row query — pagination is intentionally ignored, so `?status=applied&limit=10` returns the 10 paged rows AND the count over every applied row. Supported `fn`s: `sum`, `avg`, `min`, `max`, `count` (with or without `field` — `COUNT(*)` vs `COUNT(field)`), `count_distinct`, and `groupBy` (returns `{ value: count }`, NULLs bucket as `"(none)"`).
|
|
465
|
-
|
|
466
|
-
Compile-time validation: `field` must reference a real column; `sum`/`avg` require numeric column types; the same masking opt-out gate that governs `query.{filterable, sortable, searchable}` applies to aggregations (a `sum(salary)` leaks structure even when the row payload is redacted); aggregation names cannot collide with the reserved response fields `data`, `pagination`, `view`. No raw SQL `expr:` form in v1 — column references only. See [Views → Aggregations](/compiler/definitions/views#aggregations).
|
|
426
|
+
Aggregations run over the same firewalled, filtered set as the row query; pagination is intentionally ignored. Supported functions: `sum`, `avg`, `min`, `max`, `count`, `count_distinct`, `groupBy`. See [Views → Aggregations](/compiler/definitions/views#aggregations).
|
|
467
427
|
|
|
468
428
|
---
|
|
469
429
|
|
|
470
430
|
## v0.13.5 — May 6, 2026
|
|
471
431
|
|
|
472
|
-
### Object-form `auth.plugins`
|
|
473
|
-
|
|
474
|
-
The documented object form for per-plugin config — `plugins: { oauthProvider: {...} }`, `plugins: { organization: { teams: { enabled: true } } }`, etc. (see [Better Auth Plugins → Custom configuration](/stack/auth/plugins#oauth-provider-mcp-ready)) — was rejected by the compiler with `plugins.includes is not a function`. `hasCliAuthRoutes` called `.includes()` directly on `auth.config.plugins` to detect `deviceAuthorization`, and `generateAuthFiles` flattened plugins to a string array before handing them to the better-auth generator, silently dropping every per-plugin user option on the way through.
|
|
475
|
-
|
|
476
|
-
Both paths now run through a shared resolver that preserves the user's input format (object in → object out, array in → array out) and only adds the compiler's auto-included plugins (`organization`, `admin`, `apiKey`, plus `bearer` when `deviceAuthorization` is present) as `true` entries that don't clobber user config. Per-plugin options like `oauthProvider: { scopes: [...] }`, `organization: { teams: { enabled: true } }`, and `deviceAuthorization: { verificationUri: '...' }` now reach the generated `auth.ts` as written.
|
|
432
|
+
### Object-form `auth.plugins` config is honored
|
|
477
433
|
|
|
478
|
-
|
|
434
|
+
The documented `plugins: { oauthProvider: {...} }`, `plugins: { organization: { teams: { enabled: true } } }` shapes now flow through the compiler unchanged. Per-plugin options reach the generated `auth.ts` as written.
|
|
479
435
|
|
|
480
|
-
### `roles: ["PUBLIC"]`
|
|
436
|
+
### `roles: ["PUBLIC"]` allowed on writes and actions
|
|
481
437
|
|
|
482
|
-
|
|
438
|
+
`PUBLIC` is the explicit, uppercase opt-in for unauthenticated access on every access node — reads, writes, views, and actions. The runtime trusts the marker; row-level safety comes from firewall, masking, and the action's own validation. `PUBLIC` actions continue to receive mandatory audit logging.
|
|
483
439
|
|
|
484
|
-
|
|
485
|
-
|
|
486
|
-
`USER` and `ADMIN` keep their compile-time prerequisites (firewall must scope by `userId` / admin plugin must be enabled).
|
|
440
|
+
Common pattern: pair `roles: ["PUBLIC"]` with `firewall: { exception: true }` on the resource so the row predicate doesn't reject every unauthenticated caller.
|
|
487
441
|
|
|
488
442
|
---
|
|
489
443
|
|
|
490
444
|
## v0.12.0 — May 5, 2026
|
|
491
445
|
|
|
492
|
-
### Per-room authorization for PartyServer
|
|
446
|
+
### Per-room authorization for PartyServer
|
|
493
447
|
|
|
494
|
-
`bindings.durableObjects[].access`
|
|
448
|
+
`bindings.durableObjects[].access` declares a path-scoped gate that runs the declared resource's firewall and `read.access` pipeline before the WebSocket upgrade:
|
|
495
449
|
|
|
496
450
|
```ts
|
|
497
451
|
durableObjects: [
|
|
@@ -510,119 +464,70 @@ durableObjects: [
|
|
|
510
464
|
},
|
|
511
465
|
} },
|
|
512
466
|
|
|
513
|
-
// Anonymous
|
|
467
|
+
// Anonymous lobbies / public pads: explicit opt-out.
|
|
514
468
|
{ name: 'PublicLobby', className: 'PublicLobby', from: 'lib/PublicLobby',
|
|
515
469
|
access: 'public' },
|
|
516
|
-
]
|
|
470
|
+
]
|
|
517
471
|
```
|
|
518
472
|
|
|
519
|
-
The gate 401s unauthenticated callers, 403s when the firewall hides the row, 404s when the row is missing
|
|
473
|
+
The gate 401s unauthenticated callers, 403s when the firewall hides the row, 404s when the row is missing. Resource references are validated against feature names at compile time. See [PartyServer Rooms → Per-room authorization](/stack/realtime/partyserver-rooms#per-room-authorization-via-access-v012).
|
|
520
474
|
|
|
521
475
|
---
|
|
522
476
|
|
|
523
477
|
## v0.11.1 — May 5, 2026
|
|
524
478
|
|
|
525
|
-
### PartyServer auto-mount is
|
|
526
|
-
|
|
527
|
-
The `/realtime/*` auto-mount shipped in v0.11.0 didn't gate WebSocket upgrades — anyone who knew a room ID (CUID2, hard to guess but not a security boundary) could open a connection. `authMiddleware` populated the request context but `partyserverMiddleware` doesn't 401 anonymous upgrades on its own.
|
|
528
|
-
|
|
529
|
-
The auto-mount now wraps `partyserverMiddleware` in an auth check: `401 Unauthorized` if the caller has no resolved auth context, otherwise the upgrade proceeds. The four auth mechanisms the rest of the worker honors (session cookie, JWT bearer, `x-api-key` header, `?api_key=` / `?key=` query) all unlock connections automatically.
|
|
479
|
+
### PartyServer auto-mount is secure by default
|
|
530
480
|
|
|
531
|
-
|
|
532
|
-
|
|
533
|
-
No code changes required — `quickback compile` regenerates the gated mount automatically. Single-tenant alphas weren't exploitable in practice (room IDs aren't logged or surfaced); multi-tenant projects should redeploy to pick this up.
|
|
481
|
+
The `/realtime/*` auto-mount now wraps `partyserverMiddleware` in an auth check. Unauthenticated upgrades return 401; the four auth mechanisms (session cookie, JWT bearer, `x-api-key` header, query parameter) all unlock connections. Per-room access remains the `Server` class's responsibility in `onConnect`.
|
|
534
482
|
|
|
535
483
|
---
|
|
536
484
|
|
|
537
485
|
## v0.11.0 — May 5, 2026
|
|
538
486
|
|
|
539
|
-
### OAuth Provider
|
|
540
|
-
|
|
541
|
-
Quickback can now act as a standards-compliant OAuth 2.1 + OIDC authorization server via [`@better-auth/oauth-provider`](https://better-auth.com/docs/plugins/oauth-provider). Enable it with `plugins: ["oauthProvider"]` in your auth config — the compiler auto-includes Better Auth's `jwt` plugin (the OAuth provider delegates access-token signing to it) and the Account SPA gains a `/consent` page for the standard authorization-code flow.
|
|
542
|
-
|
|
543
|
-
This replaces Better Auth's deprecated `mcp` plugin and gives every future MCP client (Cursor, Claude Desktop, claude.ai connectors, custom tooling) RFC 7591 dynamic client registration + the well-known discovery documents they need to bootstrap themselves. See [Auth Plugins → OAuth Provider](/stack/auth/plugins#oauth-provider-mcp-ready).
|
|
487
|
+
### OAuth Provider (MCP-ready)
|
|
544
488
|
|
|
545
|
-
|
|
489
|
+
Quickback can act as a standards-compliant OAuth 2.1 + OIDC authorization server via [`@better-auth/oauth-provider`](https://better-auth.com/docs/plugins/oauth-provider). Enable with `plugins: ["oauthProvider"]`. The compiler auto-includes Better Auth's `jwt` plugin and the Account SPA gains a `/consent` page for the standard authorization-code flow.
|
|
546
490
|
|
|
547
|
-
|
|
491
|
+
This replaces Better Auth's deprecated `mcp` plugin and gives every MCP client (Cursor, Claude Desktop, claude.ai connectors, custom tooling) RFC 7591 dynamic client registration plus the discovery documents they need to bootstrap. See [Auth Plugins → OAuth Provider](/stack/auth/plugins#oauth-provider-mcp-ready).
|
|
548
492
|
|
|
549
|
-
|
|
493
|
+
### API keys via query parameter
|
|
550
494
|
|
|
551
|
-
|
|
495
|
+
The auth middleware now accepts API keys as `?api_key=…` or `?key=…` query parameters. The `x-api-key` header takes precedence when both are sent. Prefer the header whenever the client supports it — query parameters land in access logs and `Referer` headers.
|
|
552
496
|
|
|
553
|
-
|
|
497
|
+
### PartyServer rooms + realtime URL split
|
|
554
498
|
|
|
555
|
-
|
|
556
|
-
- **`/realtime/<binding>/<room-id>` is the new mount for [PartyServer](/stack/realtime/partyserver-rooms) rooms** — bidirectional, per-room (per-document) Durable Objects with presence and lifecycle hooks. Auto-mounted via `hono-party` whenever a project declares any in-worker DO via `bindings.durableObjects[].from`. Use these for collaborative editing, live cursors, and per-room state.
|
|
499
|
+
The realtime URL space is reorganized so names match what each primitive does:
|
|
557
500
|
|
|
558
|
-
|
|
501
|
+
- **`/realtime/v1/*` → `/broadcast/v1/*`** — the org-wide Broadcaster moves to its semantically accurate prefix.
|
|
502
|
+
- **`/realtime/<binding>/<room-id>`** — new mount for [PartyServer](/stack/realtime/partyserver-rooms) rooms. Per-room Durable Objects with presence and lifecycle hooks. Auto-mounted whenever a project declares any in-worker DO.
|
|
559
503
|
|
|
560
|
-
|
|
561
|
-
- The auth-ui SPA helpers `getRealtimeWsUrl()` / `getRealtimeTicketUrl()` are renamed to `getBroadcastWsUrl()` / `getBroadcastTicketUrl()`. The `appConfig.routes.api.realtime` field is renamed to `appConfig.routes.api.broadcast`.
|
|
562
|
-
- WebSocket subscribers that hardcoded `/realtime/v1/websocket` or `/realtime/v1/ws-ticket` need to be updated to `/broadcast/v1/...`. The bundled CMS and Account SPAs handle this automatically; custom clients need a one-line change.
|
|
504
|
+
**Breaking** — recompile + redeploy required:
|
|
563
505
|
|
|
564
|
-
|
|
506
|
+
- `REALTIME_URL` env var renamed to `BROADCAST_URL`.
|
|
507
|
+
- SPA helpers `getRealtimeWsUrl()` / `getRealtimeTicketUrl()` renamed to `getBroadcastWsUrl()` / `getBroadcastTicketUrl()`.
|
|
508
|
+
- `appConfig.routes.api.realtime` renamed to `appConfig.routes.api.broadcast`.
|
|
565
509
|
|
|
566
|
-
|
|
510
|
+
`partyserver`, `partysocket`, and `hono-party` are pre-installed in the compiler image; collab projects compile without an extra `npm install` step.
|
|
567
511
|
|
|
568
512
|
---
|
|
569
513
|
|
|
570
514
|
## v0.10.20 — May 4, 2026
|
|
571
515
|
|
|
572
|
-
### In-worker Durable Objects
|
|
516
|
+
### In-worker Durable Objects
|
|
573
517
|
|
|
574
|
-
`bindings.durableObjects`
|
|
575
|
-
|
|
576
|
-
Adding `from` flips the entry into in-worker mode and the compiler does both:
|
|
518
|
+
`bindings.durableObjects[].from` flips a DO binding into in-worker mode and emits the export, the `[[migrations]]` block, and the `CloudflareBindings` type all together:
|
|
577
519
|
|
|
578
520
|
```ts
|
|
579
|
-
durableObjects: [
|
|
580
|
-
|
|
581
|
-
|
|
582
|
-
|
|
583
|
-
|
|
584
|
-
},
|
|
585
|
-
]
|
|
586
|
-
```
|
|
587
|
-
|
|
588
|
-
Generates:
|
|
589
|
-
- `src/index.ts`: `export { ItemStream } from './features/loops/lib/ItemStream';` — wrangler resolves the binding by class export.
|
|
590
|
-
- `wrangler.toml`: a `[[migrations]]` block with `tag = "qb-do-ItemStream"` and `new_sqlite_classes = ["ItemStream"]`.
|
|
591
|
-
- `CloudflareBindings`: `ITEM_STREAM: DurableObjectNamespace` so `c.env.ITEM_STREAM.idFromName(...)` typechecks.
|
|
592
|
-
|
|
593
|
-
Where the class file lives: in-worker DO classes go under `quickback/lib/` or `quickback/features/<feature>/lib/` — both copy verbatim into the generated `src/` tree on every compile (the rest of `src/` is wiped). The `from` value is the resulting `src/`-relative path with no `./` prefix and no `.ts` suffix.
|
|
594
|
-
|
|
595
|
-
`from` and `scriptName` are mutually exclusive — the compiler rejects entries that set both. Cross-worker entries (`scriptName` set) skip the re-export and the migration block; the exporting worker owns its own migration table.
|
|
596
|
-
|
|
597
|
-
`migrationTag` (default `qb-do-${className}`) is stable across regenerations and **must never be removed or renamed once deployed** — wrangler tracks applied tags and will reject deploys that try to walk them back. `useSqlite` defaults to `true`; set to `false` for legacy KV-backed DOs.
|
|
598
|
-
|
|
599
|
-
See [Bindings → Durable Objects](/compiler/config/bindings#durableobjects) for the full reference.
|
|
600
|
-
|
|
601
|
-
---
|
|
602
|
-
|
|
603
|
-
## v0.10.19 — May 4, 2026
|
|
604
|
-
|
|
605
|
-
### Fix: bundled-SPA auth survives `wrangler dev` on custom_domain projects
|
|
606
|
-
|
|
607
|
-
`wrangler dev` rewrites the configured `custom_domain` host in **every** response header value (Location, Content-Security-Policy, X-…) to the local hostname, with a case-sensitive substring matcher. That mangles the CSP `connect-src` for projects with `domain: "api.example.com"` + bundled CMS / Account SPAs:
|
|
608
|
-
|
|
609
|
-
```
|
|
610
|
-
# Compiled (correct)
|
|
611
|
-
connect-src 'self' https://api.example.com …
|
|
612
|
-
|
|
613
|
-
# Served by wrangler dev (mangled)
|
|
614
|
-
connect-src 'self' https://localhost:8787 …
|
|
521
|
+
durableObjects: [{
|
|
522
|
+
name: "ITEM_STREAM",
|
|
523
|
+
className: "ItemStream",
|
|
524
|
+
from: "features/loops/lib/ItemStream",
|
|
525
|
+
}]
|
|
615
526
|
```
|
|
616
527
|
|
|
617
|
-
|
|
618
|
-
|
|
619
|
-
The compiler now emits the SPA-baked-origin literal in `connect-src` with the host's first letter capitalised (`https://Api.example.com`). CSP host-source matching is ASCII case-insensitive per CSP3, so browsers accept it for connections to `https://api.example.com`; wrangler's case-sensitive matcher misses it. The case-shift is applied at compile time and only to URLs whose host matches the configured `custom_domain` — other origins (localhost, third-party hosts) are unchanged.
|
|
620
|
-
|
|
621
|
-
`TRUSTED_ORIGINS` keeps its lowercase prod entries: it's consumed by the CORS `isTrustedOrigin` check via `Array.includes()` against the browser-supplied Origin header (always lowercase). The CSP fix only needs to land on the SPA-baked literal — that's the entry the SPA's hardcoded fetch needs covered.
|
|
622
|
-
|
|
623
|
-
If wrangler ships a fix for the response-header rewrite, the case-shifted source remains a valid CSP entry that browsers match identically — no follow-up needed in user code.
|
|
528
|
+
DO class files live under `quickback/lib/` or `quickback/features/<feature>/lib/` — both copy verbatim into the generated `src/` tree on every compile. `from` and `scriptName` are mutually exclusive; cross-worker DOs (`scriptName` set) skip the re-export and migration block.
|
|
624
529
|
|
|
625
|
-
|
|
530
|
+
`migrationTag` (default `qb-do-${className}`) is stable across regenerations and must never be removed or renamed once deployed. `useSqlite` defaults to `true`. See [Bindings → Durable Objects](/compiler/config/bindings#durableobjects).
|
|
626
531
|
|
|
627
532
|
---
|
|
628
533
|
|
|
@@ -630,93 +535,45 @@ If wrangler ships a fix for the response-header rewrite, the case-shifted source
|
|
|
630
535
|
|
|
631
536
|
### `experimentalRemote` — share deployed D1 with `wrangler dev`
|
|
632
537
|
|
|
633
|
-
Per-binding `experimental_remote = true`
|
|
538
|
+
Per-binding `experimental_remote = true` lets `wrangler dev` read/write deployed D1 for selected bindings:
|
|
634
539
|
|
|
635
540
|
```ts
|
|
636
541
|
providers: {
|
|
637
542
|
database: defineDatabase("cloudflare-d1", {
|
|
638
543
|
splitDatabases: true,
|
|
639
|
-
experimentalRemote: {
|
|
640
|
-
auth: true, // wrangler dev reads/writes deployed AUTH_DB
|
|
641
|
-
features: false, // (default) features stays local
|
|
642
|
-
audit: false,
|
|
643
|
-
webhooks: false,
|
|
644
|
-
files: false,
|
|
645
|
-
},
|
|
544
|
+
experimentalRemote: { auth: true, features: false },
|
|
646
545
|
}),
|
|
647
546
|
}
|
|
648
547
|
```
|
|
649
548
|
|
|
650
|
-
|
|
549
|
+
Useful for "share prod auth in dev, keep feature writes sandboxed." Off by default.
|
|
651
550
|
|
|
652
551
|
### Google OAuth + signup ToS
|
|
653
552
|
|
|
654
|
-
The Account SPA
|
|
655
|
-
|
|
656
|
-
Signup flow gains a Terms-of-Service checkbox gate (configurable via the Account SPA's branding config).
|
|
657
|
-
|
|
658
|
-
### CLI compile auth gate + device-auth redirect fix
|
|
659
|
-
|
|
660
|
-
- `quickback compile` now requires authentication for cloud-compiler runs (closes the unauth public-compile path).
|
|
661
|
-
- The device-flow `/cli/authorize` page was sending `?returnTo=` to login, but `signup.tsx` and the `_authenticated` middleware only read `?redirect=` — so a user who clicked "Create one" from `/login` lost the return URL. Standardized on `?redirect=` everywhere.
|
|
662
|
-
|
|
663
|
-
### Skill restructure (Claude Code skill)
|
|
553
|
+
The Account SPA wires Google OAuth end-to-end when configured under `auth.config.socialProviders.google.enabled`. The signup flow gains a Terms-of-Service checkbox gate (configurable via the Account SPA branding).
|
|
664
554
|
|
|
665
|
-
|
|
555
|
+
### CLI compile auth gate
|
|
666
556
|
|
|
667
|
-
-
|
|
668
|
-
- Reference docs split into `Compiler` and `Stack` sections
|
|
669
|
-
- Docs bundled as **files** the model navigates with `Read` / `Glob` rather than via `quickback docs <topic>` shell calls — same content, fewer tool calls per lookup
|
|
670
|
-
- Tightened against audit gaps surfaced by red-team review
|
|
671
|
-
|
|
672
|
-
Run `quickback claude install` to pick up the new skill layout.
|
|
557
|
+
`quickback compile` now requires authentication for cloud-compiler runs. Device-flow `?redirect=` parameters are standardized across the login + signup pages so a user clicking "Create one" no longer loses their return URL.
|
|
673
558
|
|
|
674
559
|
---
|
|
675
560
|
|
|
676
|
-
## v0.10.17 — May 2, 2026
|
|
677
|
-
|
|
678
|
-
### Security fix: CSP auto-config no longer widens `default-src`
|
|
679
|
-
|
|
680
|
-
When 0.10.15's auto-config was asked to add a value to a directive the user hadn't declared (e.g. `https://fonts.googleapis.com` → `style-src` when only `default-src` was set), it incorrectly pushed the value into `default-src` itself. Because CSP3 fall-back semantics make `default-src` the fallback for `script-src`, `img-src`, `media-src`, and others, this widened the attack surface to every directive that fell back to it — a `style-src`-only host became reachable from `script-src`.
|
|
681
|
-
|
|
682
|
-
0.10.17 fixes the logic: missing target directives are now **scaffolded** with the user's `default-src` values as baseline, then extended with the auto-config addition. `default-src` stays clean. The new directive (e.g. `style-src`) covers exactly the styles the SPA needs and nothing else.
|
|
683
|
-
|
|
684
|
-
Before (0.10.16):
|
|
685
|
-
```
|
|
686
|
-
default-src 'self' https://fonts.googleapis.com https://fonts.gstatic.com @trustedOrigins https://api.example.com
|
|
687
|
-
```
|
|
688
|
-
|
|
689
|
-
After (0.10.17):
|
|
690
|
-
```
|
|
691
|
-
default-src 'self'
|
|
692
|
-
style-src 'self' 'unsafe-inline' https://fonts.googleapis.com
|
|
693
|
-
font-src 'self' https://fonts.gstatic.com
|
|
694
|
-
connect-src 'self' @trustedOrigins https://api.example.com
|
|
695
|
-
```
|
|
561
|
+
## v0.10.15–v0.10.17 — May 2, 2026
|
|
696
562
|
|
|
697
|
-
|
|
563
|
+
### CSP auto-config
|
|
698
564
|
|
|
699
|
-
|
|
565
|
+
When `security.csp` is set, the compiler widens directives additively based on the project's enabled features:
|
|
700
566
|
|
|
701
|
-
|
|
702
|
-
|
|
703
|
-
|
|
704
|
-
|
|
705
|
-
|
|
706
|
-
|
|
707
|
-
When the bundled CMS or Account SPA is enabled, the compiler already inlines the API URL into the SPA bundle as a string literal at build time (`VITE_QUICKBACK_API_URL=https://${unifiedDomain}`). That hardcoded URL is what the SPA actually fetches — regardless of which origin is currently serving the page. CSP `connect-src` must allow it explicitly.
|
|
708
|
-
|
|
709
|
-
0.10.16's auto-config picks up every domain the compiler already knows about — `config.domain`, the inferred `quickback.{baseDomain}`, `cms.domain`, `account.domain`, the admin domain — and adds `https://${each}` to `connectSrc` whenever a bundled SPA is enabled.
|
|
710
|
-
|
|
711
|
-
The motivating case: running the SPA on `localhost:5173` while it's still baked against `https://quickback.your-app.com`. Pre-0.10.16 the localhost CSP's `'self'` blocked the prod URL; users were patching it manually. Now it just works.
|
|
712
|
-
|
|
713
|
-
```
|
|
714
|
-
[security] auto-added https://quickback.loop.kardoe.com to csp.connectSrc — account: true → bundled Account SPA → SPA bundle hardcodes https://quickback.loop.kardoe.com as VITE_QUICKBACK_API_URL / etc.
|
|
715
|
-
```
|
|
567
|
+
| Trigger | Auto-added | Directive |
|
|
568
|
+
|---|---|---|
|
|
569
|
+
| `cms: true` OR `account: true` | `'unsafe-inline'`, `https://fonts.googleapis.com` | `styleSrc` |
|
|
570
|
+
| `cms: true` OR `account: true` | `https://fonts.gstatic.com` | `fontSrc` |
|
|
571
|
+
| `csp` set (always) | `@trustedOrigins` | `connectSrc` |
|
|
572
|
+
| Bundled SPA enabled | SPA-baked API origin (`config.domain`, `quickback.{baseDomain}`, `cms.domain`, `account.domain`) | `connectSrc` |
|
|
716
573
|
|
|
717
|
-
|
|
574
|
+
Anything you already wrote stays — auto-config never removes or overrides. Each applied addition is logged to stderr. Opt out with `security: { cspAutoConfig: false }`.
|
|
718
575
|
|
|
719
|
-
|
|
576
|
+
Most projects can write the minimal:
|
|
720
577
|
|
|
721
578
|
```ts
|
|
722
579
|
security: {
|
|
@@ -729,286 +586,107 @@ security: {
|
|
|
729
586
|
}
|
|
730
587
|
```
|
|
731
588
|
|
|
732
|
-
…and the compiler fills in
|
|
733
|
-
|
|
734
|
-
---
|
|
735
|
-
|
|
736
|
-
## v0.10.15 — May 2, 2026
|
|
737
|
-
|
|
738
|
-
### CSP auto-config — bundled-SPA origins added automatically
|
|
589
|
+
…and the compiler fills in font hosts, trusted origins, and SPA-baked URLs.
|
|
739
590
|
|
|
740
|
-
When
|
|
741
|
-
|
|
742
|
-
| Trigger | Auto-added | Directive |
|
|
743
|
-
|---|---|---|
|
|
744
|
-
| `cms: true` OR `account: true` | `'unsafe-inline'`, `https://fonts.googleapis.com` | `styleSrc` |
|
|
745
|
-
| `cms: true` OR `account: true` | `https://fonts.gstatic.com` | `fontSrc` |
|
|
746
|
-
| `csp` set (always) | `@trustedOrigins` | `connectSrc` |
|
|
747
|
-
|
|
748
|
-
Anything you already wrote stays — auto-config never removes or overrides. Every applied addition prints to stderr at compile so the magic is visible:
|
|
749
|
-
|
|
750
|
-
```
|
|
751
|
-
[security] auto-added 'unsafe-inline' to csp.styleSrc — account: true → bundled Account SPA → inline style attributes from Tailwind / TanStack Router
|
|
752
|
-
[security] auto-added @trustedOrigins to csp.connectSrc — CORS-trusted origins must be reachable from XHR/fetch (matches cors() allowlist)
|
|
753
|
-
```
|
|
754
|
-
|
|
755
|
-
The recipe in [the security docs](/compiler/config/security#example-paste-in-csp-for-a-quickback-spa-project) becomes ~5 lines shorter — most projects no longer need to list `fonts.googleapis.com` / `fonts.gstatic.com` / `@trustedOrigins` themselves. **Loop's CSP shrinks dramatically** after recompiling against this version.
|
|
756
|
-
|
|
757
|
-
**Opt-out:** `security: { cspAutoConfig: false, csp: { ... } }` for projects fronted by a CDN that injects its own CSP, or teams that want strict from-scratch control.
|
|
758
|
-
|
|
759
|
-
**Smart fallback:** if you set `defaultSrc` but omit the target directive (e.g. `defaultSrc: ['@self']` and nothing for `connectSrc`), the addition lands in `defaultSrc` rather than creating a sibling directive — CSP fall-back semantics mean a sibling would *narrow* your intent, so we preserve the broader fallback.
|
|
760
|
-
|
|
761
|
-
### Troubleshooting table for CSP violations
|
|
762
|
-
|
|
763
|
-
The security docs page now includes a [Troubleshooting CSP violations](/compiler/config/security#troubleshooting-csp-violations) table mapping browser console errors back to the directive that needs widening. Useful when auto-config is disabled or the project has a non-bundled SPA hitting third-party origins.
|
|
764
|
-
|
|
765
|
-
### Out of scope (deferred)
|
|
766
|
-
|
|
767
|
-
- **Per-request CSP nonces** (`@nonce` sentinel implementation) — Phase 2 / 0.10.16. Sentinel still errors at compile in 0.10.15.
|
|
768
|
-
- **`revocationCheck: 'kv'` for `auth.jwt`** — schema accepts it, runtime still errors at compile. Slipped from 0.10.15 to 0.10.16.
|
|
769
|
-
- **Public R2 host auto-add to `imgSrc`** — most R2 access today goes through the worker so the SPA fetches from `'@self'`. Will revisit once we have a clean way to discover public-bucket hosts at compile.
|
|
591
|
+
When a target directive is missing, auto-config scaffolds it from `default-src` baseline rather than widening `default-src` itself — CSP3 fall-back semantics would otherwise leak the addition to every directive that falls back to `default-src`.
|
|
770
592
|
|
|
771
593
|
---
|
|
772
594
|
|
|
773
595
|
## v0.10.14 — May 1, 2026
|
|
774
596
|
|
|
775
|
-
### `auth.jwt`
|
|
597
|
+
### `auth.jwt` config
|
|
776
598
|
|
|
777
|
-
|
|
599
|
+
The bearer-token JWT used by the auth fast-path is configurable. Tune `expiresIn` to bound the post-revocation replay window without affecting browser SPAs (which auto-refresh on every authed call):
|
|
778
600
|
|
|
779
601
|
```ts
|
|
780
602
|
auth: {
|
|
781
603
|
jwt: {
|
|
782
|
-
expiresIn: 30,
|
|
783
|
-
issuer: 'my-api',
|
|
784
|
-
audience: 'partner-svc',
|
|
785
|
-
secretEnv: 'CUSTOM_JWT_SECRET',
|
|
604
|
+
expiresIn: 30,
|
|
605
|
+
issuer: 'my-api',
|
|
606
|
+
audience: 'partner-svc',
|
|
607
|
+
secretEnv: 'CUSTOM_JWT_SECRET',
|
|
786
608
|
},
|
|
787
609
|
}
|
|
788
610
|
```
|
|
789
611
|
|
|
790
|
-
|
|
612
|
+
### Admin MCP endpoints filtered
|
|
791
613
|
|
|
792
|
-
|
|
614
|
+
Better Auth admin endpoints (`/admin/list-users`, `/admin/ban-user`, etc.) now carry `x-access: { userRole: ['admin'] }` in the generated OpenAPI spec. The MCP `tools/list` access-filter drops them for non-admin callers.
|
|
793
615
|
|
|
794
|
-
###
|
|
616
|
+
### Declarative `security` config
|
|
795
617
|
|
|
796
|
-
|
|
618
|
+
Every security response header (`Content-Security-Policy`, COOP, COEP, CORP, HSTS, `X-Frame-Options`, `Referrer-Policy`, `Permissions-Policy`) is configurable from `quickback.config.ts`. `@`-prefixed sentinels (`@self`, `@none`, `@unsafe-inline`, `@trustedOrigins`, etc.) replace awkward `"'self'"` quoting.
|
|
797
619
|
|
|
798
|
-
|
|
620
|
+
The compiler lints the resolved config for known footguns: `@unsafe-inline` in `script-src`, wildcard sources, missing `default-src`, HSTS preload-list misconfiguration.
|
|
799
621
|
|
|
800
|
-
|
|
622
|
+
### HSTS skipped on localhost
|
|
801
623
|
|
|
802
|
-
|
|
803
|
-
security: {
|
|
804
|
-
csp: {
|
|
805
|
-
defaultSrc: ['@self'],
|
|
806
|
-
scriptSrc: ['@self'],
|
|
807
|
-
styleSrc: ['@self', '@unsafe-inline'],
|
|
808
|
-
frameAncestors: ['@none'],
|
|
809
|
-
objectSrc: ['@none'],
|
|
810
|
-
upgradeInsecureRequests: true,
|
|
811
|
-
},
|
|
812
|
-
coop: 'same-origin',
|
|
813
|
-
}
|
|
814
|
-
```
|
|
815
|
-
|
|
816
|
-
`@`-prefixed sentinels (`@self`, `@none`, `@unsafe-inline`, `@unsafe-eval`, `@trustedOrigins`, `@nonce`) save users from awkward `"'self'"` quoting and let `@trustedOrigins` resolve to the same allowlist `cors()` uses. Unknown sentinels throw at compile rather than silently stringify into the wire CSP.
|
|
817
|
-
|
|
818
|
-
The compiler runs lint rules over the resolved config — errors for `@nonce` (deferred to 0.10.15), `@unsafe-inline + @nonce` (silently broken), and sentinel-only directives that would resolve to nothing at runtime; warnings for `@unsafe-inline` in `script-src`, wildcard sources, missing `default-src`, HSTS preload-list misconfiguration, etc.
|
|
819
|
-
|
|
820
|
-
Defaults preserve 0.10.13 behaviour byte-for-byte — adding the block without setting any field is a no-op.
|
|
821
|
-
|
|
822
|
-
See [the docs page](/compiler/config/security) for the full reference.
|
|
823
|
-
|
|
824
|
-
### HSTS no longer pins `localhost` to HTTPS
|
|
825
|
-
|
|
826
|
-
The generated middleware now skips `Strict-Transport-Security` when the request hostname is `localhost`, `127.0.0.1`, or `*.localhost`. Without this gate, `wrangler dev` would pin the developer's browser to HTTPS for `max-age` seconds — observable across every project on that machine since HSTS keys on hostname, not port. Affects every project running locally.
|
|
827
|
-
|
|
828
|
-
### Out of scope (deferred)
|
|
829
|
-
|
|
830
|
-
- **Per-request CSP nonces** — Phase 2 / 0.10.15. Sentinel exists at config-validation level so users can author their final CSP today knowing it'll start working when nonces ship.
|
|
831
|
-
- **Asset-hash CSP** for inline `<style>` and `<script>` blocks emitted by the bundled SPAs — Phase 3.
|
|
832
|
-
- **Per-route CSP overrides** (e.g. one looser policy for `/admin`) — single global CSP for now.
|
|
624
|
+
Generated middleware skips `Strict-Transport-Security` when the request hostname is `localhost`, `127.0.0.1`, or `*.localhost`. Without this gate, `wrangler dev` would pin a developer's browser to HTTPS across every project on that machine.
|
|
833
625
|
|
|
834
626
|
---
|
|
835
627
|
|
|
836
628
|
## v0.10.13 — May 1, 2026
|
|
837
629
|
|
|
838
|
-
### Clickjacking
|
|
839
|
-
|
|
840
|
-
Every Worker now emits two clickjacking-defence headers on every
|
|
841
|
-
response:
|
|
842
|
-
|
|
843
|
-
- `Content-Security-Policy: frame-ancestors 'self' <TRUSTED_ORIGINS…>`
|
|
844
|
-
- `X-Frame-Options: SAMEORIGIN`
|
|
845
|
-
|
|
846
|
-
The CSP allowlist is sourced from the same `TRUSTED_ORIGINS` constant
|
|
847
|
-
that gates CORS, so users configure their domains in one place
|
|
848
|
-
(`auth.trustedOrigins` / `auth.trustedOriginDefaults` in
|
|
849
|
-
`quickback.config.ts`) and both CORS and frame-ancestors stay in
|
|
850
|
-
lockstep. `'self'` is always allowed so an app's own SPAs can frame
|
|
851
|
-
their own routes (e.g. an account login popover hosted on the same
|
|
852
|
-
origin).
|
|
853
|
-
|
|
854
|
-
Modern browsers obey `frame-ancestors` and ignore `X-Frame-Options`
|
|
855
|
-
when both are set; the legacy header is included for clients that
|
|
856
|
-
don't speak CSP3. The CSP intentionally only sets `frame-ancestors` —
|
|
857
|
-
adding `script-src` / `default-src` would need a much wider audit
|
|
858
|
-
across SPA assets, inline scripts, and third-party embeds, so that's
|
|
859
|
-
left as a follow-up.
|
|
860
|
-
|
|
861
|
-
Recompile (`quickback compile`) and redeploy to pick this up — no
|
|
862
|
-
config change needed unless you want to allow extra cross-origin
|
|
863
|
-
iframe embeds, in which case add them to `auth.trustedOrigins`.
|
|
864
|
-
|
|
865
|
-
---
|
|
866
|
-
|
|
867
|
-
## v0.10.12 — May 1, 2026
|
|
868
|
-
|
|
869
|
-
### Bundled-docs sync for the MCP recon fix
|
|
630
|
+
### Clickjacking defence on every Worker
|
|
870
631
|
|
|
871
|
-
|
|
872
|
-
Claude Code skill, Cursor rules, and other AI assistants) so they
|
|
873
|
-
reflect the corrected `tools/list` access-filter behavior and CORS
|
|
874
|
-
posture shipped in v0.10.11. The `compiler/config/agents.mdx` page
|
|
875
|
-
itself was already corrected on the docs site immediately after the
|
|
876
|
-
0.10.11 release; this bump propagates that text into the bundle inside
|
|
877
|
-
`@quickback-dev/cli`.
|
|
878
|
-
|
|
879
|
-
No runtime or compiler behavior change — re-running `quickback compile`
|
|
880
|
-
against this version produces the same output as v0.10.11.
|
|
632
|
+
Every Worker emits `Content-Security-Policy: frame-ancestors 'self' <TRUSTED_ORIGINS…>` and `X-Frame-Options: SAMEORIGIN` on every response. The CSP allowlist is sourced from the same `TRUSTED_ORIGINS` constant that gates CORS.
|
|
881
633
|
|
|
882
634
|
---
|
|
883
635
|
|
|
884
636
|
## v0.10.11 — May 1, 2026
|
|
885
637
|
|
|
886
|
-
### MCP `tools/list` is
|
|
887
|
-
|
|
888
|
-
The generated MCP-over-HTTP server (`src/routes/mcp.ts`) had three holes
|
|
889
|
-
that turned a standard pentest into trivial recon:
|
|
890
|
-
|
|
891
|
-
1. `tools/list` returned the entire tool catalogue to anyone — including
|
|
892
|
-
admin-only endpoints — without checking auth or roles. Tool
|
|
893
|
-
descriptions also leaked sentences like `[UNSAFE] bypasses tenant
|
|
894
|
-
scoping and requires elevated access` verbatim.
|
|
895
|
-
2. The endpoint set `Access-Control-Allow-Origin: *` so any origin could
|
|
896
|
-
pull the catalogue from a browser.
|
|
897
|
-
3. Unauthenticated `GET /mcp` enumerated every tool name in its
|
|
898
|
-
discovery payload.
|
|
899
|
-
|
|
900
|
-
Fix:
|
|
901
|
-
|
|
902
|
-
- Each tool now carries sanitised access metadata (`_access` covering
|
|
903
|
-
`roles` / `userRole` / `or` / `and`, plus `_public` for `PUBLIC`
|
|
904
|
-
pseudo-role or empty `security`). `tools/list` filters against the
|
|
905
|
-
caller's `ctx` — unauth callers see only `_public` tools, authed
|
|
906
|
-
callers see only role-gated tools they pass. Record predicates and
|
|
907
|
-
function-form access (opaque at list time) are dropped.
|
|
908
|
-
- Wildcard CORS removed entirely. The parent app's `cors()` middleware
|
|
909
|
-
(origin allowlist via `TRUSTED_ORIGINS` + `BETTER_AUTH_URL`) now
|
|
910
|
-
applies uniformly to `/mcp`, same as every other route.
|
|
911
|
-
- `[UNSAFE] ... bypasses tenant scoping ...` flavour text is gone.
|
|
912
|
-
`annotations.destructiveHint` and `_unsafe` remain — those are the
|
|
913
|
-
spec-correct signals for clients to warn users.
|
|
914
|
-
- Unauthenticated `GET /mcp` no longer lists tool names. Inventory is
|
|
915
|
-
only available via the access-filtered `tools/list`.
|
|
916
|
-
|
|
917
|
-
This filter is recon-mitigation, not a security boundary: `tools/call`
|
|
918
|
-
still re-enters the Hono app and runs every middleware (auth, firewall,
|
|
919
|
-
access, guards, masking), so hiding a tool from list never weakens the
|
|
920
|
-
underlying gate.
|
|
921
|
-
|
|
922
|
-
Known follow-up: Better Auth admin endpoints (`ban-user`, `create-user`,
|
|
923
|
-
`impersonate-user`, etc.) don't yet emit `x-access` in the OpenAPI spec,
|
|
924
|
-
so any logged-in user still sees them in `tools/list` (the actual call
|
|
925
|
-
is still gated by the admin plugin). Tracked separately.
|
|
926
|
-
|
|
927
|
-
---
|
|
928
|
-
|
|
929
|
-
## v0.10.10 — April 29, 2026
|
|
930
|
-
|
|
931
|
-
### Reject reserved keys inside `access.record` at compile time
|
|
638
|
+
### MCP `tools/list` is access-filtered
|
|
932
639
|
|
|
933
|
-
|
|
934
|
-
entries — keys must be column names. Putting `and: [...]` (or `or` /
|
|
935
|
-
`roles` / `userRole`) inside `record` was a real-world footgun: the
|
|
936
|
-
runtime treated the literal string `"and"` as a column lookup, the
|
|
937
|
-
predicate failed on every row, and the caller got a silent `403` /
|
|
938
|
-
empty list with nothing pointing at the misuse. The TypeScript type
|
|
939
|
-
couldn't catch this — `RecordConditions` is an open-ended index
|
|
940
|
-
signature, so any key parses.
|
|
640
|
+
Each MCP tool now carries sanitised access metadata. `tools/list` filters against the caller's `ctx`: unauthenticated callers see only `PUBLIC` tools, authenticated callers see only role-gated tools they pass.
|
|
941
641
|
|
|
942
|
-
|
|
943
|
-
|
|
944
|
-
|
|
945
|
-
reserved key:
|
|
642
|
+
- Wildcard CORS removed from the MCP endpoint.
|
|
643
|
+
- Unauthenticated `GET /mcp` no longer enumerates tool names.
|
|
644
|
+
- Internal flavor text is removed; `annotations.destructiveHint` and `_unsafe` remain — those are the spec-correct signals for clients.
|
|
946
645
|
|
|
947
|
-
-
|
|
948
|
-
sibling: `{ and: [{ record: { ... } }, { record: { ... } }] }`
|
|
949
|
-
- `roles` / `userRole` inside `record` → put them at the access node
|
|
950
|
-
alongside `record`: `{ roles: [...], record: { ... } }`
|
|
951
|
-
|
|
952
|
-
The error names the exact origin (`crud.update.access`,
|
|
953
|
-
`actions.focus.access.or[1]`, etc.) so the fix lands in the right place.
|
|
646
|
+
`tools/call` continues to re-enter the Hono app and run every middleware (auth, firewall, access, guards, masking), so hiding a tool from list never weakens the underlying gate.
|
|
954
647
|
|
|
955
648
|
---
|
|
956
649
|
|
|
957
|
-
## v0.10.
|
|
958
|
-
|
|
959
|
-
### Role hierarchy now expands in record-based action access
|
|
960
|
-
|
|
961
|
-
`auth.roleHierarchy: ['member', 'admin', 'owner']` plus
|
|
962
|
-
`access: { roles: ['member+'] }` on a record-based action used to
|
|
963
|
-
silently 403 valid callers. The standalone-action route generator
|
|
964
|
-
inlined the expanded role list as a JSON literal, but the
|
|
965
|
-
record-based generator read the access config back through the
|
|
966
|
-
runtime `actions['name'].access` import — the user's source, where
|
|
967
|
-
the unexpanded `'member+'` shorthand still lived. The runtime did
|
|
968
|
-
literal string matching against `ctx.roles`, so an `owner` calling
|
|
969
|
-
the action got `['member+'] !== 'owner'` and was rejected.
|
|
650
|
+
## v0.10.10 — April 29, 2026
|
|
970
651
|
|
|
971
|
-
|
|
972
|
-
same way standalone routes do. `input` and `execute` still flow
|
|
973
|
-
through the runtime import (closures aren't serializable); only the
|
|
974
|
-
access config is lifted to a JSON literal so the compile-time
|
|
975
|
-
expansion actually reaches the matcher.
|
|
652
|
+
### Reserved keys in `access.record` are rejected
|
|
976
653
|
|
|
977
|
-
|
|
978
|
-
behavior in — it asserts that `member+` never reaches the route
|
|
979
|
-
output and that the access config is no longer read from
|
|
980
|
-
`actions[name].access` at runtime.
|
|
654
|
+
`access.record` is a flat field map evaluated as implicit AND between entries — keys must be column names. The compiler now rejects reserved keys (`and`, `or`, `roles`, `userRole`) inside `record` with migration guidance pointing at the working pattern (top-level siblings with their own `record:` blocks).
|
|
981
655
|
|
|
982
656
|
---
|
|
983
657
|
|
|
984
658
|
## v0.10.8 — April 29, 2026
|
|
985
659
|
|
|
986
|
-
### Audit
|
|
660
|
+
### Audit logging on Postgres targets
|
|
661
|
+
|
|
662
|
+
`audit_events` previously only existed on `cloudflare-d1`. The audit table now lives in a dedicated `audit` schema (`drizzle.pgSchema('audit')`) on Postgres targets. The `hasSecurityAudit` gate accepts D1 or any PG dialect; `auditDatabaseId` remains a D1-only requirement.
|
|
987
663
|
|
|
988
|
-
|
|
664
|
+
### `auditDatabaseId` is a compile-time requirement
|
|
989
665
|
|
|
990
|
-
|
|
666
|
+
Projects with unsafe or `PUBLIC` actions that previously produced a placeholder `database_id = "local-audit"` in production now fail at compile time with the exact `wrangler d1 create <project>-audit` command and the config key where the returned ID goes.
|
|
991
667
|
|
|
992
|
-
###
|
|
668
|
+
### Action input → OpenAPI / MCP
|
|
993
669
|
|
|
994
|
-
|
|
670
|
+
`defineAction({ input: z.object({...}) })` schemas flow into the OpenAPI `requestBody` and the MCP tool's `inputSchema.properties`. Simple `z.object` shapes are extracted at compile time; discriminated unions, refinements, recursive schemas, and bare-identifier references run through Zod's native `z.toJSONSchema()` for full-fidelity output.
|
|
995
671
|
|
|
996
|
-
|
|
997
|
-
- Response schemas now emit `required[]` for every non-nullable column, so generated SDKs treat them as guaranteed-present rather than optional.
|
|
998
|
-
- `text(_, { enum: [...] })` columns emit as closed `{ type: "string", enum: [...] }`, narrowing to literal unions.
|
|
999
|
-
- `id` only claims `format: "uuid"` when the project's `generateId` actually produces UUIDs. cuid2 / prefixed / nanoid / serial generators get plain `{ type: "string" }` — strict validators stop rejecting responses against their own spec.
|
|
672
|
+
### OpenAPI fidelity
|
|
1000
673
|
|
|
1001
|
-
|
|
674
|
+
- Response schemas emit `required[]` for every non-nullable column.
|
|
675
|
+
- `text(_, { enum: [...] })` columns emit as closed `{ type: "string", enum: [...] }`.
|
|
676
|
+
- `id` claims `format: "uuid"` only when the project's `generateId` actually produces UUIDs. cuid2 / prefixed / nanoid / serial generators emit plain `{ type: "string" }`.
|
|
1002
677
|
|
|
1003
|
-
|
|
678
|
+
### Minor
|
|
1004
679
|
|
|
1005
|
-
|
|
680
|
+
- Auto-mask predicate verifies the resolved owner column exists before emitting an `or: 'owner'` clause; falls back to roles-only with a warning otherwise.
|
|
681
|
+
- Generated CRUD errors emit canonical `QuickbackErrorCode` enum values (`DB_NOT_NULL_VIOLATION`, `DB_UNIQUE_VIOLATION`, etc.) so generated SDKs can exhaustively switch on `code`. See [API errors](/compiler/targets/hono-api/using-the-api/errors#database).
|
|
1006
682
|
|
|
1007
683
|
---
|
|
1008
684
|
|
|
1009
|
-
##
|
|
685
|
+
## DSL: one file per action, multi-table per feature
|
|
1010
686
|
|
|
1011
|
-
|
|
687
|
+
### One file per action
|
|
688
|
+
|
|
689
|
+
Action authoring is one file per action under `<feature>/actions/<name>.ts`. The filename is the action name and the URL segment:
|
|
1012
690
|
|
|
1013
691
|
```typescript
|
|
1014
692
|
// features/applications/actions/advance.ts
|
|
@@ -1029,65 +707,37 @@ export default defineAction({
|
|
|
1029
707
|
});
|
|
1030
708
|
```
|
|
1031
709
|
|
|
1032
|
-
`defineAction` is imported from a generated per-feature helper at `<feature>/.quickback/define-action.ts` —
|
|
710
|
+
`defineAction` is imported from a generated per-feature helper at `<feature>/.quickback/define-action.ts` — `record`, `input`, and audit fields are typed without manual annotations.
|
|
1033
711
|
|
|
1034
712
|
**Discovery rules:**
|
|
1035
|
-
- `actions/<name>.ts` binds to the feature's primary table
|
|
1036
|
-
- `actions/<table>/<name>.ts` binds to the sibling table file
|
|
1037
|
-
- Setting `path:` makes the action standalone (custom URL, no record fetch
|
|
1038
|
-
- Tableless features
|
|
1039
|
-
- Action names are unique per `(bindTable, name)` pair — sibling-bound actions on different tables may share a verb (e.g. `actions/episodes/publish.ts` + `actions/shows/publish.ts` mount at `/episodes/:id/publish` and `/shows/:id/publish` and don't collide). Standalone actions are unique per `(method, path)`.
|
|
1040
|
-
- Files under `<feature>/lib/` are copied verbatim for feature-local helpers; `quickback/lib/` is exposed via the `~/lib/*` alias for cross-feature shared code (with a one-way import rule enforced at compile time).
|
|
1041
|
-
|
|
1042
|
-
**Retired** (rejected at load time with migration guidance):
|
|
1043
|
-
|
|
1044
|
-
- `actions.ts` (bundled multi-action file)
|
|
1045
|
-
- `_feature.ts` (shared preamble + tableless actions)
|
|
1046
|
-
- `handlers/` directory + `handler:` string ref
|
|
1047
|
-
- `defineActions(table, {…})` and `defineActions(null, {…})`
|
|
1048
|
-
- `export default { actions: {…} }`
|
|
1049
|
-
- Colocated `defineActions` inside table files
|
|
1050
|
-
- `standalone: true` flag (presence of `path:` is the new signal)
|
|
1051
|
-
- `*-actions.ts` / `*.actions.ts` filename patterns
|
|
1052
|
-
|
|
1053
|
-
The phantom-`unsafe` regex bug that flattened nested `unsafe: { … }` blocks into a fake top-level action is gone — the parser now reads action files as real TS modules with real imports, so type inference, jump-to-definition, and rename refactoring all work end-to-end.
|
|
1054
|
-
|
|
1055
|
-
The CLI loader rejects retired primitives at load time with batched migration errors. Existing projects need to be migrated by hand to the new shape before recompiling.
|
|
1056
|
-
|
|
1057
|
-
See the [Actions docs](/compiler/definitions/actions) for the full reference.
|
|
1058
|
-
|
|
1059
|
-
---
|
|
1060
|
-
|
|
1061
|
-
## Multi-table actions per feature
|
|
1062
|
-
|
|
1063
|
-
Features used to support exactly one `defineActions(table, …)` call via `actions.ts`, which forced unnatural feature splits whenever multiple tables in the same feature needed actions (a podcast feature with `episodes`, `shows`, `seasons`, `collections`, etc.). One feature directory can now own actions on multiple tables across three discovery modes:
|
|
713
|
+
- `actions/<name>.ts` binds to the feature's primary table.
|
|
714
|
+
- `actions/<table>/<name>.ts` binds to the sibling table file.
|
|
715
|
+
- Setting `path:` makes the action standalone (custom URL, no record fetch).
|
|
716
|
+
- Tableless features require every action to be standalone.
|
|
1064
717
|
|
|
1065
|
-
|
|
1066
|
-
- **`actions.ts`** (existing) — single primary-table actions file at feature root. Unchanged behaviour.
|
|
1067
|
-
- **`actions/<table>.ts`** — per-table action files for teams that want strict schema/behavior separation or need to break an import cycle.
|
|
718
|
+
**Retired** (rejected at load time with migration guidance): `actions.ts` (bundled multi-action file), `_feature.ts`, `handlers/` directory + `handler:` string ref, `defineActions(table, {…})`, colocated `defineActions` inside table files, `standalone: true` flag, `*-actions.ts` / `*.actions.ts` filename patterns.
|
|
1068
719
|
|
|
1069
|
-
|
|
720
|
+
See [Actions docs](/compiler/definitions/actions).
|
|
1070
721
|
|
|
1071
|
-
|
|
722
|
+
### Multi-table actions per feature
|
|
1072
723
|
|
|
1073
|
-
|
|
724
|
+
One feature directory can own actions on multiple tables. Three discovery modes:
|
|
1074
725
|
|
|
1075
|
-
|
|
726
|
+
- **Colocated** (canonical) — `<table>.ts` containing both `defineTable` and `defineActions(<table>, …)`. One file per entity.
|
|
727
|
+
- **`actions.ts`** — single primary-table actions file at feature root.
|
|
728
|
+
- **`actions/<table>.ts`** — per-table action files for strict schema/behavior separation.
|
|
1076
729
|
|
|
1077
|
-
|
|
730
|
+
Plus a universal `_feature.ts` slot for non-table-bound feature-level actions and shared Zod schemas.
|
|
1078
731
|
|
|
1079
|
-
|
|
1080
|
-
|
|
1081
|
-
Migration: existing `actions.ts` projects compile bit-identically — the legacy single-table path is unchanged. Legacy `*-actions.ts` filenames produce a soft warning and silently aren't picked up; rename to `<table>.ts` (colocated), `actions/<table>.ts`, or single `actions.ts`.
|
|
732
|
+
Action names are unique per `(bindTable, name)` pair. Sibling-bound `actions/episodes/publish.ts` and `actions/shows/publish.ts` mount at `/episodes/:id/publish` and `/shows/:id/publish` and compile cleanly.
|
|
1082
733
|
|
|
1083
734
|
---
|
|
1084
735
|
|
|
1085
|
-
## Firewall: named-scope shape
|
|
736
|
+
## Firewall: named-scope shape
|
|
1086
737
|
|
|
1087
|
-
The named-scope firewall shape
|
|
738
|
+
The named-scope firewall shape is a co-equal user-facing input alongside the predicate array:
|
|
1088
739
|
|
|
1089
740
|
```typescript
|
|
1090
|
-
// All three are now valid; all compile to the same predicate array internally.
|
|
1091
741
|
firewall: { organization: { column: 'tenant_id' } } // named-scope (compact)
|
|
1092
742
|
firewall: { owner: { column: 'account_user_id' } }
|
|
1093
743
|
firewall: { exception: true }
|
|
@@ -1099,27 +749,17 @@ firewall: [
|
|
|
1099
749
|
|
|
1100
750
|
Pick the form that reads better — named-scope for the common one-line case, predicate array when you need custom `in`-lists or non-scope predicates.
|
|
1101
751
|
|
|
1102
|
-
**Auto-detection synonyms
|
|
1103
|
-
|
|
1104
|
-
**`ownerId` is now a targeted error signal.** When a table carries `ownerId` but no isolation column AND no explicit `firewall:`, the compiler raises a specific error: `\`ownerId\` is business-logic ownership, not access control — Quickback won't auto-derive a firewall from it. Either rename to \`userId\` if this column controls access, add a separate \`userId\` / \`organizationId\` column, or specify \`firewall:\` explicitly.` This replaces the generic "missing isolation column" error in the `ownerId`-only case and preserves the documented distinction between RLS-style access control (`userId`) and business-logic ownership (`ownerId`).
|
|
752
|
+
**Auto-detection synonyms.** When `firewall:` is omitted, the compiler scans the schema for an isolation column. The org-scope list accepts `organizationId`, `organisationId`, `orgId`, `organization`, `organisation`, `org` (American + British). User-scope accepts `userId`.
|
|
1105
753
|
|
|
1106
|
-
|
|
754
|
+
**`ownerId` is a targeted error signal.** When a table carries `ownerId` but no isolation column and no explicit `firewall:`, the compiler raises a specific error — `ownerId` is business-logic ownership, not access control. Use `userId` for access control, declare an explicit `firewall:`, or add a separate isolation column.
|
|
1107
755
|
|
|
1108
756
|
---
|
|
1109
757
|
|
|
1110
758
|
## v0.10.0 — April 26, 2026
|
|
1111
759
|
|
|
1112
|
-
### `q.scope()`
|
|
1113
|
-
|
|
1114
|
-
Two related DSL consolidations land. The `q.scope()` half is purely additive; the `masking.query` half rejects three legacy per-capability flags at compile time (migration is mechanical — see below).
|
|
760
|
+
### `q.scope()` — single-declaration tenant scoping
|
|
1115
761
|
|
|
1116
|
-
|
|
1117
|
-
|
|
1118
|
-
1. Auto-derive the firewall predicate (`{ field: 'organizationId', equals: 'ctx.activeOrgId' }`) so the explicit `firewall:` block can be omitted entirely.
|
|
1119
|
-
2. Add the column to `GUARDS_CONFIG.systemManaged` so client input is rejected at the guard layer.
|
|
1120
|
-
3. Auto-populate from `ctx` on create / upsert.
|
|
1121
|
-
|
|
1122
|
-
The systemManaged extension generalises beyond `q.scope()`: any firewall predicate whose `equals` references `ctx.*` adds its `field` to the systemManaged set. So a hand-rolled `firewall: [{ field: 'tenantId', equals: 'ctx.activeOrgId' }]` gets the same treatment.
|
|
762
|
+
`q.scope(kind)` replaces the three-place pattern (column declaration + firewall predicate + ownership-guard) with one column:
|
|
1123
763
|
|
|
1124
764
|
```typescript
|
|
1125
765
|
columns: {
|
|
@@ -1129,304 +769,148 @@ columns: {
|
|
|
1129
769
|
}
|
|
1130
770
|
```
|
|
1131
771
|
|
|
1132
|
-
|
|
772
|
+
`q.scope()` columns auto-derive the firewall predicate, register with the guards layer as `systemManaged` (client input rejected), and auto-populate from `ctx` on create / upsert. The systemManaged extension generalises beyond `q.scope()`: any firewall predicate whose `equals` references `ctx.*` registers its `field` automatically.
|
|
773
|
+
|
|
774
|
+
See [`q.scope()`](/compiler/definitions/schema#qscope--tenant-scope-columns).
|
|
1133
775
|
|
|
1134
|
-
|
|
776
|
+
### `masking[col].query.roles` — unified filter / sort / search gate
|
|
777
|
+
|
|
778
|
+
The three legacy per-capability flags (`filterable`, `searchable`, `sortable`) are replaced by a single `query.roles` allowlist:
|
|
1135
779
|
|
|
1136
780
|
```typescript
|
|
1137
781
|
masking: {
|
|
1138
782
|
email: {
|
|
1139
783
|
type: 'email',
|
|
1140
784
|
show: { roles: ['admin'] },
|
|
1141
|
-
query: { roles: ['admin'] }, //
|
|
785
|
+
query: { roles: ['admin'] }, // defaults to show.roles when omitted
|
|
1142
786
|
},
|
|
1143
787
|
}
|
|
1144
788
|
```
|
|
1145
789
|
|
|
1146
|
-
|
|
790
|
+
A view's own `query.{filterable,searchable,sortable}` allowlist is the opt-in for higher-privileged roles; the existing intersection validator gates it at compile time.
|
|
1147
791
|
|
|
1148
|
-
**Breaking:**
|
|
792
|
+
**Breaking:** `masking[col].filterable / .searchable / .sortable` is rejected at compile time with a migration hint. Replace with `query.roles` (or delete the flags — `query` defaults to `show.roles`).
|
|
1149
793
|
|
|
1150
794
|
---
|
|
1151
795
|
|
|
1152
796
|
## v0.9.0 — April 25, 2026
|
|
1153
797
|
|
|
1154
|
-
###
|
|
798
|
+
### Unified `read:` pipeline
|
|
1155
799
|
|
|
1156
|
-
|
|
1157
|
-
side of every resource now has its own block — `read:` — that owns the
|
|
1158
|
-
collection-level `GET /` endpoint, single-record `GET /:id`, and named view
|
|
1159
|
-
projections. The legacy `crud.list` and `crud.get` shapes are rejected at
|
|
1160
|
-
compile time. See the new [Read pipeline](/compiler/definitions/read) page
|
|
1161
|
-
for the full reference and migration table.
|
|
800
|
+
The read side of every resource has its own block — `read:` — that owns the collection-level `GET /` endpoint, single-record `GET /:id`, and named view projections.
|
|
1162
801
|
|
|
1163
802
|
**Breaking changes** (compile-time errors with migration hints):
|
|
1164
803
|
|
|
1165
|
-
- `crud.list` →
|
|
1166
|
-
- `crud.get` → `read.access` (single-record GET inherits automatically
|
|
1167
|
-
- Top-level `views: {...}` →
|
|
804
|
+
- `crud.list` → `read.access` (plus `read.pageSize` / `read.maxPageSize`)
|
|
805
|
+
- `crud.get` → `read.access` (single-record GET inherits automatically)
|
|
806
|
+
- Top-level `views: {...}` → `read.views: {...}`
|
|
1168
807
|
- `crud.list.fields` / `crud.get.fields` → declare a named view under `read.views` and call `/views/{name}`
|
|
1169
808
|
|
|
1170
|
-
|
|
1171
|
-
access check **before** the firewall query, so a caller without a matching
|
|
1172
|
-
role gets 403 before the database is touched. This closes the 404-vs-403
|
|
1173
|
-
ID-probe channel — an unauthorized caller can no longer distinguish "row
|
|
1174
|
-
exists in another tenant" from "row doesn't exist." See
|
|
1175
|
-
[Access evaluation order](/compiler/definitions/access#evaluation-order).
|
|
1176
|
-
|
|
1177
|
-
**Transactional batch operations**: batch endpoints now expose a
|
|
1178
|
-
`failFast` option (replacing the old `atomic` naming) and a
|
|
1179
|
-
`meta.transactional` response field. On tx-supporting providers
|
|
1180
|
-
(postgres, supabase, neon, libsql, better-sqlite3, bun-sqlite), `failFast: true`
|
|
1181
|
-
wraps the per-record loop in `db.transaction(...)` so any failure rolls
|
|
1182
|
-
back the entire batch. On Cloudflare D1 (no `db.transaction`), `failFast: true`
|
|
1183
|
-
still stops on the first error but prior writes stay committed; inspect
|
|
1184
|
-
`meta.transactional` to know which guarantee you got. Embedding queue
|
|
1185
|
-
messages and realtime broadcasts are emitted **after** the transaction
|
|
1186
|
-
commits, so a rolled-back batch produces no orphan jobs. See
|
|
1187
|
-
[Batch Operations: Transactional semantics](/compiler/targets/hono-api/using-the-api/batch-operations#transactional-semantics).
|
|
1188
|
-
|
|
1189
|
-
**`firewallErrorMode` lifted off the firewall block**: the field that
|
|
1190
|
-
controls 403-vs-404 on firewall misses now lives at the resource top level
|
|
1191
|
-
(sibling to `firewall:`), since the firewall config is now a predicate
|
|
1192
|
-
array and this is a presentation-layer choice. Existing `firewall.errorMode`
|
|
1193
|
-
values should be lifted to `firewallErrorMode` at the resource level.
|
|
1194
|
-
|
|
1195
|
-
**Read-only resources**: an empty `crud: {}` block (or omitting `crud:`
|
|
1196
|
-
entirely) is valid for read-only resources. `read:` alone is enough to
|
|
1197
|
-
expose `GET /` and `GET /:id`.
|
|
1198
|
-
|
|
1199
|
-
**Strict-mode top-level keys**: the strict allow-list now includes `dev` so
|
|
1200
|
-
`defineConfig({ dev: { ... } })` is accepted at the top level.
|
|
1201
|
-
|
|
1202
|
-
---
|
|
1203
|
-
|
|
1204
|
-
## v0.8.7 — April 17, 2026
|
|
809
|
+
### Pre-record access ordering
|
|
1205
810
|
|
|
1206
|
-
|
|
811
|
+
Handlers on `/:id` run a role-only access check before the firewall query. A caller without a matching role gets 403 before the database is touched. This closes the 404-vs-403 ID-probe channel — an unauthorized caller can no longer distinguish "row exists in another tenant" from "row doesn't exist." See [Access evaluation order](/compiler/definitions/access#evaluation-order).
|
|
1207
812
|
|
|
1208
|
-
|
|
813
|
+
### Transactional batch operations
|
|
1209
814
|
|
|
1210
|
-
|
|
815
|
+
Batch endpoints expose `failFast` and a `meta.transactional` response field. On tx-supporting providers (postgres, supabase, neon, libsql, better-sqlite3, bun-sqlite), `failFast: true` wraps the per-record loop in `db.transaction(...)` so any failure rolls back the entire batch. On Cloudflare D1 (no `db.transaction`), `failFast: true` stops on the first error but prior writes stay committed.
|
|
1211
816
|
|
|
1212
|
-
|
|
817
|
+
Embedding queue messages and realtime broadcasts emit after the transaction commits — rolled-back batches produce no orphan jobs.
|
|
1213
818
|
|
|
1214
|
-
|
|
1215
|
-
|
|
1216
|
-
Aligned the whole dep surface — monorepo, compiler Docker image, and generator emissions into compiled projects — so new compiles and existing recompiles converge on the same versions:
|
|
1217
|
-
|
|
1218
|
-
- `wrangler@^4.83.0`
|
|
1219
|
-
- `drizzle-orm@^0.45.2`, `drizzle-kit@^0.31.10`
|
|
1220
|
-
- `zod@^4.3.6`
|
|
1221
|
-
- `@cloudflare/workers-types@^4.20260417.1` (also deduped — was accidentally declared in both `dependencies` and `devDependencies` in some paths)
|
|
1222
|
-
- `@tanstack/react-query@^5.99.0` (Account app)
|
|
819
|
+
See [Batch Operations → Transactional semantics](/compiler/targets/hono-api/using-the-api/batch-operations#transactional-semantics).
|
|
1223
820
|
|
|
1224
821
|
---
|
|
1225
822
|
|
|
1226
|
-
## v0.8.
|
|
1227
|
-
|
|
1228
|
-
### Fix: Better Auth 1.5 and `@cloudflare/workers-types` Compatibility
|
|
823
|
+
## v0.8.7 — April 17, 2026
|
|
1229
824
|
|
|
1230
|
-
|
|
825
|
+
### Hono CVE bump
|
|
1231
826
|
|
|
1232
|
-
|
|
1233
|
-
- **`REALTIME_URL` and `ACCESS_TOKEN`** are always emitted as optional `CloudflareBindings` fields when the organization plugin is active, so the broadcast hook typechecks even when `realtimeMode` is `"inline"` (or realtime isn't configured at all).
|
|
1234
|
-
- **`auth.api.listOrganizations` / `getFullOrganization` / `session.session.activeOrganizationId`** — third-party Better Auth plugins narrow the inferred `auth.api` type and hide organization-plugin endpoints. The generated middleware and `/admin/v1/organizations` route now cast through `any` for these calls.
|
|
1235
|
-
- **`crypto.subtle.sign` / `verify`** no longer accept `Uint8Array<ArrayBufferLike>` directly. Generated `jwt.ts` casts encoded payloads to `BufferSource`.
|
|
827
|
+
Hono is bumped to `^4.12.14` across the monorepo, the compiler Docker image's pre-installed deps, and every generator path that emits Hono into compiled projects. Older ranges covered the vulnerable window. Recompile to pick up the fix in your generated project's `package.json`.
|
|
1236
828
|
|
|
1237
|
-
|
|
829
|
+
### Cloudflare Email Sending in public beta
|
|
1238
830
|
|
|
1239
|
-
|
|
831
|
+
Quickback defaults to the Workers `send_email` binding for Cloudflare deploys. Cloudflare Email Sending has graduated to public beta — production-ready with zero-config. AWS SES remains a fully supported opt-in (`email.provider: 'aws-ses'`) for non-Cloudflare runtimes. See [Email Configuration](/compiler/config#email-configuration).
|
|
1240
832
|
|
|
1241
|
-
|
|
833
|
+
### Dependency sweep
|
|
1242
834
|
|
|
1243
|
-
|
|
835
|
+
`wrangler@^4.83.0`, `drizzle-orm@^0.45.2`, `drizzle-kit@^0.31.10`, `zod@^4.3.6`, `@cloudflare/workers-types@^4.20260417.1`.
|
|
1244
836
|
|
|
1245
|
-
|
|
1246
|
-
- **`/api/v1/schema`** — returns `403` to non-admins.
|
|
1247
|
-
- **`custom_view` CRUD** — now gated on the new `userRole: ["admin"]` primitive rather than org membership.
|
|
1248
|
-
- **In-SPA gate** — unchanged; defense in depth behind the server-side gates.
|
|
837
|
+
---
|
|
1249
838
|
|
|
1250
|
-
|
|
839
|
+
## v0.8.5 — April 15, 2026
|
|
1251
840
|
|
|
1252
|
-
###
|
|
841
|
+
### `userRole` access primitive
|
|
1253
842
|
|
|
1254
|
-
|
|
843
|
+
A new `userRole?: string[]` field in the declarative `Access` config evaluates against `ctx.userRole` (the Better Auth admin-plugin `user.role` column). Distinct from `roles`, which matches `ctx.roles` (org membership).
|
|
1255
844
|
|
|
1256
845
|
```typescript
|
|
1257
|
-
//
|
|
1258
|
-
access: { roles: ['admin'] }
|
|
1259
|
-
|
|
1260
|
-
// New: explicitly require user.role === 'admin' regardless of org membership
|
|
1261
|
-
access: { userRole: ['admin'] }
|
|
1262
|
-
|
|
1263
|
-
// "Org owner OR platform admin"
|
|
846
|
+
// Org owner OR platform admin
|
|
1264
847
|
access: { or: [{ roles: ['owner'] }, { userRole: ['admin'] }] }
|
|
1265
848
|
|
|
1266
849
|
// Platform admins see SSNs across every org
|
|
1267
850
|
masking: { ssn: { type: 'ssn', show: { userRole: ['admin'] } } }
|
|
1268
851
|
```
|
|
1269
852
|
|
|
1270
|
-
`userRole` works everywhere `Access` is accepted — CRUD, actions, views, masking, and inside `or
|
|
1271
|
-
|
|
1272
|
-
### Fix: `ReferenceError: customAlphabet is not defined` in generated POST handlers
|
|
1273
|
-
|
|
1274
|
-
Projects with `providers.database.config.generateId: "short"` (or `"nanoid"` / `"cuid"`) compiled routes that called the ID helper but never imported it. Every generated `src/features/**/*.routes.ts` had `customAlphabet('0123...', 6)()` in its POST body but no matching `import { customAlphabet } from 'nanoid';` at the top of the file. Every `POST /api/v1/<resource>` and batch-create returned `500` with `ReferenceError: customAlphabet is not defined` on the first write.
|
|
1275
|
-
|
|
1276
|
-
The compiler now emits the correct import alongside the ID expression for all three modes: `nanoid`, `customAlphabet`, and `createId` from `@paralleldrive/cuid2`.
|
|
1277
|
-
|
|
1278
|
-
No config changes required — recompile to pick up the fix.
|
|
1279
|
-
|
|
1280
|
-
### Fix: Dangling `export const` in generated `actions.ts` breaks `tsc`
|
|
1281
|
-
|
|
1282
|
-
When a feature authored actions as `export const xActions = defineActions(...)` (instead of `export default defineActions(...)`), the compiler's preamble extractor leaked the assignment's left-hand side into the generated `src/features/<feature>/actions.ts`. The output contained a dangling `export const xActions =` with no right-hand side, and `tsc --noEmit` failed with `TS1109: Expression expected`. Runtime happened to work because the unused placeholder was never evaluated, but typecheck was red.
|
|
1283
|
-
|
|
1284
|
-
The preamble extractor now anchors its boundary to the start of the top-level statement containing `defineActions(...)`, covering `export default`, `export const X =`, `const X =`, and bare call forms. Local Zod helper declarations above the call continue to be preserved.
|
|
1285
|
-
|
|
1286
|
-
### Fix: Files worker `database_id` reverted to `"local-files"` on every compile
|
|
1287
|
-
|
|
1288
|
-
Projects using the two-worker R2 architecture had their files worker's `wrangler.toml` (`apps/backend/cloudflare-workers/files/wrangler.toml`) rewritten with `database_id = "local-files"` on every `quickback compile`, even when `providers.database.config.filesDatabaseId` was set to a real D1 UUID. The main worker's binding was correct — only the files worker fell through. Remote deploys of the files worker bound to a non-existent D1, so file serving and access-control reads failed with a binding error.
|
|
1289
|
-
|
|
1290
|
-
The files-worker wrangler generator now reads `filesDatabaseId` (and `filesDatabaseName`) from `providers.database.config` as a fallback when they aren't set on `providers.fileStorage.config`, matching the precedence chain already used by the main worker. Local dev is unaffected — `wrangler dev --local` uses `.wrangler/state/` regardless of the configured ID.
|
|
1291
|
-
|
|
1292
|
-
No config changes required — recompile and redeploy the files worker.
|
|
1293
|
-
|
|
1294
|
-
---
|
|
1295
|
-
|
|
1296
|
-
## v0.8.6 — April 16, 2026
|
|
1297
|
-
|
|
1298
|
-
### Fix: Audit columns silently dropped from tables with a same-line index callback
|
|
1299
|
-
|
|
1300
|
-
Tables authored with the composite-index shape Drizzle / prettier produces —
|
|
1301
|
-
|
|
1302
|
-
```ts
|
|
1303
|
-
export const episodeTags = sqliteTable("episode_tags", {
|
|
1304
|
-
id: text("id").primaryKey(),
|
|
1305
|
-
episodeId: text("episode_id").notNull(),
|
|
1306
|
-
tagId: text("tag_id").notNull(),
|
|
1307
|
-
}, (t) => [ // <-- "}, (t) =>" on one line
|
|
1308
|
-
uniqueIndex("episode_tag_unique").on(t.episodeId, t.tagId),
|
|
1309
|
-
]);
|
|
1310
|
-
```
|
|
1311
|
-
|
|
1312
|
-
never received audit field injection. A regex in `injectAuditFields` required a literal `\n` between the columns-object `},` and the `(t) =>` index callback, so same-line closers were silently skipped and the function returned the source unchanged. drizzle-kit then diffed the audit-less schema against the previous snapshot and emitted `ALTER TABLE ... DROP COLUMN created_at/modified_at/deleted_at/created_by/modified_by/deleted_by` for every affected table. Any project that applied those migrations had production CRUD return `500` because the generated firewall helper still referenced `deletedAt`.
|
|
1313
|
-
|
|
1314
|
-
The regex is now whitespace-flexible and the identifier class accepts any valid JS identifier (`t`, `table`, `_t`, `tbl2`). A defensive guard throws at compile time if all three terminator patterns fail on a recognizable Drizzle table — no more silent drops.
|
|
853
|
+
`userRole` works everywhere `Access` is accepted — CRUD, actions, views, masking, and inside `or` / `and` combinators. See [Access → userRole vs roles](/compiler/definitions/access#userrole-vs-roles).
|
|
1315
854
|
|
|
1316
|
-
|
|
855
|
+
### CMS admin gate enforced server-side
|
|
1317
856
|
|
|
1318
|
-
|
|
1319
|
-
- Projects that already hand-patched their schema and ran a manual `ADD COLUMN` migration (like the `podcast-app` workaround in commit `98d8758`): the next compile will regenerate a matching `ADD COLUMN` migration that will fail with "duplicate column name" against a DB that already has the columns. Mark the new migration as applied without running it (e.g. `INSERT INTO __drizzle_migrations` in the features DB) or hand-edit the generated SQL to a no-op, then continue normally.
|
|
857
|
+
`cms: { access: "admin" }` previously only hid the CMS link in Account UI and rendered an "Access Denied" screen inside the SPA. Server-side enforcement now applies at every CMS-facing surface: the SPA shell, `/api/v1/schema`, and `custom_view` CRUD.
|
|
1320
858
|
|
|
1321
|
-
###
|
|
859
|
+
### Better Auth 1.5 + `@cloudflare/workers-types` compatibility
|
|
1322
860
|
|
|
1323
|
-
|
|
1324
|
-
|
|
1325
|
-
The three concerns are now fully independent:
|
|
1326
|
-
|
|
1327
|
-
- **`firewall.exception: true`** — only disables tenant scoping (org/user/team `WHERE` clauses). It does not gate audit fields or soft-delete.
|
|
1328
|
-
- **Audit fields** — always injected unless globally opted out. Unchanged.
|
|
1329
|
-
- **Soft-delete filter** — emitted only when the schema actually has `deletedAt` *or* the user explicitly set `firewall.softDelete`.
|
|
1330
|
-
|
|
1331
|
-
In the default configuration (audit injection on), behavior is unchanged: exception resources still filter `deletedAt IS NULL`. Only the broken case changes — exception resources on a schema without `deletedAt` now return `undefined` (no firewall), matching the column reality.
|
|
1332
|
-
|
|
1333
|
-
No config changes required — recompile to pick up the fix.
|
|
861
|
+
Generated API code typechecks against the new versions. The org-member role-change broadcast hook is emitted via `organizationHooks.afterUpdateMemberRole` (the supported shape after the 1.5 deprecation of `databaseHooks.member.update.after`). `REALTIME_URL` and `ACCESS_TOKEN` are always emitted as optional bindings when the organization plugin is active.
|
|
1334
862
|
|
|
1335
863
|
---
|
|
1336
864
|
|
|
1337
865
|
## v0.8.4 — April 14, 2026
|
|
1338
866
|
|
|
1339
|
-
###
|
|
867
|
+
### `generateId: "short"` strategy
|
|
1340
868
|
|
|
1341
|
-
|
|
869
|
+
A compact ID option for tables where short, shareable codes matter more than collision resistance at scale:
|
|
1342
870
|
|
|
1343
871
|
```typescript
|
|
1344
872
|
providers: {
|
|
1345
|
-
database: defineDatabase("cloudflare-d1", {
|
|
1346
|
-
generateId: "short",
|
|
1347
|
-
}),
|
|
873
|
+
database: defineDatabase("cloudflare-d1", { generateId: "short" }),
|
|
1348
874
|
}
|
|
1349
875
|
```
|
|
1350
876
|
|
|
1351
|
-
Generates 6-character alphanumeric IDs (e.g. `a3F9xK`) using nanoid's `customAlphabet` with the full 62-char alphabet (`0-9A-Za-z`). Requires the `nanoid` package
|
|
877
|
+
Generates 6-character alphanumeric IDs (e.g. `a3F9xK`) using nanoid's `customAlphabet` with the full 62-char alphabet (`0-9A-Za-z`). Requires the `nanoid` package.
|
|
1352
878
|
|
|
1353
|
-
**When to use:** room codes, invite links, share URLs, ephemeral records
|
|
879
|
+
**When to use:** room codes, invite links, share URLs, ephemeral records.
|
|
1354
880
|
|
|
1355
|
-
**When not to use:** high-volume tables. 62^6 ≈ 56.8B combinations means ~238K rows before a 50% collision probability
|
|
1356
|
-
|
|
1357
|
-
See [Providers - ID Generation Options](/compiler/config/providers#id-generation-options) for the full list of strategies.
|
|
1358
|
-
|
|
1359
|
-
---
|
|
1360
|
-
|
|
1361
|
-
## v0.8.3 — April 14, 2026
|
|
1362
|
-
|
|
1363
|
-
### Fix: `wrangler.toml` Route Placement and Binding IDs
|
|
1364
|
-
|
|
1365
|
-
Two bugs in the generated `wrangler.toml` that blocked production deployment without manual edits:
|
|
1366
|
-
|
|
1367
|
-
**Routes were nested under `[dev]`.** The `routes = [...]` array was emitted after the `[dev]` section header, so TOML parsed it as `dev.routes` and wrangler ignored the custom domain (warning: `Unexpected fields found in dev field: "routes"`). Routes now emit as a top-level key.
|
|
1368
|
-
|
|
1369
|
-
**D1 and KV bindings used placeholder IDs.** Despite `databaseId`, `filesDatabaseId`, and `kvId` being set in the quickback config, the generated `wrangler.toml` wrote `"local-features"`, `"local-files"`, and `"local"` instead of the real UUIDs. The compiler now resolves IDs from multiple config sources:
|
|
1370
|
-
|
|
1371
|
-
| Binding | Config sources checked (in order) |
|
|
1372
|
-
|---------|-----------------------------------|
|
|
1373
|
-
| `AUTH_DB` | `database.config.authDatabaseId` |
|
|
1374
|
-
| `DB` | `database.config.featuresDatabaseId`, `database.config.databaseId` |
|
|
1375
|
-
| `FILES_DB` | `fileStorage.config.filesDatabaseId`, `database.config.filesDatabaseId` |
|
|
1376
|
-
| `KV` | `database.config.kvNamespaceId`, `storage.config.namespaceId`, `auth.config.kvId` |
|
|
1377
|
-
|
|
1378
|
-
See [Providers - Database Options](/compiler/config/providers#database-options) for the full list of supported ID properties.
|
|
1379
|
-
|
|
1380
|
-
### Fix: Account SPA Post-Login Redirect on Unified Domain
|
|
1381
|
-
|
|
1382
|
-
When the Account SPA was served at `/account/` on the unified quickback domain (e.g. `secure.example.com/account/`), post-login redirects dropped the basepath and sent users to `/dashboard` instead of `/account/dashboard`. Sign-out redirects had the same issue.
|
|
1383
|
-
|
|
1384
|
-
The SPA now shares a basepath module across the router and all raw `window.location.href` assignments, so login, signup, email OTP, welcome, and sign-out flows all stay under the correct path prefix regardless of whether the SPA is on the unified domain or its own dedicated auth subdomain.
|
|
1385
|
-
|
|
1386
|
-
No config changes required — recompile to pick up the fix.
|
|
881
|
+
**When not to use:** high-volume tables. 62^6 ≈ 56.8B combinations means ~238K rows before a 50% collision probability. For large tables stick with `"uuid"`, `"cuid"`, or `"prefixed"`. See [Providers → ID Generation Options](/compiler/config/providers#id-generation-options).
|
|
1387
882
|
|
|
1388
883
|
---
|
|
1389
884
|
|
|
1390
885
|
## v0.8.2 — April 11, 2026
|
|
1391
886
|
|
|
1392
|
-
### Catch-
|
|
887
|
+
### Catch-all `VITE_QUICKBACK_URL`
|
|
1393
888
|
|
|
1394
|
-
|
|
889
|
+
A single Quickback origin can be set in place of four separate URL env vars:
|
|
1395
890
|
|
|
1396
891
|
```bash
|
|
1397
|
-
# One variable — done.
|
|
1398
892
|
VITE_QUICKBACK_URL=https://secure.example.com
|
|
1399
893
|
```
|
|
1400
894
|
|
|
1401
|
-
When set, it's used as a fallback for the individual URLs:
|
|
1402
|
-
|
|
1403
895
|
| Individual var (explicit) | Fallback when unset |
|
|
1404
896
|
|---|---|
|
|
1405
897
|
| `VITE_QUICKBACK_API_URL` | `${VITE_QUICKBACK_URL}` |
|
|
1406
898
|
| `VITE_QUICKBACK_ACCOUNT_URL` | `${VITE_QUICKBACK_URL}/account` |
|
|
1407
899
|
| `VITE_QUICKBACK_CMS_URL` | `${VITE_QUICKBACK_URL}/cms` |
|
|
1408
900
|
|
|
1409
|
-
`VITE_QUICKBACK_APP_URL` stays independent — it points at the tenant's own frontend
|
|
1410
|
-
|
|
1411
|
-
**Non-breaking.** Individual vars still take precedence when set, so existing configurations work unchanged. The compiler now also emits `VITE_QUICKBACK_URL` into the generated SPA `.env` files, and library users can set `__QUICKBACK_URL__` on `globalThis` for the same effect.
|
|
1412
|
-
|
|
1413
|
-
See [Environment Variables](/stack/account-ui/environment-variables) for the full reference.
|
|
901
|
+
`VITE_QUICKBACK_APP_URL` stays independent — it points at the tenant's own frontend. Non-breaking; individual vars take precedence when set. Library users can set `__QUICKBACK_URL__` on `globalThis`. See [Environment Variables](/stack/account-ui/environment-variables).
|
|
1414
902
|
|
|
1415
903
|
---
|
|
1416
904
|
|
|
1417
905
|
## v0.8.1 — April 9, 2026
|
|
1418
906
|
|
|
1419
|
-
### Role
|
|
907
|
+
### Role hierarchy with `+` suffix
|
|
1420
908
|
|
|
1421
|
-
|
|
909
|
+
Define a hierarchy and use `+` to mean "this role and above":
|
|
1422
910
|
|
|
1423
911
|
```typescript
|
|
1424
|
-
|
|
1425
|
-
auth: {
|
|
1426
|
-
roleHierarchy: ['member', 'admin', 'owner'],
|
|
1427
|
-
}
|
|
912
|
+
auth: { roleHierarchy: ['member', 'admin', 'owner'] }
|
|
1428
913
|
|
|
1429
|
-
// In resource definitions
|
|
1430
914
|
crud: {
|
|
1431
915
|
list: { access: { roles: ["member+"] } }, // member, admin, owner
|
|
1432
916
|
create: { access: { roles: ["admin+"] } }, // admin, owner
|
|
@@ -1434,15 +918,15 @@ crud: {
|
|
|
1434
918
|
}
|
|
1435
919
|
```
|
|
1436
920
|
|
|
1437
|
-
Roles are expanded at compile time. No `+` = exact match. See [Access
|
|
921
|
+
Roles are expanded at compile time. No `+` = exact match. See [Access → Role Hierarchy](/compiler/definitions/access#role-hierarchy).
|
|
1438
922
|
|
|
1439
923
|
---
|
|
1440
924
|
|
|
1441
925
|
## v0.8.0 — April 9, 2026
|
|
1442
926
|
|
|
1443
|
-
### Breaking: VITE URL
|
|
927
|
+
### Breaking: VITE URL environment variables namespaced
|
|
1444
928
|
|
|
1445
|
-
All Quickback-generated URL environment variables are
|
|
929
|
+
All Quickback-generated URL environment variables are namespaced under `VITE_QUICKBACK_*` to avoid collisions with other Vite projects.
|
|
1446
930
|
|
|
1447
931
|
| Old | New |
|
|
1448
932
|
|-----|-----|
|
|
@@ -1451,129 +935,58 @@ All Quickback-generated URL environment variables are now namespaced under `VITE
|
|
|
1451
935
|
| `VITE_APP_URL` | `VITE_QUICKBACK_APP_URL` |
|
|
1452
936
|
| `VITE_CMS_URL` | `VITE_QUICKBACK_CMS_URL` |
|
|
1453
937
|
|
|
1454
|
-
|
|
938
|
+
Non-URL variables are unchanged (`VITE_ENABLE_*`, branding vars, `VITE_STRIPE_PUBLISHABLE_KEY`).
|
|
1455
939
|
|
|
1456
940
|
**Action required:**
|
|
1457
|
-
-
|
|
1458
|
-
-
|
|
1459
|
-
-
|
|
1460
|
-
|
|
1461
|
-
See [Environment Variables](/stack/account-ui/environment-variables) for the full reference.
|
|
1462
|
-
|
|
1463
|
-
### CMS Access Control
|
|
1464
|
-
|
|
1465
|
-
The `cms.access` config option now enforces access at the CMS level, not just link visibility in Account UI.
|
|
1466
|
-
|
|
1467
|
-
```typescript
|
|
1468
|
-
cms: { access: "admin" }
|
|
1469
|
-
```
|
|
1470
|
-
|
|
1471
|
-
When set to `"admin"`, non-admin users (`user.role !== "admin"`) see an "Access Denied" screen with a sign-out button instead of the CMS. When set to `"user"` (the default), any authenticated user can access the CMS.
|
|
941
|
+
- Compiled projects: re-run `quickback compile`.
|
|
942
|
+
- Standalone deploys: update `.env`, `.env.production`, and `wrangler.toml` files manually.
|
|
943
|
+
- Library users: `__QUICKBACK_API_URL__` / `__QUICKBACK_APP_URL__` globals are unchanged.
|
|
1472
944
|
|
|
1473
|
-
|
|
945
|
+
### CMS access control
|
|
1474
946
|
|
|
1475
|
-
|
|
1476
|
-
|
|
1477
|
-
Fixed a bug where hard-refreshing or directly navigating to SPA sub-routes (e.g., `/account/profile`, `/cms/tables/users`) returned a blank white screen. The Worker now correctly serves `index.html` for all SPA paths, allowing the client-side router to handle routing.
|
|
947
|
+
`cms.access: "admin"` enforces access at the CMS level, not just link visibility. Non-admin users (`user.role !== "admin"`) see an "Access Denied" screen with a sign-out button.
|
|
1478
948
|
|
|
1479
949
|
---
|
|
1480
950
|
|
|
1481
951
|
## v0.5.11 — February 24, 2026
|
|
1482
952
|
|
|
1483
|
-
###
|
|
1484
|
-
|
|
1485
|
-
- Fixed email-OTP magic links not working correctly
|
|
1486
|
-
- Removed deprecated `/internal/validate` endpoint — use standard Better Auth session validation instead
|
|
1487
|
-
- Auth is now required for all API routes when running locally (previously some routes were unprotected in dev)
|
|
1488
|
-
|
|
1489
|
-
### Multiple Table Exports Fix
|
|
1490
|
-
|
|
1491
|
-
- Fixed a compiler error when a single file exports multiple Drizzle tables alongside a `defineTable()` default export
|
|
1492
|
-
- The CLI now properly detects and reports this with a clear error message pointing to the fix
|
|
1493
|
-
|
|
1494
|
-
### Headless Drizzle Rename Hints
|
|
953
|
+
### Mandatory unsafe action audit trail
|
|
1495
954
|
|
|
1496
|
-
-
|
|
1497
|
-
- Compile errors now include explicit rename key paths and fail fast on malformed rename config keys
|
|
1498
|
-
- See [Configuration](/compiler/config) for details
|
|
955
|
+
Structured `unsafe` config (`unsafe: { reason, adminOnly, crossTenant, targetScope }`). Cross-tenant unsafe actions require Better Auth authentication plus platform admin role (`ctx.userRole === "admin"`). Mandatory audit logging on success, denial, and error paths. Cloudflare output includes `AUDIT_DB` wiring, `drizzle.audit.config.ts`, and `db:migrate:audit:*` scripts when unsafe actions are present.
|
|
1499
956
|
|
|
1500
|
-
|
|
957
|
+
Compile-time raw SQL guard for actions and handlers (`allowRawSql: true` required per action).
|
|
1501
958
|
|
|
1502
|
-
|
|
1503
|
-
- `reports/security-contracts.report.json`
|
|
1504
|
-
- `reports/security-contracts.report.sig.json`
|
|
1505
|
-
- Added config-driven signing controls:
|
|
1506
|
-
- `compiler.securityContracts.report.signature.enabled`
|
|
1507
|
-
- `compiler.securityContracts.report.signature.required`
|
|
1508
|
-
- `compiler.securityContracts.report.signature.key` / `keyEnv` / `keyId`
|
|
1509
|
-
- Missing required signing keys now fail loudly with explicit remediation guidance
|
|
1510
|
-
- Added strict config validation for report/signature paths and signing options
|
|
959
|
+
### Security contract report artifacts
|
|
1511
960
|
|
|
1512
|
-
|
|
961
|
+
Generated security contract artifacts: `reports/security-contracts.report.json`, `reports/security-contracts.report.sig.json`. Config-driven signing controls (`compiler.securityContracts.report.signature.*`). Missing required signing keys fail loudly with explicit remediation.
|
|
1513
962
|
|
|
1514
|
-
|
|
1515
|
-
- Cross-tenant unsafe actions now require Better Auth authentication plus platform admin role (`ctx.userRole === "admin"`)
|
|
1516
|
-
- Added mandatory audit logging for unsafe cross-tenant actions (success, denial, and error paths)
|
|
1517
|
-
- Cloudflare output now includes optional `AUDIT_DB` wiring, `drizzle.audit.config.ts`, and `db:migrate:audit:*` scripts when unsafe actions are present
|
|
1518
|
-
- Added compile-time raw SQL guard for actions and handlers (`allowRawSql: true` required per action)
|
|
963
|
+
### Headless Drizzle rename hints
|
|
1519
964
|
|
|
1520
|
-
|
|
1521
|
-
|
|
1522
|
-
## v0.5.10 — February 19, 2026
|
|
1523
|
-
|
|
1524
|
-
### Compiler Page Parsing & CLI Output
|
|
965
|
+
`compiler.migrations.renames` configuration for CI/CD environments where Drizzle's interactive rename prompts block compilation. See [Configuration](/compiler/config).
|
|
1525
966
|
|
|
1526
|
-
|
|
1527
|
-
- Better CLI output formatting during compilation
|
|
1528
|
-
- Added `apiPath` to schema registry for CMS integration
|
|
967
|
+
### Minor
|
|
1529
968
|
|
|
1530
|
-
|
|
1531
|
-
|
|
1532
|
-
-
|
|
1533
|
-
- API key authentication (`x-api-key` header) is now handled separately from session tokens (`Bearer` header)
|
|
1534
|
-
|
|
1535
|
-
---
|
|
1536
|
-
|
|
1537
|
-
## v0.5.9 — February 16, 2026
|
|
1538
|
-
|
|
1539
|
-
### CMS Pages & CLI Page Support
|
|
1540
|
-
|
|
1541
|
-
- Added `definePage()` support for CMS-managed pages
|
|
1542
|
-
- Auth middleware improvements for page routes
|
|
1543
|
-
- CLI now supports page definitions alongside table and action definitions
|
|
969
|
+
- Email OTP magic links work correctly.
|
|
970
|
+
- Auth is required for all API routes when running locally.
|
|
971
|
+
- Single-file multi-table exports alongside `defineTable()` produce a clear error.
|
|
1544
972
|
|
|
1545
973
|
---
|
|
1546
974
|
|
|
1547
975
|
## v0.5.8 — February 14, 2026
|
|
1548
976
|
|
|
1549
|
-
### CMS
|
|
1550
|
-
|
|
1551
|
-
- Introduced the Quickback CMS — a schema-driven admin panel that connects to your generated API
|
|
1552
|
-
- CMS namespace added to actions for admin-specific operations
|
|
1553
|
-
- Fixed `guard` → `access` naming inconsistency in CMS action definitions
|
|
1554
|
-
|
|
1555
|
-
### Schema Registry & Firewall Improvements
|
|
977
|
+
### Quickback CMS
|
|
1556
978
|
|
|
1557
|
-
-
|
|
1558
|
-
- Firewall error modes: choose between `reveal` (403 with details) and `hide` (opaque 404) for security-sensitive deployments
|
|
1559
|
-
|
|
1560
|
-
### Bug Fixes
|
|
1561
|
-
|
|
1562
|
-
- Fixed anonymous user email format generation
|
|
1563
|
-
- Organization selector improvements in Account UI
|
|
1564
|
-
- Config validation now catches more errors at compile time
|
|
1565
|
-
- Better CRUD error handling with structured error responses
|
|
1566
|
-
- Fixed masking to use representative star counts instead of fixed formatting
|
|
979
|
+
A schema-driven admin panel that connects to your generated API. The compiler now outputs a JSON schema registry consumed by the CMS at runtime. Firewall error modes (`reveal` for 403 with details, `hide` for opaque 404) are configurable per resource for security-sensitive deployments.
|
|
1567
980
|
|
|
1568
981
|
---
|
|
1569
982
|
|
|
1570
983
|
## v0.5.7 — February 12, 2026
|
|
1571
984
|
|
|
1572
|
-
### Scoped
|
|
985
|
+
### Scoped database for actions
|
|
1573
986
|
|
|
1574
|
-
Actions
|
|
987
|
+
Actions receive a security-scoped database instead of a raw Drizzle instance. The compiler generates a proxy wrapper that automatically enforces org isolation, owner filtering, and soft-delete visibility — the same protections that CRUD routes have always had.
|
|
1575
988
|
|
|
1576
|
-
|
|
989
|
+
Duck-typed column detection at runtime:
|
|
1577
990
|
|
|
1578
991
|
| Column Detected | SELECT / UPDATE / DELETE | INSERT |
|
|
1579
992
|
|---|---|---|
|
|
@@ -1581,24 +994,9 @@ The scoped DB uses duck-typed column detection at runtime:
|
|
|
1581
994
|
| `ownerId` | Adds `WHERE ownerId = ?` | Auto-injects `ownerId` from context |
|
|
1582
995
|
| `deletedAt` | Adds `WHERE deletedAt IS NULL` | — |
|
|
1583
996
|
|
|
1584
|
-
|
|
997
|
+
Every action is secure by default — no manual `WHERE` clauses needed.
|
|
1585
998
|
|
|
1586
|
-
|
|
1587
|
-
defineActions(todos, {
|
|
1588
|
-
complete: {
|
|
1589
|
-
type: "record",
|
|
1590
|
-
execute: async ({ db, ctx, record, input }) => {
|
|
1591
|
-
// db is scoped — only sees records in user's org, excludes soft-deleted
|
|
1592
|
-
const siblings = await db.select().from(todos);
|
|
1593
|
-
// ↑ automatically filtered to ctx.activeOrgId + deletedAt IS NULL
|
|
1594
|
-
},
|
|
1595
|
-
},
|
|
1596
|
-
});
|
|
1597
|
-
```
|
|
1598
|
-
|
|
1599
|
-
#### Unsafe Mode
|
|
1600
|
-
|
|
1601
|
-
Actions that intentionally need to bypass security (admin reports, cross-org queries, migrations) can declare `unsafe: true` to receive a raw, unscoped database handle:
|
|
999
|
+
Actions that intentionally need to bypass security (admin reports, cross-org queries, migrations) can declare `unsafe: true` to receive a raw, unscoped database handle via `rawDb`:
|
|
1602
1000
|
|
|
1603
1001
|
```typescript
|
|
1604
1002
|
defineActions(analytics, {
|
|
@@ -1613,108 +1011,45 @@ defineActions(analytics, {
|
|
|
1613
1011
|
});
|
|
1614
1012
|
```
|
|
1615
1013
|
|
|
1616
|
-
Without `unsafe: true`, `rawDb` is `undefined`.
|
|
1617
|
-
|
|
1618
|
-
**Related docs:** [Actions](/compiler/definitions/actions), [Actions API](/compiler/targets/hono-api/using-the-api/actions-api)
|
|
1014
|
+
Without `unsafe: true`, `rawDb` is `undefined`. See [Actions](/compiler/definitions/actions).
|
|
1619
1015
|
|
|
1620
|
-
|
|
1621
|
-
|
|
1622
|
-
### Cascading Soft Delete
|
|
1623
|
-
|
|
1624
|
-
Soft-deleting a parent record now **automatically cascades** to child and junction tables within the same feature. The compiler detects foreign key references at build time and generates cascade UPDATE statements.
|
|
1016
|
+
### Cascading soft delete
|
|
1625
1017
|
|
|
1626
|
-
|
|
1627
|
-
DELETE /api/v1/projects/:id
|
|
1628
|
-
```
|
|
1629
|
-
|
|
1630
|
-
Generated behavior:
|
|
1631
|
-
```typescript
|
|
1632
|
-
// 1. Soft delete the parent
|
|
1633
|
-
await db.update(projects)
|
|
1634
|
-
.set({ deletedAt: now, deletedBy: userId })
|
|
1635
|
-
.where(eq(projects.id, id));
|
|
1636
|
-
|
|
1637
|
-
// 2. Auto-cascade to children (compiler-generated)
|
|
1638
|
-
await db.update(projectMembers)
|
|
1639
|
-
.set({ deletedAt: now, deletedBy: userId })
|
|
1640
|
-
.where(eq(projectMembers.projectId, id));
|
|
1641
|
-
|
|
1642
|
-
await db.update(projectTasks)
|
|
1643
|
-
.set({ deletedAt: now, deletedBy: userId })
|
|
1644
|
-
.where(eq(projectTasks.projectId, id));
|
|
1645
|
-
```
|
|
1018
|
+
Soft-deleting a parent record automatically cascades to child and junction tables within the same feature. The compiler detects foreign key references at build time and generates cascade `UPDATE` statements.
|
|
1646
1019
|
|
|
1647
1020
|
Rules:
|
|
1648
|
-
-
|
|
1649
|
-
-
|
|
1650
|
-
- Child tables must have `deletedAt` / `deletedBy` columns (auto-added by the compiler
|
|
1021
|
+
- Applies to soft delete only. Hard delete relies on database-level `ON DELETE CASCADE`.
|
|
1022
|
+
- Cascades within the same feature only — cross-feature references are not affected.
|
|
1023
|
+
- Child tables must have `deletedAt` / `deletedBy` columns (auto-added by the compiler).
|
|
1651
1024
|
|
|
1652
|
-
|
|
1653
|
-
|
|
1654
|
-
---
|
|
1025
|
+
See [Actions API → Cascading Soft Delete](/compiler/targets/hono-api/using-the-api/actions-api#cascading-soft-delete).
|
|
1655
1026
|
|
|
1656
|
-
### Advanced
|
|
1027
|
+
### Advanced query parameters
|
|
1657
1028
|
|
|
1658
|
-
New
|
|
1029
|
+
New capabilities for all list endpoints:
|
|
1659
1030
|
|
|
1660
|
-
- **Field selection** — `?fields=id,name,status`
|
|
1661
|
-
- **Multi-sort** — `?sort=status:asc,createdAt:desc`
|
|
1662
|
-
- **Total count** — `?count=true` returns total matching records in
|
|
1031
|
+
- **Field selection** — `?fields=id,name,status`
|
|
1032
|
+
- **Multi-sort** — `?sort=status:asc,createdAt:desc`
|
|
1033
|
+
- **Total count** — `?count=true` returns total matching records in `X-Total-Count`
|
|
1663
1034
|
- **Full-text search** — `?search=keyword` searches across all text columns
|
|
1664
1035
|
|
|
1665
|
-
|
|
1666
|
-
# Get only names and statuses, sorted by status then date, with total count
|
|
1667
|
-
GET /api/v1/todos?fields=id,name,status&sort=status:asc,createdAt:desc&count=true
|
|
1668
|
-
|
|
1669
|
-
# Search across all text fields
|
|
1670
|
-
GET /api/v1/todos?search=urgent
|
|
1671
|
-
```
|
|
1672
|
-
|
|
1673
|
-
**Related docs:** [Query Parameters](/compiler/targets/hono-api/using-the-api/query-params)
|
|
1674
|
-
|
|
1675
|
-
---
|
|
1676
|
-
|
|
1677
|
-
### Audit Field Improvements
|
|
1678
|
-
|
|
1679
|
-
- `deletedAt` and `deletedBy` fields are now **always injected** by the compiler for tables with soft delete enabled — no need to define them in your schema
|
|
1680
|
-
- All audit fields (`createdAt`, `createdBy`, `modifiedAt`, `modifiedBy`, `deletedAt`, `deletedBy`) are auto-managed
|
|
1681
|
-
|
|
1682
|
-
---
|
|
1683
|
-
|
|
1684
|
-
## v0.5.6 — February 8, 2026
|
|
1685
|
-
|
|
1686
|
-
### Database Naming Conventions
|
|
1687
|
-
|
|
1688
|
-
- Default table and column naming changed to **snake_case** with `usePlurals: false`
|
|
1689
|
-
- Table names derived from generated Better Auth schema for consistency
|
|
1690
|
-
- Removed legacy single-database mode — split databases (auth + features) is now the standard
|
|
1691
|
-
|
|
1692
|
-
### Auth Variable Shadowing Fix
|
|
1693
|
-
|
|
1694
|
-
- Fixed `member` variable in auth middleware that shadowed the Drizzle `member` table import
|
|
1695
|
-
- Renamed to `sessionMember` to avoid conflicts in generated routes
|
|
1036
|
+
See [Query Parameters](/compiler/targets/hono-api/using-the-api/query-params).
|
|
1696
1037
|
|
|
1697
1038
|
---
|
|
1698
1039
|
|
|
1699
1040
|
## v0.5.5 — February 5, 2026
|
|
1700
1041
|
|
|
1701
|
-
###
|
|
1042
|
+
### OpenAPI spec generation
|
|
1702
1043
|
|
|
1703
|
-
|
|
1704
|
-
- Published `@quickback-dev/better-auth-combo-auth` — combined email + password + OTP authentication
|
|
1705
|
-
- Published `@quickback-dev/better-auth-aws-ses` — AWS SES email provider for Better Auth
|
|
1044
|
+
Generated APIs include a full OpenAPI specification at `/openapi.json`. Better Auth endpoints are included in the spec.
|
|
1706
1045
|
|
|
1707
|
-
###
|
|
1046
|
+
### Better Auth plugins
|
|
1708
1047
|
|
|
1709
|
-
-
|
|
1710
|
-
- Better Auth endpoints included in the spec
|
|
1711
|
-
- Runtime route: `GET /openapi.json`
|
|
1048
|
+
Published `@quickback-dev/better-auth-upgrade-anonymous` (post-passkey email collection flow), `@quickback-dev/better-auth-combo-auth` (combined email + password + OTP), and `@quickback-dev/better-auth-aws-ses` (AWS SES email provider).
|
|
1712
1049
|
|
|
1713
|
-
### Security
|
|
1050
|
+
### Security headers
|
|
1714
1051
|
|
|
1715
|
-
|
|
1716
|
-
- Security headers middleware (CSP, HSTS, X-Frame-Options, X-Content-Type-Options)
|
|
1717
|
-
- `BETTER_AUTH_SECRET` properly passed to generated config
|
|
1052
|
+
Global error handler prevents leaking internal error details. Security headers middleware (CSP, HSTS, X-Frame-Options, X-Content-Type-Options). `BETTER_AUTH_SECRET` properly passed to generated config.
|
|
1718
1053
|
|
|
1719
1054
|
---
|
|
1720
1055
|
|
|
@@ -1722,34 +1057,28 @@ GET /api/v1/todos?search=urgent
|
|
|
1722
1057
|
|
|
1723
1058
|
### Account UI
|
|
1724
1059
|
|
|
1725
|
-
|
|
1726
|
-
- Features: sessions, organizations, passkeys, passwordless, admin panel, API keys
|
|
1727
|
-
- Dual-mode: standalone (degit template) or embedded with Quickback projects
|
|
1060
|
+
Pre-built authentication UI deployed as Cloudflare Workers. Sessions, organizations, passkeys, passwordless, admin panel, API keys. Dual-mode: standalone (degit template) or embedded with Quickback projects.
|
|
1728
1061
|
|
|
1729
|
-
### Webhook
|
|
1062
|
+
### Webhook system
|
|
1730
1063
|
|
|
1731
|
-
|
|
1732
|
-
- Outbound webhooks via Cloudflare Queues with automatic retries
|
|
1733
|
-
- Configurable per-feature webhook events
|
|
1064
|
+
Inbound webhook endpoints with signature verification. Outbound webhooks via Cloudflare Queues with automatic retries. Configurable per-feature webhook events.
|
|
1734
1065
|
|
|
1735
|
-
### Realtime &
|
|
1066
|
+
### Realtime & vector search
|
|
1736
1067
|
|
|
1737
|
-
|
|
1738
|
-
- Vector embeddings via Cloudflare Vectorize
|
|
1739
|
-
- KV and R2 storage integrations
|
|
1068
|
+
Durable Objects + WebSocket realtime subscriptions. Vector embeddings via Cloudflare Vectorize. KV and R2 storage integrations.
|
|
1740
1069
|
|
|
1741
1070
|
---
|
|
1742
1071
|
|
|
1743
1072
|
## v0.5.0 — January 2026
|
|
1744
1073
|
|
|
1745
|
-
### Initial
|
|
1746
|
-
|
|
1747
|
-
- **Quickback Compiler** — TypeScript-first backend compiler
|
|
1748
|
-
- **Four
|
|
1749
|
-
- **`defineTable()`** —
|
|
1750
|
-
- **Templates** — Cloudflare Workers,
|
|
1751
|
-
- **Cloud
|
|
1752
|
-
- **CLI** — `quickback create`, `quickback compile
|
|
1753
|
-
- **Better Auth
|
|
1754
|
-
- **Drizzle ORM** —
|
|
1755
|
-
- **Cloudflare D1** —
|
|
1074
|
+
### Initial release
|
|
1075
|
+
|
|
1076
|
+
- **Quickback Compiler** — TypeScript-first backend compiler.
|
|
1077
|
+
- **Four security pillars** — Firewall, Access, Guards, Masking.
|
|
1078
|
+
- **`defineTable()`** — schema + security configuration in a single file.
|
|
1079
|
+
- **Templates** — Cloudflare Workers, B2B SaaS.
|
|
1080
|
+
- **Cloud compiler** — remote compilation via `compiler.quickback.dev`.
|
|
1081
|
+
- **CLI** — `quickback create`, `quickback compile`.
|
|
1082
|
+
- **Better Auth integration** — organizations, roles, sessions.
|
|
1083
|
+
- **Drizzle ORM** — schema-first with automatic migrations.
|
|
1084
|
+
- **Cloudflare D1** — split database support (auth + features).
|