Back to Blog
Announcement 4 min read

Flare CMS v1.0 Released

Forked from Flare CMS and rebuilt as a monorepo. Here's what changed and why.

JA
Jaime Aleman

The Birth of Flare CMS

Flare CMS started as a fork of Flare CMS v2.8.0, an excellent headless CMS for Cloudflare Workers. After months of building on top of it — adding collections, fixing bugs, deploying to production — it became clear that the project had evolved enough to stand on its own.

What Changed

The migration from four separate repositories into one pnpm monorepo was the biggest structural change:

  • packages/core — Renamed from @sonicjs-cms/core to @flare-cms/core. All exports renamed: createFlareApp, FlareConfig, FlareApp, FLARE_VERSION. Old names kept as deprecated aliases.
  • packages/cms — Cloudflare Worker backend with collection configs. Renamed to flare-cms on Cloudflare.
  • packages/site — Astro 5 SSR frontend. Renamed to flare-site on Cloudflare Pages.

Admin UI Rebranding

Every user-visible "Flare CMS" string in the admin dashboard, login page, API docs, and plugin system was updated. The version badge now shows v1.0.0 instead of inheriting from upstream.

CI/CD Pipeline

GitHub Actions deploys automatically on push to main:

  1. Build the core package (produces 8 entry points via tsup)
  2. Deploy the CMS Worker to Cloudflare (parallel)
  3. Build and deploy the Astro site to Cloudflare Pages (parallel)

Steps 2 and 3 run in parallel after the core build, cutting deploy time roughly in half.

Custom Domains

The project now runs on its own domain:

  • flarecms.dev — Public Astro site
  • admin.flarecms.dev — CMS backend and admin dashboard

Known Issues

Some bugs were inherited from Flare CMS v2.8.0 and remain in v1.0:

  • API filter parameters are ignored server-side (must filter client-side)
  • Select field defaults don't pre-populate in the admin UI
  • Content status is one-way — can't unpublish once published
  • Soft-delete doesn't cascade to child records

These will be addressed in future releases, either as fixes in @flare-cms/core or as upstream PRs to Flare CMS.

What's Next

The roadmap for v1.x includes:

  • Full documentation site (dogfooding Flare CMS itself)
  • Fix the broken API filters
  • Redesigned admin UI (replacing the inherited Flare CMS look)
  • Image optimization via Cloudflare Images