ForgeCMS v0.4.0

Published ForgeCMS packages to npm as 0.4.0.

• @forge-cms/admin@0.4.0
• @forge-cms/angular@0.4.0
• @forge-cms/api@0.4.0
• @forge-cms/auth@0.4.0
• @forge-cms/cloudflare@0.4.0
• @forge-cms/core@0.4.0
• @forge-cms/db@0.4.0
• @forge-cms/runtime@0.4.0
• @forge-cms/storage@0.4.0
• @forge-cms/testing@0.4.0

ForgeCMS v0.3.0

ForgeCMS packages have been published to npm as 0.3.0.

This release syncs GitHub tags/releases with the package versions currently published under the @forge-cms scope.

Highlights include browser auth foundations, cookie-backed sessions, CSRF-protected auth endpoints, and the 0.3.0 package version bump across the fixed @forge-cms package group.

ForgeCMS v0.0.2

Second public experimental release of ForgeCMS.

API stability is not guaranteed before 1.0.

Highlights:

• Collection-level compound indexes and unique constraints (spec 046): indexes?: { fields: string[]; unique?: boolean }[] on defineCollection, validated at definition time and enforced identically across the InMemory, D1, and libSQL adapters.
• Unique-constraint conflicts now surface as a typed UniqueConstraintError (409, UNIQUE_CONSTRAINT) from the Local API down to the HTTP layer, with no per-handler changes needed.
• Shared adapter contract tests (runDatabaseAdapterConstraintContractTests) prove identical constraint behavior across all three database adapters.
• CI/release hardening: release verification no longer hardcodes an expected package version, so future fixed-group version bumps don't require a matching CI change.

All public packages (@forge-cms/core, db, auth, storage, api, runtime, cloudflare, angular, admin, testing) are published at 0.0.2.

ForgeCMS v0.0.1

First public experimental release of ForgeCMS.\n\nAPI stability is not guaranteed before 1.0.\n\nHighlights:\n- Core schema DSL, runtime validation, access/hook metadata, relations, uploads, rich text, globals, versions, localization, and relation integrity options.\n- Runtime, Local API, framework-agnostic HTTP handlers, and Cloudflare D1/R2 adapters.\n- Angular client SDK and Angular admin components.\n- Shared adapter contract tests, docs, demo apps, CI/CD, packed-artifact verification, E2E, Cloudflare Pages deploy, and Changesets publish pipeline.