Upgrade to unified Pages

Core 0.2.0 uses one Page model for all content. Content types define fields, URL patterns and default templates. The old Collections API, item tools and storage layout are removed. This is a coordinated data and runtime upgrade.

Typeroll Cloud operators performed this upgrade for managed installations. AI agents and integrations must use the Pages and Content types APIs.

Self-hosted installations

The upgrade was an offline migration of the Google Cloud (Firestore) installation profile, run with npm run self-host:migrate from a verified backup while every writer was stopped. That profile and its commands are removed in later releases. An installation still on data schema 1 must run the migration with Core 0.2.157 or earlier, following the guide in that release’s checkout, before it can move to a later release. The current runtime refuses schema 1, missing installation metadata and an unfinished migration lock.

The migration converted every site’s Pages, content types, templates, references, working copies and history. HTML bodies stayed HTML; automatic HTML-to-blocks conversion was not applied. Version inheritance and public URLs were preserved. Media objects and authentication accounts were not moved, and shared storage connections and site settings were retained.

Integration changes

Create articles and other records with create_page, using content_type and fields. Use Page IDs for previews, references, block tools and working copies. Replace old collection queries with list_pages and a content-type filter. Templates are reusable Page templates with a content slot. External Extensions using removed content scopes must publish an updated manifest; signed historical manifests are not rewritten during migration.