v3.3.2

Editor and dashboard

• Reorder repeater items in the editor. Drag items or use the keyboard and move controls in the fields panel. This works for top-level and nested repeaters, including for content-only editors. Items keep their values and identities when moved.
• Edit more comfortably on phones and tablets with responsive dialogs, larger touch targets, and stacked editing panes.
• Create, rename, delete, and reorder pages more reliably. Newly created nested pages are easier to find, and previews use the correct page-type head settings.
• Retry failed saves without re-entering content. Inline text, rich text, image editing, and block selection are more reliable.
• Return to the same dashboard group and scroll position after editing, refreshing, or using Back and Forward. Starter sites clone faster.
• Content-only editors can update content while the server protects design code, field schemas, site settings, and domains.

Repeater reordering: move items earlier, later, first, or last from the fields panel.

Page creation on mobile: the responsive Pages dialog keeps page details and controls within reach.

Publishing and site transfers

• Publishing reuses unchanged page builds and scripts. Interactive blocks initialize independently, preserve distinct generated IDs across repeated sections, and better preserve rendered content and head elements.
• Site-wide fields resolve consistently across editing, import, and publication. Publishing validates routes, page structure, and references before replacing live output.
• Site and shared-library exports preserve CMS code edits. Partial site uploads preserve existing routes and sections, and larger CLI imports can use checksum-verified chunks through restrictive proxies.
• Archive imports support up to 512 MiB. Recovery snapshot uploads authenticate before streaming, use a default 256 MiB file limit with operator overrides, and remain available if publishing fails.
• Domain changes preserve existing published output and update sitemap URLs to the new hostname. Hosted setup includes Fly domain-provider support and readiness checks.

Local development and reliability

• Develop locally on the dashboard provides a setup prompt for a local agent. Approve CLI access in the browser using your existing CMS session.
• This CMS release pairs with Primo CLI 0.3.0 and Primo MCP 0.1.11. Both CLI 0.3.0 and MCP 0.1.11 are available on npm.
• The editor loads its core compiler assets from the CMS origin, starts compiler workers as needed, and recovers more reliably from interrupted downloads and temporary session refresh failures.
• Updated dependencies, stricter validation, and safer analytics handling improve security and privacy.

Develop locally: choose a local workflow and copy the setup prompt directly from the dashboard.

Screenshots show v3.3.2 with demo content.

Compatibility and upgrading

• Back up the complete PocketBase data directory (normally pb_data) and any
  separately configured file storage before upgrading. Stop writes while making
  a filesystem copy, or use PocketBase's supported backup operation. Keep the
  previous executable/image and verify that the backup can be restored into a
  separate directory. Automatic push backups cover a site's or library's content;
  they are not a substitute for a complete instance backup.
• Rehearse the upgrade on that copy. Database migrations run at startup. For
  rollback, restore the pre-upgrade data and matching previous executable;
  do not run the previous version against an already migrated database.
• Published sites now send Content-Security-Policy: frame-ancestors 'self'.
  Same-origin embedding continues to work. Embedding a published site in an
  iframe on another origin is blocked; check existing integrations before upgrading.
• Local development uses primo-cli@0.3.0 and primo-mcp@0.1.11. It requires
  Node 22.13 or newer on the 22.x line, or Node 24 or newer. Building the CMS
  from source requires Node 22.17 or newer on the 22.x line, or Node 24 or newer.
  The standalone CMS executable does not require Node.
• Browser approval for CLI sign-in requires HTTPS when connecting to a server
  outside the local computer.

Verified release assets

The five native binaries are the exact artifacts from successful qualification of commit b7538843. SHA-256 checksums are provided in SHA256SUMS, with a qualification record beside each executable.

Full changes since v3.3.1