@quickback-dev/cli 0.66.5 → 0.66.6

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.
Files changed (77) hide show
  1. package/README.md +0 -1
  2. package/dist/index.js +1 -1
  3. package/dist/skill/SKILL.md +0 -2
  4. package/dist/skill/docs/api/openapi.md +1 -1
  5. package/dist/skill/docs/configure/auth.md +4 -5
  6. package/dist/skill/docs/configure/domains.md +1 -1
  7. package/dist/skill/docs/configure/index.md +4 -4
  8. package/dist/skill/docs/configure/security.md +3 -3
  9. package/dist/skill/docs/define/access.md +23 -3
  10. package/dist/skill/docs/define/actions/defining.md +2 -2
  11. package/dist/skill/docs/define/actions/record-and-standalone.md +1 -2
  12. package/dist/skill/docs/define/areas.md +14 -15
  13. package/dist/skill/docs/define/changesets.md +5 -0
  14. package/dist/skill/docs/define/diagnostics.md +2 -2
  15. package/dist/skill/docs/define/fga.md +1 -1
  16. package/dist/skill/docs/define/firewall.md +5 -5
  17. package/dist/skill/docs/define/guards.md +2 -1
  18. package/dist/skill/docs/define/masking.md +2 -2
  19. package/dist/skill/docs/define/relationships.md +8 -10
  20. package/dist/skill/docs/define/scopes.md +1 -1
  21. package/dist/skill/docs/index.md +0 -6
  22. package/dist/skill/docs/platform/auth/jwt-optimization.md +2 -2
  23. package/dist/skill/docs/platform/realtime/durable-objects.md +1 -1
  24. package/dist/skill/docs/platform/realtime/partyserver-rooms.md +4 -4
  25. package/dist/skill/docs/platform/webhooks/inbound.md +1 -1
  26. package/dist/skill/docs/tooling/claude-skill.md +0 -7
  27. package/dist/skill/docs/tooling/cloud-compiler/endpoints.md +1 -1
  28. package/dist/skill/docs/tooling/output.md +7 -6
  29. package/dist/skill/docs/ui/account/features/admin.md +1 -1
  30. package/dist/skill/docs/ui/account/features/organizations.md +1 -1
  31. package/dist/skill/docs/ui/admin/index.md +1 -1
  32. package/dist/skill/docs/ui/admin/owned-records.md +81 -0
  33. package/dist/skill/docs/ui/admin/schema-format.md +16 -0
  34. package/package.json +1 -1
  35. package/src/skill/SKILL.md +0 -2
  36. package/src/skill/docs/api/openapi.md +1 -1
  37. package/src/skill/docs/configure/auth.md +4 -5
  38. package/src/skill/docs/configure/domains.md +1 -1
  39. package/src/skill/docs/configure/index.md +4 -4
  40. package/src/skill/docs/configure/security.md +3 -3
  41. package/src/skill/docs/define/access.md +23 -3
  42. package/src/skill/docs/define/actions/defining.md +2 -2
  43. package/src/skill/docs/define/actions/record-and-standalone.md +1 -2
  44. package/src/skill/docs/define/areas.md +14 -15
  45. package/src/skill/docs/define/changesets.md +5 -0
  46. package/src/skill/docs/define/diagnostics.md +2 -2
  47. package/src/skill/docs/define/fga.md +1 -1
  48. package/src/skill/docs/define/firewall.md +5 -5
  49. package/src/skill/docs/define/guards.md +2 -1
  50. package/src/skill/docs/define/masking.md +2 -2
  51. package/src/skill/docs/define/relationships.md +8 -10
  52. package/src/skill/docs/define/scopes.md +1 -1
  53. package/src/skill/docs/index.md +0 -6
  54. package/src/skill/docs/platform/auth/jwt-optimization.md +2 -2
  55. package/src/skill/docs/platform/realtime/durable-objects.md +1 -1
  56. package/src/skill/docs/platform/realtime/partyserver-rooms.md +4 -4
  57. package/src/skill/docs/platform/webhooks/inbound.md +1 -1
  58. package/src/skill/docs/tooling/claude-skill.md +0 -7
  59. package/src/skill/docs/tooling/cloud-compiler/endpoints.md +1 -1
  60. package/src/skill/docs/tooling/output.md +7 -6
  61. package/src/skill/docs/ui/account/features/admin.md +1 -1
  62. package/src/skill/docs/ui/account/features/organizations.md +1 -1
  63. package/src/skill/docs/ui/admin/index.md +1 -1
  64. package/src/skill/docs/ui/admin/owned-records.md +81 -0
  65. package/src/skill/docs/ui/admin/schema-format.md +16 -0
  66. package/dist/skill/docs/changelog/index.md +0 -945
  67. package/dist/skill/docs/changelog/v0.1x.md +0 -1202
  68. package/dist/skill/docs/changelog/v0.2x.md +0 -589
  69. package/dist/skill/docs/changelog/v0.3x.md +0 -1152
  70. package/dist/skill/docs/changelog/v0.4x.md +0 -1108
  71. package/dist/skill/docs/changelog/v0.5x.md +0 -885
  72. package/src/skill/docs/changelog/index.md +0 -945
  73. package/src/skill/docs/changelog/v0.1x.md +0 -1202
  74. package/src/skill/docs/changelog/v0.2x.md +0 -589
  75. package/src/skill/docs/changelog/v0.3x.md +0 -1152
  76. package/src/skill/docs/changelog/v0.4x.md +0 -1108
  77. package/src/skill/docs/changelog/v0.5x.md +0 -885
@@ -1,945 +0,0 @@
1
- # Changelog
2
-
3
- The current release series. Older entries are archived by version range:
4
-
5
- - [v0.50 – v0.54](/changelog/v0.5x)
6
- - [v0.40 – v0.48](/changelog/v0.4x)
7
- - [v0.32 – v0.39](/changelog/v0.3x)
8
- - [v0.20 – v0.29](/changelog/v0.2x)
9
- - [v0.18 and earlier](/changelog/v0.1x)
10
-
11
- ## Unreleased — delete rows reach after-write consumers
12
-
13
- - **Every delete statement now carries `.returning()`** ([#414](https://github.com/paulstenhouse/quickback-compiler/issues/414)). The single-record soft delete, the single-record hard delete, and the batch hard delete emitted no `RETURNING`, so on D1 the write result carried no rows and the audit-wrapper chokepoint had nothing to hand to its consumers: `afterDelete` trigger hooks never ran, live-view deltas were not emitted, and the scope-revocation and SEALED hard-delete audit-snapshot taps were skipped on those paths. Recompile to pick it up; response shapes are unchanged.
14
-
15
- ## Unreleased — scope enter tenant drop
16
-
17
- - **`/scope/v1/enter` mints a relationship-only token for a foreign-tenant instance** (follow-up to [#391](https://github.com/paulstenhouse/quickback-compiler/issues/391)). When the relationship's `from` table carries an organization column, the proven row's tenant is compared with `ctx.activeOrgId`; on a mismatch the token carries no `orgId` / `role`. Previously such a token was harmless (the tenant-bound firewall and resolver refused it) but still persisted the foreign org beside the scope. See [scopes](/define/scopes#per-matched-lane-minting-forging-safety).
18
- - **The shipped access evaluator and the compiler's reference copy are parity-tested** — `access-evaluator-parity.test.ts` runs both through one behavioural table (roles, principals, `userRole`, every `record:` condition, `or` / `and` nesting, collection predicates), so a fix that lands in one copy and not the other fails a test instead of drifting.
19
-
20
- ## Unreleased — access-evaluator hardening
21
-
22
- - **`access.record` is enforced on collection reads and batch-create** ([#394](https://github.com/paulstenhouse/quickback-compiler/issues/394)). `GET /`, per-view lists, and the MCP list tool fold each admitted arm's `record:` predicates into the query `WHERE`; `POST /batch` checks every input record the way single `POST` does. The `AUTHZ_RECORD_PREDICATE_NOT_ON_LIST` warning is retired because the list now honours the predicate. See [access](/define/access#collection-routes-honour-accessrecord-too).
23
- - **The access evaluator denies instead of throwing** ([#354](https://github.com/paulstenhouse/quickback-compiler/issues/354)). A `$ctx.` path with a missing intermediate resolves to undefined (403, not 500), and `equals` / `notEquals` deny when either side is absent instead of matching `undefined === undefined`.
24
- - **Function-form `read.access` is a compile error** ([#353](https://github.com/paulstenhouse/quickback-compiler/issues/353)) instead of emitting `const getAccess = undefined` into `GET /:id`.
25
- - **Dependency overrides land in the key your package manager reads** ([#359](https://github.com/paulstenhouse/quickback-compiler/issues/359)): `overrides` for npm and bun, `pnpm.overrides` for pnpm, `resolutions` for yarn — so the lodash security pin is no longer silently inert off npm.
26
- - **Top-level `rateLimit` is accepted by the config schema** ([#180](https://github.com/paulstenhouse/quickback-compiler/issues/180)); it was typed and consumed but rejected by the strict validator.
27
-
28
- ## Unreleased — tenant binding and credential hygiene
29
-
30
- Fixes from the attend-vip API security review. All are compiler changes;
31
- recompile to pick them up.
32
-
33
- - **Namespaces / scopes are tenant-bound** ([#391](https://github.com/paulstenhouse/quickback-compiler/issues/391)). A `{ roles }` / `{ team }` bulk-grant lane only applies when the hydrated instance belongs to `ctx.activeOrgId`; otherwise the caller falls through to the relationship lanes with no org roles. Inside an `any` firewall group with an org arm, scope / `via:` / permission arms are tenant-bound. Every mint (`/scope/v1/enter`, namespace `mintScope`, `/api/v1/token`) signs `orgId` only beside a membership `role`, the verifier ignores an unpaired `orgId`, and `POST /api/v1/token { dropOrg: true }` is a native privilege drop. See [scopes](/define/scopes#the-bulk-grant-lane-is-tenant-bound).
34
- - **Admin plugin honours the declared roles** ([#199](https://github.com/paulstenhouse/quickback-compiler/issues/199)). `plugins.admin.adminRoles` and `roles` are emitted verbatim; a narrowed `appmanager` stays narrowed, and an un-honourable declaration is a compile error.
35
- - **Better Auth rate limiting is durable on Workers** ([#404](https://github.com/paulstenhouse/quickback-compiler/issues/404)). `rateLimit.storage` defaults to `"database"` on Cloudflare (a `rateLimit` table is added — expect one migration), and every credential door (sign-up, password reset, email / phone OTP, magic link, two-factor, device flow) ships with a per-route rule; `customRules` merge on top. See [auth security](/platform/auth/security#rate-limiting).
36
- - **Presigned uploads enforce `maxFileSize` / `allowedTypes`** ([#405](https://github.com/paulstenhouse/quickback-compiler/issues/405)). `storage.signPutUrl` now requires `contentLength`; size and type are signed headers (`Content-Length`, `Content-Type`) the PUT must replay, and the declared limits are checked before a URL is minted. **Breaking for authored presign actions:** pass `contentLength`. See [using R2](/platform/storage/using-r2#presigned-uploads-with-ctxstorage).
37
- - **Auth catch blocks are generic in production** ([#406](https://github.com/paulstenhouse/quickback-compiler/issues/406)). `/auth/v1/*` and `/api/v1/token` 500s carry the underlying message only under `EXPOSE_ERROR_STACK`; the error-body redaction list now includes the compiler's own credential fields (`sessionToken`, `eventSessionToken`, `scopeJwt`, `wsTicket`, …).
38
- - **`openapi.publish` defaults to `'authenticated'` and gates every discovery surface** ([#407](https://github.com/paulstenhouse/quickback-compiler/issues/407)). `/openapi.json`, `/asyncapi.json`, `/docs`, `/llms.txt`, and `/.well-known/api-catalog` share one gate. **Breaking:** a project that relied on the anonymous default must set `publish: 'public'`. See [OpenAPI](/api/openapi#the-publish-gate).
39
- - **No shared `'default'` realtime room** ([#408](https://github.com/paulstenhouse/quickback-compiler/issues/408)). Org-less callers get a ticket bound to their own user room; org-less emits are skipped; a target naming no room is refused.
40
- - **`contract.redirects`** ([#409](https://github.com/paulstenhouse/quickback-compiler/issues/409)). Declarative same-origin path redirects (`/api/v2/*` → `/api/v1/*`, 308 by default), emitted right after the CORS mount so they survive every compile. See [API contract](/platform/api-contract#redirects--keep-answering-an-old-prefix).
41
-
42
- ## Unreleased — the standard API shape
43
-
44
- ### BREAKING: `contract.version` is retired
45
-
46
- There is one standard API shape, so there is nothing to select. Pinning
47
- `contract.version` is now a **compile error** on either value.
48
-
49
- **Delete that one line and keep `contract.routes` if you have it.** `routes`
50
- is the surviving axis and is what decides whether your URLs read `/api/v1` or
51
- `/api/v2` — removing it would move them.
52
-
53
- {/* doc-compile: skip — config fragment, not a compilable project */}
54
- ```typescript
55
- contract: { version: "v2", routes: "v1" } // before
56
- contract: { routes: "v1" } // after — same URLs, same behavior
57
- ```
58
-
59
- Deleting `version: "v2"` changes **no** behavior: it selected what is now
60
- simply the standard shape. Deleting `version: "v1"` is a real migration — see
61
- [the contract page](/platform/api-contract#contractversion-is-retired) for the
62
- four behaviors that pin opted out of, all now unconditional.
63
-
64
- ### BREAKING: CloudEvents `type` is reverse-DNS prefixed
65
-
66
- Realtime `postgres_changes` and `view_changes` frames now carry a
67
- `dev.quickback.` prefix on the CloudEvents `type`:
68
-
69
- ```
70
- myapp.registrations.insert → dev.quickback.myapp.registrations.insert
71
- myapp.view.agendaBoard.changed → dev.quickback.myapp.view.agendaBoard.changed
72
- ```
73
-
74
- **`qbframe` is the supported discriminator — do not match on `type`.** Its
75
- shape is not a stable contract; `qbframe` (`"broadcast"` / `"postgres_changes"`
76
- / `"view_changes"`) is. A client switching on `type` breaks here.
77
-
78
- **Author-supplied broadcast event names are unchanged.** A named-invalidation
79
- frame's `type` is still your `wireName` verbatim — that vocabulary is yours,
80
- not ours to prefix.
81
-
82
- `/asyncapi.json` documents the new `type` patterns, and its `info.version` is
83
- now the event-document version rather than a contract version.
84
-
85
- ### BREAKING: outbound webhooks are Standard Webhooks only
86
-
87
- The legacy `X-Webhook-Signature` / `X-Webhook-Event` / `X-Webhook-Delivery`
88
- headers and the Stripe-format `signPayload` / `verifySignature` pair are gone
89
- from the generated project — including from the public webhooks module's
90
- exports. Receivers must verify with `webhook-signature`. This is the one
91
- change a **receiver** absorbs without any config change of its own, so tell
92
- your endpoint partners.
93
-
94
- ### BREAKING: `include` and `fields[...]` are reserved query params
95
-
96
- `?include=` is always available now (where allowlisted), which makes `include`
97
- a reserved parameter and any `fields[`-prefixed key reserved too. **A column
98
- literally named `include` is no longer filterable** via `?include=…`. Unknown
99
- `?fields=` and `fields[<fk>]=` names return **400** instead of being dropped.
100
-
101
- ### Fixed: scoped projects without `auth.jwt` could not admit their own scope tokens
102
-
103
- Scope admission used to be emitted only inside the JWT credential lane, so a
104
- project with `authz.scopes` and no `auth.jwt` minted scope tokens that no
105
- generated code could accept — 401 on every presentation, with no diagnostic.
106
- Live since v0.64.0, when that lane stopped being on by default.
107
-
108
- Admission is now emitted whenever the project declares scopes, independent of
109
- `auth.jwt`. **No config change is needed** — and declaring scopes does not
110
- open the credential surface: no `POST /token` route, no identity fast-path,
111
- no bearer fast-path unless you separately declare `auth.jwt`.
112
-
113
- This covers **sessionless** scope tokens (`ctx.mintScope`). A token minted
114
- from a session — `POST /scope/v1/enter`, or a namespace with
115
- `mintScope: true` — carries user claims rather than the scope-only marker, so
116
- without `auth.jwt` it still cannot be admitted: 200 from the mint, 401 on
117
- presentation. The compiler now warns instead of failing silently. Declare
118
- `auth: { jwt: {} }` if you use those routes.
119
-
120
- ### CMS and Account consume CloudEvents frames as-is
121
-
122
- The bundled SPAs no longer invert realtime frames back into a private
123
- `{ type, table, event }` shape, and they no longer sniff `/api/v2` to pick
124
- the broadcast URL. They match on `qbframe`, read `data` / `qbseq`, and take
125
- `/broadcast/v1` or `/broadcast/v2` from the injected runtime config — the
126
- same prefixes the worker actually mounts.
127
-
128
- ### `allowClientIds` — optional client-supplied ids on create
129
-
130
- `providers.database.config.allowClientIds: true` lets `POST /` and
131
- `POST /batch` carry an **optional** `id`, built for optimistic updates: the
132
- client mints the id up front (`crypto.randomUUID()` under
133
- `generateId: 'uuid'`), renders immediately, and the server inserts that id —
134
- or mints one when it is omitted, exactly as before. The id is shape-locked at
135
- the Zod boundary to the active `generateId` strategy's format (400 on
136
- mismatch, 409 on collision), guards stay on (the id is compiler-managed and
137
- exempt from `createable`), and OpenAPI `<R>Create` schemas plus the client
138
- `Insert` types advertise it as optional. A no-op under `generateId: false`
139
- (ids stay client-supplied and **required**) and `'serial'` / numeric PKs.
140
- See [Client-supplied IDs](/api/crud#client-supplied-ids-optimistic-updates).
141
-
142
- ## v0.65.x — August 16, 2026
143
-
144
- ### Passkeys no longer silently degrade to `rpID: 'localhost'`
145
-
146
- The generated passkey plugin (and the SEALED reveal step-up, which must verify
147
- against the same relying party) now bakes a compile-time fallback derived from
148
- your configured domain — `account.domain` when set, else the unified host.
149
- `ACCOUNT_URL` remains a runtime override, and its **bare origin** is now used
150
- for WebAuthn even when the value carries a path (`https://host/account`), so
151
- one variable serves both the email link base and the relying-party origin.
152
- The rpID derivation also stops stripping two-label hostnames to a bare TLD
153
- (`example.com` no longer became rpID `com`). `localhost` now applies only to
154
- projects with no configured domain at all.
155
-
156
- ### `APP_URL` — per-deploy override for `account.appUrl`
157
-
158
- `account.appUrl` is baked at compile time into the Account SPA runtime config
159
- and the "Go To App" email CTAs, which pointed preview/dev deploys at
160
- production. Set `APP_URL` on the deploy target to override both at serve
161
- time — same one-bundle-several-hostnames pattern as `EXTRA_APP_HOSTS` and
162
- `BETTER_AUTH_URL`.
163
-
164
- ### Account SPA keeps its `/account` basepath through login redirects
165
-
166
- On path-mounted deployments, a post-login redirect could navigate to a bare
167
- path (`/dashboard` instead of `/account/dashboard`) and fall through to a
168
- tenant route. The callback sanitizer now re-applies the basepath to
169
- same-origin paths, covering every sign-in flow (password, passkey, email OTP,
170
- signup) and social-link callbacks.
171
-
172
- ### Fix: Start deploys of R2 apps failed to resolve `aws4fetch`
173
-
174
- Package-mode compiles (Start's **Deploy to Cloudflare**) bundle against the
175
- compiler image's `/deps/node_modules`, not a generated `npm install`. R2
176
- apps import `aws4fetch` from `src/storage/presign.ts`, but it was only
177
- declared on the generated `package.json` — CLI deploys worked, Start died
178
- with `Could not resolve "aws4fetch"`. The compiler image now ships the same
179
- pin the generator writes.
180
-
181
- ### Start: seeded admin uses your Quickback email
182
-
183
- A browser deploy writes the first `sysadmin` with the **verified email on
184
- your Quickback account**, not a synthetic `owner@<app>.invalid` address.
185
- Reset admin password still rotates the hash only — the broker never
186
- `UPDATE`s that email afterwards. See [Owner access](/start/deploy-owner-access).
187
-
188
- ## v0.65.0 — August 16, 2026
189
-
190
- ### All Quickback auth plugins are now bundled — zero `@quickback-dev/*` npm dependencies
191
-
192
- The compiler now vendors the AWS SES, AWS SNS, combo-auth, and
193
- upgrade-anonymous plugin sources into generated projects at
194
- `src/plugins/<name>/`, completing what the subscriptions plugin started in
195
- v0.64: **no generated project installs a `@quickback-dev/*` package from npm.**
196
- The plugin code ships with the compiler that wires it, so the emitted callers
197
- (`getSESConfig`, OTP callbacks, `upgradeAnonymous()` calls) can never skew from
198
- the plugin version they were generated against — and upgrades arrive by
199
- recompiling, not by `npm update`.
200
-
201
- Recompile and the dependencies disappear from `package.json`; no config
202
- changes needed. The `@quickback-dev/better-auth-*` npm packages are being
203
- retired from the registry — the vendored source in your project is the
204
- supported copy.
205
-
206
- ## v0.64.0 — August 15, 2026
207
-
208
- ### `contract.version` defaults to v2 — and no longer moves your URLs
209
-
210
- **Semantics and routes are now independent axes.**
211
-
212
- | Key | Controls | Default |
213
- |---|---|---|
214
- | `version` | Framing, strictness, the auth lane | `'v2'` |
215
- | `routes` | The URL prefix, nothing else | `'v1'` |
216
-
217
- A project with no `contract` block runs the **v2 contract on `/api/v1`**. You
218
- inherit the flagship semantics; your clients keep calling the address they
219
- already call.
220
-
221
- Previously these were one knob: `version: 'v2'` moved `/api`, `/auth`, and
222
- `/broadcast` to `/v2` as a side effect of selecting v2 behavior. That coupling
223
- made the better contract expensive to adopt for the wrong reason — a URL
224
- migration nobody asked for.
225
-
226
- **Breaking — action required if you pinned `version: 'v2'` for the URLs.**
227
- Add `routes: 'v2'` to keep serving `/api/v2`:
228
-
229
- ```typescript
230
- contract: { version: "v2", routes: "v2" }
231
- ```
232
-
233
- Without it, a previously-v2 project moves back to `/api/v1` on its next
234
- compile. Semantics are unaffected either way.
235
-
236
- ### What the v2 default changes on the wire
237
-
238
- URLs do not move. These do:
239
-
240
- - Realtime frames become CloudEvents 1.0 envelopes. The largest change — every
241
- subscriber re-parses. Routing info moves to `type`, payload to `data`.
242
- - Outbound webhooks are signed Standard-Webhooks-only; the legacy
243
- `X-Webhook-*` headers stop being sent. v1 already sent **both** sets, so
244
- consumers can migrate to `webhook-signature` before upgrading and the flip
245
- becomes a no-op for them.
246
- - Unknown `?fields=` names return `400` instead of being silently dropped.
247
- - The Quickback HMAC-JWT lane is off unless `auth.jwt` is declared.
248
- - `?include=`, aggregate changesets (`owns`), and delegated principals become
249
- available without a pin.
250
-
251
- Pin `contract: { version: "v1" }` to opt out. A pre-v0.64 project that leaves
252
- `contract.version` unset gets a one-time notice naming what changed — the
253
- generated `wrangler.toml` header records the resolved version in a
254
- `# quickback:contract` stamp, so new projects and projects that have already
255
- compiled on v2 stay warning-free without restating the default.
256
-
257
- ### Action-schema harvest no longer keys on contract version
258
-
259
- `assertCompleteActionInputSchemas` fired whenever the contract was v2 and any
260
- harvested schema was absent. With v2 as the default that would have failed
261
- every [Start](https://start.quickback.dev) project containing an action —
262
- `rawFiles` callers post project source and never execute action code, so they
263
- cannot harvest at all.
264
-
265
- The gate now fires only on a **partial** payload: some schemas supplied,
266
- others missing. Callers that supply none get the coverage warning instead. The
267
- CLI has failed closed on its own since v0.63.0, with the local per-action
268
- reason the compiler cannot know.
269
-
270
- ### Fixes
271
-
272
- - CloudEvents framing was derived from `broadcastBase.endsWith('/v2')`. Once
273
- routes and semantics decoupled, that silently reverted every default project
274
- to raw v1 frames. Framing is now passed explicitly.
275
- - The bundled CMS/Account SPAs gated their base-path override on *semantics*
276
- when it is a *routes* concern, emitting a redundant `/api/v1` override for
277
- every new project.
278
-
279
- ## v0.63.0 — August 14, 2026
280
-
281
- ### Action input schemas now fail the compile instead of degrading
282
-
283
- **Affects every project with actions, on every contract version.**
284
-
285
- The CLI harvests each action's `input` locally with `z.toJSONSchema`. When an
286
- action failed to harvest, the compiler fell back to a static parser that reads
287
- Zod as text — and that parser cannot emit `required` or `additionalProperties`.
288
- The resulting operation kept its `properties` and looked fully typed in
289
- `openapi.json` and the MCP tool list while enforcing nothing: generated clients
290
- treated required fields as optional and unknown keys passed. Constructs the
291
- parser could not read at all degraded further, to a bare `{}`.
292
-
293
- None of it was visible in a diff. One project shipped ~346 unenforced request
294
- schemas this way; the change read as reformatting.
295
-
296
- A failed harvest is now a compile error naming each action, whether bundling or
297
- evaluation failed, and the underlying local error. This was previously the
298
- behavior of `contract.version: 'v2'` only.
299
-
300
- `quickback compile --allow-degraded-schemas` restores degrade-and-continue for a
301
- single compile. It prints every action that fell back and why. (Removed in
302
- 0.66.2 — it worked on a total harvest failure but still threw on a partial one,
303
- the case it existed for.)
304
-
305
- The compiler also warns when a caller supplies no schemas at all — `rawFiles`
306
- callers such as the Start app cannot harvest — naming how many actions of the
307
- total lost `required`, with sampled paths.
308
-
309
- ### `contract.version` default flips to v2 in v0.64.0
310
-
311
- An unset `contract.version` resolves to `'v1'` today. That default becomes
312
- `'v2'` in **v0.64.0**. See the
313
- [contract matrix](/platform/api-contract#contractversion-is-retired).
314
-
315
- > v0.64.0 shipped this **without** moving any URLs — semantics and routes became
316
- > independent axes, so `/api/v1` stays put. This entry originally said the flip
317
- > would move `/api/v1` → `/api/v2`; that is not what happened.
318
-
319
-
320
- Every compile that leaves `contract.version` unset now warns. Pin
321
- `contract: { version: "v1" }` to keep the current wire, or set `"v2"` to migrate
322
- now.
323
-
324
- **Pinning your CLI version does not pin the contract.** The default lives in the
325
- compiler, which is a hosted service, so an older CLI inherits the flip too. The
326
- config key is the only pin.
327
-
328
- ### MCP tool grouping no longer assumes a `v1` path segment
329
-
330
- Internal. Group derivation matched the literal segment `v1`, so a contract-v2
331
- path would have fallen through and grouped under `api`. Operation tags take
332
- precedence and every generated operation carries one, so no shipped tool list
333
- was affected — the fallback is now correct for any `/api/v<n>/` prefix ahead of
334
- the v0.64.0 default flip.
335
-
336
- ## v0.62.0 — August 13, 2026
337
-
338
- ### Security: `record:` access arms on `GET /:id` were never evaluated
339
-
340
- **Affects any resource whose `read.access` contains a `record:` arm.**
341
-
342
- A code rewrite corrupted `"$ctx.userId"` into `"$effectiveCtx.userId"` inside the
343
- serialized access tree, and only the `$ctx.` prefix is recognised at runtime. The
344
- arm therefore compared a column against the literal string and was permanently
345
- false: a caller the config named was denied with 403 on the single-record read,
346
- while the same tree admitted them everywhere else.
347
-
348
- Those arms now evaluate. **Callers your config grants access to will start
349
- receiving 200 where they previously received 403.** That is the documented
350
- behavior being restored, not a widening — no caller is admitted whom the tree
351
- does not name. Durable Object room gates already behaved correctly, so this also
352
- removes a divergence where a room admitted a caller that `GET /:id` refused.
353
-
354
- ### Security: revocation is per scope kind, not per token
355
-
356
- **Affects projects using `authz.scopes`.**
357
-
358
- A token carried one proof timestamp for a claim map whose kinds were proven at
359
- different moments, so re-proving one kind restamped the others. A revoked kind
360
- survived indefinitely as long as the caller kept re-proving any sibling.
361
-
362
- Each entry now carries its own proof time, and both readers use it: the
363
- revocation check, and the carry-forward cap. **The cap matters more** — it
364
- applies on the default configuration, where `revocationCheck` is unset and no
365
- KV marker is ever read, so it was the only bound on a carried claim.
366
-
367
- Tokens minted before this release have no per-entry stamp and fall back to the
368
- token-level proof time, conservatively. `authz.scopes[].roles[].subKeys` may no
369
- longer declare `id`, `roles`, `subjectId`, or `sctMs` — those are server-minted,
370
- and a row value overwriting one would forge a proof time. Compile fails naming
371
- the path.
372
-
373
- ### Generated projects with in-worker Durable Objects can install again
374
-
375
- `npm install` failed with `ERESOLVE` immediately after a successful compile:
376
- `hono-party` requires `@cloudflare/workers-types@^4`, and Quickback pins `^5`.
377
- Unsatisfiable at any version — no `hono-party` release accepts 5.x.
378
-
379
- Generated `package.json` now carries a scoped override so the peer resolves to
380
- the project's own pin. Nothing outside `hono-party` is relaxed. Only projects
381
- declaring an in-worker Durable Object receive it.
382
-
383
- ### Fixed: two configurations that emitted uncompilable projects
384
-
385
- - `plugins: { apiKey: false }` emitted a `problemJson(...)` call without its
386
- import, so the generated project failed `tsc`.
387
- - `organization: { allowUserToCreateOrganization: … }` in object form emitted the
388
- key twice in one object literal (`TS1117`). `organizationHooks` had the same
389
- collision and is now stripped from the merged options — the compiler owns it.
390
-
391
- ### `defineEmail` — inbound mail, provider-agnostic execute
392
-
393
- Declare an inbound handler in `services/email/*.ts`. The compiler emits a shared `deliverInboundEmail()` dispatcher plus a Cloudflare Worker `email()` adapter. **Execute sees a portable `InboundEmailMessage`** (`from`, `to`, `headers`, `raw: ArrayBuffer`) — the same body runs for Cloudflare Email Routing and Amazon SES (Receipt → S3 → SNS calling `deliverInboundEmail`). Optional `to` matches the envelope recipient. Unmatched messages log a warning and are **not** rejected. Audit actor is `system:email-<name>`. See [Email](/platform/email).
394
-
395
- ## v0.61.0 — August 12, 2026
396
-
397
- ### Security: JWT revocation now fails closed when KV is unreachable
398
-
399
- **Affects projects using `auth.jwt.revocationCheck: 'kv'`** — including every
400
- project with a `.sealed()` column, which force-enables it.
401
-
402
- Setting `revocationCheck: 'kv'` asks the verifier to consult current security
403
- state before trusting a signed bearer. It did the opposite under failure: a
404
- missing `KV` binding, a failed read, or a corrupt entry all returned "not
405
- revoked," so a token was accepted during exactly the outage that hid its
406
- revocation. A banned user's bearer kept working for the rest of its TTL, and
407
- the one signal that would have caught it was the thing that had broken.
408
-
409
- The check now returns `active` / `revoked` / `unavailable`, and only `active`
410
- authenticates the bearer. A corrupt stamp is `unavailable` too — it used to
411
- parse as `NaN` and compare as "not revoked."
412
-
413
- **What changes operationally.** A bearer whose revocation state can't be read
414
- gets a retryable `503 AUTH_REVOCATION_UNAVAILABLE` ([RFC 9457](/api/errors))
415
- instead of being let through. Recovery is a separate cookie-only request: a
416
- request carrying `Authorization` has its cookie stripped before session auth,
417
- so during a KV outage every JWT-bearer request gets the 503 until the client
418
- retries on its session cookie. One reason-only log line per occurrence carries
419
- the cause (`missing-binding` / `read-error`) with no token, claim, or KV key in
420
- it — **alert on it.**
421
-
422
- This ties bearer-token availability to KV. That is the trade the opt-in now
423
- makes honestly, and it is the right way round: a revocation check that gives
424
- up under load is worth nothing. If you want the TTL bound *without* the
425
- coupling, leave `revocationCheck` at `'none'` and set `expiresIn: 30`.
426
-
427
- Because the binding is now load-bearing, a project with named `environments`
428
- must declare `bindings.kv` on **every** target — a compile error naming the
429
- environment, rather than a 503 discovered after deploy.
430
-
431
- `revocationCheck: 'none'` output is byte-identical. See
432
- [`revocationCheck`](/configure/auth#revocationcheck-none--kv--token-revocation-strategy).
433
-
434
- ### Security: revocation was off by one second
435
-
436
- **Also affects projects using `auth.jwt.revocationCheck: 'kv'`.**
437
-
438
- Revocation markers and token mint timestamps were both whole seconds, and the
439
- check rejected only a token stamped *strictly before* the marker. A token
440
- minted earlier in the same second as the revocation therefore compared **equal**
441
- and survived — a sub-second hole in a mechanism whose whole promise is
442
- "revoked within seconds." Whether an attacker landed in it was a coin flip on
443
- clock alignment, not on anything defensible.
444
-
445
- Markers are now epoch milliseconds, tokens carry millisecond companions
446
- (`iatMs`, and `sctMs` for the relationship-scope proof), and the comparison
447
- denies a tie. A token minted milliseconds before the revocation is rejected; one
448
- legitimately re-minted *after* it in that same second is still accepted, which
449
- is why simply flipping `<` to `<=` on seconds was not the fix.
450
-
451
- `iat` and `sct` remain standards-compatible unix **seconds** for external
452
- tooling — the millisecond claims are internal ordering metadata, set by the
453
- signer from the same clock sample and never accepted from a caller.
454
-
455
- **Rollout is conservative, not clever.** Marker format is read from an explicit
456
- version marker, never guessed from magnitude. Where one side is from v0.60.4 or
457
- earlier — an old token against a new marker, or any token against an old marker
458
- — there is no sub-second information to compare, so the **entire marker second**
459
- is revoked. That over-revocation is bounded (old tokens expire within their TTL,
460
- old markers within the entry lifetime), and it costs the caller a `401` and a
461
- re-authentication, exactly as any other rejected token does. No action is needed
462
- upgrading forward.
463
-
464
- **Do not straddle this release, though.** A worker from before v0.61.0 reads a
465
- millisecond marker as `NaN` and concludes *not revoked* — it does not recognise
466
- it as corrupt, so the fail-closed path added above never fires. Rolling back
467
- across this release, or running two differently-versioned deploy targets against
468
- one shared KV namespace, means every revocation written by the new version is
469
- **silently unenforced** by the old one until the entry expires (~19 minutes at
470
- default settings). Upgrade targets that share a namespace together. If you must
471
- roll back, treat outstanding bearers as unrevoked for that window: lower
472
- `expiresIn`, or purge the `qbrev:` keys and re-stamp from the old version.
473
-
474
- ## v0.60.4 — August 4, 2026
475
-
476
- ### Fix: retired-path cleanup was inert in v0.60.1–v0.60.3
477
-
478
- The stale-file cleanup shipped in v0.60.1 never ran. Both ends were correct —
479
- the compiler resolved the retired paths, the CLI was ready to delete them — but
480
- the v2 compile stream's `done` event didn't carry the field, so it arrived
481
- `undefined` and the CLI dutifully deleted nothing.
482
-
483
- The event is a hand-maintained projection of the compiler's output, and nothing
484
- type-checks that it stays complete: a field added on both sides but missed
485
- there is dropped in transit with no error anywhere. The only symptom was an
486
- absent side effect.
487
-
488
- The underlying duplication is gone rather than patched: the event is now
489
- derived from the compiler's output by omitting `files`, instead of three
490
- separate hand-maintained lists (the server builder, the CLI's type, the CLI's
491
- reconstruction) that all had to agree. A new field reaches the CLI for free. A
492
- test still asserts the contract so the intent stays visible.
493
-
494
- If you compiled on any of v0.60.1–v0.60.3, the stale root `openapi.json` /
495
- `asyncapi.json` / `schema-registry.json` are still on disk. Recompile on
496
- v0.60.4 and they are removed.
497
-
498
- ## v0.60.1 — August 3, 2026
499
-
500
- ### Fix: moved files no longer leave orphans behind
501
-
502
- Upgrading to v0.60 left the old `openapi.json`, `asyncapi.json`, and
503
- `schema-registry.json` sitting at your project root. The compiler wrote the new
504
- copies under `src/apps/__quickback/spec/`, but nothing removed the old ones —
505
- on a real project that was **6.7 MB of stale specs**, still committed, that
506
- tooling pointed at the old path kept reading in place of the live ones.
507
-
508
- That is worse than a clean break: a stale spec drifts from your API silently,
509
- where a missing file fails immediately.
510
-
511
- The root cause was structural, not a one-off. The compiler's output is a
512
- manifest of files to **write**, with no way to express "and drop what you wrote
513
- last time at a path I no longer use." The CLI's pre-write wipe covers `src/`
514
- only, so any path that relocates outside `src/` leaves an orphan forever.
515
-
516
- The compiler now also returns **retired paths**, and the CLI deletes them on
517
- your next compile. See [Retired paths](/tooling/output#retired-paths).
518
-
519
- Every filter errs toward keeping a file, because a wrong deletion is
520
- unrecoverable while a missed one is only untidy — a moved path is removed only
521
- once its replacement is actually emitted, a path the current compile still
522
- writes is never removed, and nothing may escape the output directory.
523
-
524
- No action needed: recompile and the stale files go.
525
-
526
- ## v0.60.0 — August 3, 2026
527
-
528
- ### Spec blobs move out of the Worker bundle
529
-
530
- `openapi.json`, `asyncapi.json`, and `schema-registry.json` are no longer
531
- imported by the Worker. They are emitted into `src/apps/__quickback/spec/` and
532
- served through the Cloudflare [ASSETS
533
- binding](https://developers.cloudflare.com/workers/static-assets/).
534
-
535
- Previously the specs shipped as text imports parsed lazily on first request.
536
- That kept their object graphs out of the isolate startup window, but the *bytes*
537
- still sat in the script V8 has to parse on every cold start. On a large API
538
- that is measured in megabytes, spent to serve discovery routes most callers
539
- never request. As assets they leave the bundle entirely.
540
-
541
- Measured on a 40-feature production API (paired runs, alternating, same
542
- machine):
543
-
544
- | | Before | After | |
545
- |---|---|---|---|
546
- | Bundle (raw) | 23,610 KiB | 17,218 KiB | **−6,392 KiB (−27%)** |
547
- | Bundle (gzip) | 3,027 KiB | 2,762 KiB | −266 KiB (−8.8%) |
548
- | Startup CPU (median) | 258 ms | 232 ms | −26 ms (−10%) |
549
- | of which GC | 77 ms | 70 ms | −7 ms |
550
-
551
- The bundle numbers are exact. The CPU figure is a local `wrangler check
552
- startup` median whose run-to-run ranges overlap, so treat −10% as the shape of
553
- the win rather than a precise constant — and note it scales with spec size: a
554
- project with a small spec will see little.
555
-
556
- Two consequences worth knowing:
557
-
558
- - Projects now get an `[assets]` block even with **no** CMS, Account, or custom
559
- app configured.
560
- - `run_worker_first = true` in that block is **security-load-bearing**, not a
561
- performance setting. It routes every request through your Worker first, so an
562
- asset is served only when the Worker fetches it — which is what keeps
563
- `__quickback/spec/` reachable exclusively through the gated spec routes. A
564
- `publish: 'admin'` spec is not a public URL. Do not relax it.
565
-
566
- The `[[rules]] type = "Text"` block added in v0.59 is gone; nothing imports the
567
- specs now.
568
-
569
- Routes and payloads are unchanged: `GET /openapi.json` returns the same spec
570
- under the same `openapi.publish` gate. See [Output
571
- structure](/tooling/output#spec-blobs-are-assets-not-bundle).
572
-
573
- > **BREAKING — `openapi.json` is no longer written to the project root.**
574
- > Tooling that read it (`npx openapi-typescript openapi.json`, CI steps, lint
575
- > rules) must point at `src/apps/__quickback/spec/openapi.json`.
576
- >
577
- > `api-types.gen.ts` is **unaffected** — the compiler still generates it at the
578
- > project root, which is why most projects never invoke `openapi-typescript`
579
- > directly and need no change at all.
580
- >
581
- > On your first compile after upgrading, the CLI deletes the now-orphaned root
582
- > copies. It only does so for blobs it just re-emitted under the new path, so an
583
- > older compiler that still writes to the root is never second-guessed.
584
-
585
-
586
- ## v0.59.1 — July 29, 2026
587
-
588
- ### Fix: auth and features D1 bindings could collapse onto one name
589
-
590
- A project whose database config carried a single `binding` (e.g.
591
- `binding: 'DB'`) emitted **two** `[[d1_databases]]` entries bound to the same
592
- name, while the generated code still called `env.AUTH_DB`. Half the runtime
593
- therefore reached a database with no auth tables.
594
-
595
- In split mode — the default for `cloudflare-d1` — `binding` names the
596
- **features** database only; auth is a separate D1 with its own `authBinding`.
597
- The service resolver was letting auth fall back to the generic `binding`, so one
598
- value drove both.
599
-
600
- It went unnoticed because three places resolved the auth binding independently
601
- and only one carried that extra fallback, so the reserved-name validator
602
- computed `AUTH_DB`/`DB`, saw no clash, and passed while the wrangler emit
603
- computed `DB`/`DB`. All three now agree.
604
-
605
- A binding collision in split mode is also a **compile error** now rather than a
606
- silently broken deploy, naming `authBinding` / `featuresBinding` and the
607
- `splitDatabases: false` single-database alternative as the fixes.
608
-
609
- Not introduced by v0.59.0 — the same behaviour is present in v0.58.3 and
610
- earlier. If you hit it, set `authBinding` explicitly or upgrade.
611
-
612
- ## v0.59.0 — July 29, 2026
613
-
614
- ### BREAKING · Masking: sensitive columns now require an explicit decision
615
-
616
- **The compiler no longer decides whether to mask a column. It refuses to
617
- compile until you do.**
618
-
619
- Quickback has always detected sensitive column names (`email`, `ssn`, `apiKey`,
620
- `stripeSecret`, `refreshToken`, …) and silently attached a default mask rule
621
- plus a warning. That was wrong in both directions: it broke list views nobody
622
- asked it to break, and it created a false sense of protection. Worse, only
623
- *some* surfaces read the auto-detected set — through v0.58.3 the HTTP response
624
- path applied **declared-only** masking while realtime and live views applied
625
- detected-plus-declared, so an auto-detected secret was redacted over WebSocket
626
- and returned in **plaintext** on `GET /:id`, list, `POST` and `PATCH`, and
627
- stayed freely filterable and sortable. Making detection non-silent removes that
628
- whole bug class by construction: the set of masked columns is now exactly the
629
- set you declared, so no two surfaces can disagree about it.
630
-
631
- Every detected column must now carry an explicit decision in `masking`:
632
-
633
- ```typescript
634
- masking: {
635
- apiKey: { type: 'redact', show: { roles: ['admin'] } }, // yes, mask it
636
- email: false, // no, reviewed
637
- }
638
- ```
639
-
640
- `false` is a new first-class answer meaning **reviewed — not sensitive here**:
641
- the value is returned in full and the column stays freely `?filter=`-able,
642
- `?sort=`-able and `?search=`-able. An omitted key is not a decision.
643
-
644
- #### Migrating
645
-
646
- Compile the project. For each error, you get the resource name, every undecided
647
- column, its suggested rule, and a paste-ready `masking` block with both answers
648
- per column — delete the wrong line from each pair:
649
-
650
- ```
651
- customers: 2 columns match Quickback's sensitive-column patterns but carry no masking decision.
652
- ...
653
- masking: {
654
- email: { type: 'email', show: { or: 'owner', roles: ['admin'] } }, // mask it
655
- // email: false, // …or this instead: reviewed, not sensitive here
656
- },
657
- ```
658
-
659
- Two ways to resolve each column:
660
-
661
- 1. **Mask it** — keep the suggested rule (or write your own). The value is
662
- redacted for callers outside `show.roles`, and only those roles may
663
- filter/sort/search it. Widen the query surface independently with
664
- `query: { roles: [...] }`; drop `or: 'owner'` if the table has no owner
665
- column.
666
- 2. **Don't mask it** — `column: false`. Nothing changes about how the column
667
- behaves; you've recorded that somebody looked.
668
-
669
- A false positive (`cc` on an accounting table, `webhook` on a config row) costs
670
- one line. That is the intended trade: the compiler asks about everything it
671
- recognises rather than guessing.
672
-
673
- Detection itself is unchanged — same keyword table, same suffix matching, and
674
- the suggested rule is still `show: { or: 'owner', roles: ['admin'] }`. It is
675
- now a suggestion in an error message rather than a default that applies on its
676
- own. See [Masking](/define/masking).
677
-
678
- ### Security fix: live views and realtime subscribe now evaluate `read.access`
679
-
680
- The live-view materialize route (`GET /api/v1/views/:view/:rootId`) and the
681
- view-subscribe ws-ticket lane applied the firewall and masking but **never the
682
- role gate**. A firewall is a tenant filter, not a role gate, so a same-org
683
- member who was correctly `403`'d on `GET /<table>/:id` received the full row —
684
- and every included child row — through the view, and could subscribe to its
685
- live deltas.
686
-
687
- Every table on a [live view](/platform/realtime/live-views#security) surface (the
688
- root *and* each included child) is now gated by its own `read: { access }`,
689
- **deny-on-any**: a root denial is a `403`, an included-table denial collapses to
690
- `404` with the firewall miss. Both entry points enforce it, and the gate lives
691
- inside the materializer so resync inherits it too.
692
-
693
- Shapes the view path cannot decide now **fail closed at compile time** instead
694
- of silently passing: function-form access, `relationship:`/`fga:` arms, and a
695
- `record:` condition on an *included* table. A `record:` condition on the root
696
- is evaluated post-fetch against the materialized row, the same two-phase gate
697
- `GET /:id` uses.
698
-
699
- ### Security fix: a team-only firewall no longer opens every tenant
700
-
701
- A resource whose **only** tenant predicate was team-scoped emitted no `WHERE`
702
- filter at all when `ctx.activeTeamId` was absent, so every authenticated caller
703
- could read, update and delete every tenant's rows.
704
-
705
- The team predicate is rendered drop-when-absent — correct while an org arm still
706
- bounds the query (the teamless rest-of-org slice), but with team as the sole arm
707
- "drop the team filter" meant "drop the entire tenant boundary". The claim is
708
- genuinely absent in ordinary setups: the Better Auth teams sub-plugin is opt-in,
709
- and the external auth provider never supplies it. Auto-detection also derives
710
- team-only isolation for any table carrying a `teamId` and no `organizationId`,
711
- with no explicit `firewall` block.
712
-
713
- An absent claim now **denies** when team is the sole tenant arm. Soft-delete and
714
- literal predicates are row filters, not tenant boundaries, so they don't count as
715
- a co-existing arm. Team alongside org is unchanged.
716
-
717
- Paired with a compile-time gate: a team-only firewall on a project without the
718
- teams sub-plugin is now a build error rather than a resource that denies every
719
- request, since that claim can never be populated. See
720
- [Firewall](/define/firewall).
721
-
722
- ### Security fixes: managed file storage
723
-
724
- Three scope-expansion holes in the managed file subsystem (`managed: true`):
725
-
726
- - **Removed organization members kept reading private files.** The files worker
727
- read `activeOrgId` straight off the session row; a session outlives
728
- membership, and a bucket with no `readRoles` had no second gate. Membership is
729
- now re-checked per request and a missing member row clears the organization
730
- before any org-scoped check.
731
- - **JWT claims were trusted as current.** The worker's JWT fast path took `orgId`
732
- and `role` from the signed token — a mint-time snapshot. Both are now
733
- re-derived from the database. The lookup only runs when a request carries an
734
- org claim, so user-scoped and public reads stay lookup-free.
735
- - **`writeScope: "user"` buckets bound nothing to the owner.** Keys come from a
736
- client-supplied path and the R2 write landed *before* the unique-key metadata
737
- insert could reject it, so a member who knew a peer's key overwrote their
738
- object — with no undo. Presigned uploads were worse: they signed a `PUT` URL
739
- and deleted the victim's metadata row. Both paths now check ownership first,
740
- and for presign that check runs *before signing*, since the URL is itself the
741
- write capability. The metadata row is also reserved before the R2 write, so a
742
- failed insert can no longer leave an overwrite behind.
743
-
744
- See [File storage](/platform/storage/r2).
745
-
746
- ## v0.58.1–v0.58.3 — July 28, 2026
747
-
748
- > No changelog entries were written for these three patch releases. Reconstructed
749
- > from git: compilation and generated-output hardening (`fc7d54fb`) and a
750
- > string-keyed batch FK visibility set that removes spurious `fkNotFound`
751
- > (`96f764ed`) in `0.58.1`; a CI deploy-serialization fix in `0.58.2`
752
- > (`2bf00e9c`). `0.58.3` was published from CI and has no bump commit in this
753
- > repository — its contents are not reconstructible from git history here.
754
-
755
- ## v0.58.0 — July 28, 2026
756
-
757
- ### `?include=<ownsRelation>` — the aggregate reader lands
758
-
759
- `read.include` now accepts **owns relation names** alongside FK columns:
760
- `?include=reactions` on a changeset root embeds the aggregate's owned child
761
- rows (pivot on the root PK, match the child's declared `fk`), landing in the
762
- same top-level `included` map keyed by include token, then row PK. The child's
763
- full security surface applies exactly as for FK embeds — pre-record-evaluable
764
- `read.access` (compile-enforced), firewall ANDed into the fetch on the
765
- caller-claims handle, masking, and `fields[<token>]` sparse projection. The
766
- `?fields=` pivot guard follows the direction: an owns embed requires the
767
- **source PK** in the projection (an FK embed still requires the FK column).
768
- This closes the changeset design's phase-2 reader — write the aggregate with
769
- the changeset media type, read it back with `?include=`.
770
-
771
- ### `afterCommit.reindex` + `afterCommit.notify` — the 06 fast-follows land
772
-
773
- The two deliveries deferred out of afterCommit v1 now ship, riding the same
774
- post-commit dispatch seam (best-effort, `waitUntil`, never rolling back the
775
- committed changeset):
776
-
777
- - **`reindex: true`** re-enqueues the committed **root row** for embedding
778
- regeneration on the same at-least-once `EMBEDDINGS_QUEUE` lane the plain
779
- routes use — after the tx commits, so a rolled-back changeset produces no
780
- orphan jobs. Fail-closed: requires the root's `embeddings` block; honors
781
- `onInsert`/`onUpdate: false`; a field-watch array means "always" on the
782
- aggregate lane. The owns validator's embeddings warning now clears for a
783
- reindex-declaring root (owned children still warn — root row only).
784
- - **`notify`** sends a device push via the web-push provider (compile error
785
- without `push: { provider: 'web-push' }`). The audience is a
786
- `defineRealtimeDelivery` profile resolved with the **same disclosure
787
- gates as `broadcast`** — masked columns, `q.stamp` proven identity, and
788
- child-id enumeration are shared code, not a parallel set. Title/body/url/
789
- tag are `{key}` templates over a gate-checked payload map; an unmapped
790
- placeholder is a compile error, a null value at runtime pushes to nobody.
791
- Scope-keyed deliveries fan to `scope:<room>` subscription tags; user
792
- deliveries to the user's devices; roles AND-compose.
793
-
794
- A reindex- or notify-only `afterCommit` no longer requires realtime
795
- infrastructure — the ws-infra gate now applies only to `broadcast`/`realtime`
796
- lanes.
797
-
798
- ## v0.57.1 — July 28, 2026
799
-
800
- > No changelog entry was written for this release. Reconstructed from git: a
801
- > polish pass over `0.57.0` — `q.table` column initializers that cannot be
802
- > resolved now throw instead of dropping silently (`ace6cf17`), the scope-grant
803
- > gate distinguishes "permission arm present" from "no arm at all"
804
- > (`1b7a5773`), tenant-scope arrow endpoints and object-thunk references parse
805
- > again so authz analysis is restored (`ad53b924`), and the anchored fallback
806
- > fails closed (`48c70370`).
807
-
808
- ## v0.57.0 — July 28, 2026
809
-
810
- ### Typed scoped `db` on every Neon mode + write-side audit forbids
811
-
812
- The action `db` is now schema-aware on **all** Neon connection modes, not just
813
- Hyperdrive: http mode gets the same insert relaxation and typed reads with
814
- `.transaction` **blocked at the type level** (the neon-http driver throws at
815
- runtime — the type now says so instead of a 500), websocket mode gets the full
816
- interactive-tx flavor. With D1 already typed, every supported provider's action
817
- `db` now carries the schema — including the `SealedValue` brand on `.sealed()`
818
- columns, so string-processing a sealed value is a compile error everywhere.
819
-
820
- On every typed provider, the compiler-managed audit keys are now `?: never` in
821
- `.insert().values()` **and** the newly-typed `.update().set()`: the audit
822
- wrapper hard-stamps them from the verified caller, so a supplied value was
823
- always discarded — now it's a compile error instead of a silent lie.
824
- `.set({ deletedAt })` stays allowed (the soft-delete signal).
825
-
826
- ### Hard-stamp unification — one audit-actor contract
827
-
828
- The scoped db's dead "fill-if-absent" actor lane is gone: on every wrapped
829
- handle, `createdBy`/`modifiedBy` come from the verified principal, period (the
830
- raw client remains the documented escape for system writes that own their
831
- provenance). Three attribution gaps closed with it: cron schedules' and queue
832
- handlers' `withInternalContext` now hand out an **audit-wrapped** db, so
833
- `system:cron-<name>` / `system:queue-<name>` actually land on audit columns;
834
- upserts into encrypted/sealed tables now stamp `modifiedAt`/`modifiedBy` on the
835
- `onConflictDoUpdate` conflict branch like every other write; and an org-scoped
836
- child table whose source can't accept the injected `organizationId` column now
837
- fails the compile instead of silently shipping without its tenant column.
838
-
839
- ### Visible audit columns — `...q.audit()` / `...q.softDelete()` + canon validator
840
-
841
- The compiler-managed audit quartet and soft-delete pair can now be **declared visibly**
842
- in authored feature files: q-DSL tables spread `...q.audit()` / `...q.softDelete()` into
843
- the columns object (types flow through — `$infer` shows `createdAt`/`modifiedBy`/… on the
844
- author's own table object), raw Drizzle tables declare the canonical lines literally.
845
- `quickback migrate visible-columns` codemods an existing project in one shot; emitted
846
- output is unchanged either way (the spreads expand to the exact injector lines).
847
-
848
- With visibility comes validation, **on by default**: every feature table must declare its
849
- managed columns visibly (`...q.audit()` / `...q.softDelete()` or the canonical literal
850
- lines — one `quickback migrate visible-columns` run), and every managed column that appears
851
- in authored source is checked against the canonical spec — insert-time default chains on
852
- `createdAt`/`modifiedAt` (+`$onUpdate`), nullable no-default actor columns, nullable
853
- no-default `deletedAt`, canonical SQL names, never `.encrypted()`/`.sealed()`. Divergence
854
- (silently accepted before) and missing declarations **fail the build**, with soft-delete
855
- presence pinned to `crud.delete.mode`. Opt out with
856
- `compiler.features.visibleAuditColumns: false`, which downgrades divergence to warnings and
857
- restores invisible injection. Unknown spreads in a q-DSL columns object are now a compile
858
- error instead of being silently dropped.
859
-
860
- Also in this line: `q.table`'s `$insert` type is honest (required vs defaulted/stamped
861
- columns; audit keys are `?: never` — the wrapper hard-stamps them), `$infer` includes the
862
- audit columns, and the canonical column definitions collapsed into one shared spec
863
- (`constants/managed-columns.ts`) consumed by the injectors, meta augmentation, request
864
- validation, spread expansion, and the new validator.
865
-
866
- ## v0.56.0–v0.56.11 — July 21–27, 2026
867
-
868
- > No changelog entries were written for the v0.56 line (twelve releases).
869
- > Reconstructed from git: feature-area follow-through — generated CRUD/changeset
870
- > routes claimed by an area prefix (`d33262e8`), feature-area transition route
871
- > adapters (`05d57940`), a fail-closed guard for generated routes under an area
872
- > prefix (`23f1f58d`), and a run of cross-feature resolution fixes
873
- > (`b6984a22`, `747dfad4`, `fb0cfb41`, `26bc569f`, `ae76e3e8`) — plus
874
- > relationship-proven `SESSION` parity for `q.stamp` (`b11fabfe`), an RLS
875
- > serial-sequence sweep with an audit-schema latch and `fga_tuples` backstop
876
- > (`299c93ee`), changeset trigger parity and `define-action` typing fixes
877
- > (`4c64edab`), and R2 files-migration scheduling gated on managed files
878
- > (`29b908f2`).
879
-
880
- ## v0.55.1 — July 21, 2026
881
-
882
- ### Feature areas — hierarchical authz grouping (`_area.ts`)
883
-
884
- A folder under `features/` carrying an `_area.ts` (`export default defineArea({...})`) is now
885
- an **area**: it declares a route prefix + admission lanes (the same shape as a project
886
- namespace, incl. `mintScope`/`acceptScope`) and an authz vocabulary — relationships, composed
887
- roles, named gates, tenant anchors, scope kinds — that every feature inside the folder
888
- references by bare name. The vocabulary is visible to the area's subtree ONLY: the compiler
889
- checks every reference channel (access roles/gates/scoped aliases, action `access`/`anchor`,
890
- firewall `via`/`{ rule }`/`{ tenant }` arms, `ctx.scope.<kind>` accessors, auth-view tenant
891
- includes, realtime handshake roles, table-level namespace lanes, and other `_area.ts` nodes)
892
- and fails the build on any outside reference. Root `authz` stays the global level, and root
893
- bodies may reference root-declared names only (no laundering an area name project-wide).
894
-
895
- Fail-closed rules shipped with it: re-declaring an inherited name is a compile error (no
896
- overrides in v1); a descendant action whose path opts out of the area prefix must carry an
897
- explicit `route: 'self'` marker; relative `path: './…'` resolves against the area prefix with
898
- dot segments rejected; foreign features can't claim paths (or table-level namespace prefixes)
899
- under an area's prefix; nested areas may add vocabulary but not mount a second prefix under a
900
- mounted ancestor (unlinked parent/child admission never compiles); and area-tree projects
901
- must declare `requires: ['feature-areas']` — the marker reaches the compiler through ANY CLI
902
- version, so an area-unaware toolchain is rejected instead of silently dropping nested
903
- features. Area projects also emit a reviewed audit artifact, `quickback/authz-manifest.json`
904
- (area tree, declared names, member features, area-gated vs self-gated actions, root-config
905
- namespace consumers), and the generated `AGENTS.md` gains a feature-areas section.
906
-
907
- Byte-parity guarantee: a flat root-authz project re-expressed as an area tree compiles to
908
- byte-identical output (the emit-site key-order determinism pass from v2 step 0 makes the fold
909
- order provably irrelevant). See [Feature areas](/define/areas).
910
-
911
- One cosmetic side effect of that determinism pass: the first recompile of an existing project
912
- on this release may reorder generated relationship-table **import lines** (they are now
913
- emitted in sorted order instead of authz-map insertion order). The reordering is a one-time,
914
- behavior-free diff.
915
-
916
- ### Access rules: named gates (`authz.rules`) and tenant anchors (`authz.tenants`)
917
-
918
- Two new root-`authz` blocks let you declare a row/role rule once and stamp it by name instead
919
- of copying predicates across files. A **named gate** in `authz.rules` bundles up to three
920
- arms — `who` (roles), `record:` (record-aware predicates), and `firewall` lanes — under one
921
- name, referenced by bare name in any `access: { roles: [...] }` array (applies who + record)
922
- and as `{ rule: '<name>' }` in a resource's `firewall:` (splices the lanes into the top-level
923
- AND array — a reference can only *narrow* row admission, never widen it). A **tenant anchor**
924
- in `authz.tenants` names the tenant predicate (`{ column, equals }`, claim side locked to
925
- verified ctx claims) and is written `{ tenant: 'org' }` in firewalls — with an optional
926
- per-site column override — and `tenant: 'org'` in auth-view includes. Expansion happens at
927
- compile time; emitted SQL is byte-identical to the inline spelling.
928
-
929
- Everything fails closed: gate/role/scoped-role/`+`/`:` name collisions, `+` hierarchy sugar
930
- inside rule bodies, `{ rule }` inside `all`/`any` groups, firewall-less gates referenced from
931
- `firewall:`, firewall-bearing gates on actions or in `masking.show`, and an access-side
932
- reference to a firewall-bearing gate whose lanes the resource doesn't also stamp are all
933
- compile errors. Gates in `realtime.requiredRoles` lower to static who-roles at the handshake;
934
- a declared non-empty list that lowers to nothing is a compile error, never a silent `[]`. A
935
- new `AUTHZ_UNKNOWN_ROLE_NAME` warning flags reference-shaped names that resolve to nothing.
936
- See [named gates](/define/authz-roles#named-gates-authzrules) ·
937
- [`{ tenant }`](/define/firewall#named-tenant-anchors-tenant) ·
938
- [`{ rule }`](/define/firewall#named-gate-references-rule).
939
-
940
- ## v0.55.0 — July 17, 2026
941
-
942
- ### Generated projects ship an `AGENTS.md`
943
-
944
- Every compiled project now emits an `AGENTS.md` at its root — the file coding agents read first — weaving Quickback's security model and a *"when to use what"* decision guide into the output. An agent editing the features is steered to the right primitive: a **view** for a filtered read, a **transition** for a guarded state change, an **action** for custom logic, **guards**/**masking** for field-level control, **named invalidations** for realtime refresh — each with a `docs.quickback.dev` link. It also documents the access tiers (incl. `SESSION`/`SCOPED`), the `WHERE column = value` firewall model with the org-OR-scope `{ any: [...] }` pattern for non-org callers, and the fail-closed coherence guardrail (with the *"never `exception: true` as a workaround"* rule). Regenerated on every compile.
945
-