This is the largest release since 1.0. Forty commits, and three themes worth calling out: Inline became a collaborative editor, the edge cache moved onto Cloudflare's Workers Cache, and the schema layer grew the kind of guardrails that stop a content model rotting as it ages.
Realtime collaboration
The dashboard is now multiplayer, backed by Durable Object rooms rather than polling.
- Live presence — see who else is in the dashboard, on which entry, as a presence dot on content-list rows and a bottom-centre toast in the editor.
- Live comments and review handoff — comments appear as they are written, and handing an entry to a reviewer is now a live event rather than a page refresh.
- Cross-device live preview — edit on one device, watch the preview update on another.
- Status incidents and media events broadcast to every open dashboard, so a failing integration surfaces without a reload.
Edge caching on Cloudflare's Workers Cache
The hand-rolled caches.default layer is gone. The Worker is now a thin gateway that routes cacheable requests to three cache-enabled entrypoints — pages, delivery, and media — and lets the platform own freshness, request collapsing, tiered caching, and stale-while-revalidate.
What this buys you:
- Global instant purge. Publishing an entry purges its page everywhere, not per-colo. Replacing or deleting a media object now purges every derived variant of it — previously impossible.
- Correct image caching. A transformed image is cached per negotiated format, so an AVIF render is never handed to a browser that cannot decode it.
- Zero-execution cache hits. A cached page is served without the render graph executing at all.
Editors are unaffected by design: any logged-in dashboard user bypasses the cache entirely and always sees a fresh render.
Upgrading
This release requires wrangler 4.107 or newer and moves the engine compatibility date to 2026-05-01. Run pnpm inline update and redeploy; no application code changes are needed.
Note that Workers Cache does not run in local development — this is deliberate on Cloudflare's part. Cache behaviour is observable on a deployed Worker only.
A stricter schema layer
Content models now carry their own rules, and the dashboard enforces them client-side:
- Per-field
validatefunctions, with a new warning severity for advisory problems that should not block a save. - Deprecation markers on fields, containers, and types — deprecated things are visibly marked in the dashboard and can be retired without breaking existing content.
- Schema-level filters on relationship pickers, so an editor only ever sees the entries a field is actually allowed to reference.
- Reference integrity and usage tracking — an entry knows what points at it, and deleting something that is still in use tells you so.
Typed delivery, end to end
Delivery queries are now typed from the schema through to the response, so a query for a content type returns that type's fields with no hand-written interfaces to drift.
Editor and CLI
- Canvas media drop — drag an image straight onto the page canvas.
- Block multi-select with bulk operations.
inline deploy <env>andinline migrate <env>are first-class commands with coordinated, minimal step output shared across deploy, migrate, update, docs, and init.- Lossless content export — an export can now be re-imported without loss.
Fixes
- Page passwords work on the public site again (
/api/protected/unlockis wired). - CSRF protection on the dashboard API, and an account-lockout denial-of-service path is closed.
- Snapshots no longer abort when the database is behind on migrations.
- The content list no longer crashes for users without analytics permission.