Changelog

ChaiBuilder ships three things on independent release cycles, so there are three changelogs.

Changelog	Covers	Read it when
chaipro	The Pro package (chaipro), the licensed builder your project depends on	You are upgrading the SDK in an existing project
chaicore	The open source core (chaicore): the embeddable editor and the basic website builder	You embed the editor directly or track the open source line
Starter	The public starter repositories - starter-sqlite and starter-postgres - that npx chaibuilder-app create and the one click deploys generate from	You are starting a new project, or pulling starter changes into an existing one

How to read an entry

Every release carries its version and release date, followed by grouped changes:

• Breaking - requires a config, code or database change on your side. Always read these before upgrading.
• Added - new capability.
• Changed - existing behavior that works differently now.
• Security - a hardening change. Worth reading even when nothing else in the release affects you.
• Fixed - a bug that no longer happens.
• Removed - a capability or option that is gone.

A release with no group of a given kind simply omits it. Releases that only carry dependency bumps or internal maintenance are listed as maintenance releases with no detail.

Each chaipro release from v0.3.0 onward has a page of its own, listed on the chaipro changelog, which also carries the upgrade notes for that release. Earlier releases, and the chaicore and starter lines, are summarised inline on their changelog page.

Versioning

chaipro follows semantic versioning. While the package is pre 1.0, minor bumps (0.2.x to 0.3.0) are where breaking changes land, so treat a minor bump the way you would treat a major one after 1.0. Pin an exact version in package.json and upgrade deliberately.

chaicore will follow semantic versioning once it publishes. See chaicore for current status.

The starter is not a package you install, so it is not versioned with semver. It ships as two repositories, starter-sqlite and starter-postgres, and releases through the 2026-09-05 split are tagged in pairs, one tag per database flavor, at each snapshot worth pulling:

v3-sqlite    v3-pg
v2-sqlite    v2-pg
v1-sqlite    v1-pg

v3-sqlite and v3-pg are the same release, differing only in the database the project is wired to. Read the entry once and apply the tag matching your database.

Versions and your license

License eligibility is tied to the release window, not to a running subscription. Your license covers any chaipro version released during your license year, and an expired license never breaks a deployed site, it only gates upgrades. Details: Trial and Licensing.

Upgrading

The safe upgrade procedure, including the migration steps that an SDK bump can require, lives in Releases and Upgrading.

Staying informed

• In the builder - update and license notices surface directly in the editor.
• Release notes - published per release alongside the package.
• Support channels - see Support for upgrade questions.