Release notes for the ChaiBuilder SDK are published with each version. This page explains how releases relate to your license and the safe way to upgrade a project; check the in-builder update notice or your package registry for the latest version and its notes.

Versions and your license

License eligibility is tied to the release window, not to a running subscription:

• Your license covers any version released during your license year.
• After the license expires, versions released later are no longer eligible - the builder prompts you to renew or stay on the last eligible version.
• An expired license never breaks a deployed site; it only gates upgrades.

Details: Trial & Licensing.

Upgrading a project

An SDK upgrade is the same flow as any Payload schema change, because ChaiBuilder's tables live in your app's single migration pipeline:

# 1. Bump the SDK
pnpm update chaipro

# 2. Generate a migration for any schema changes the new version brings
pnpm payload migrate:create

# 3. Review the generated migration, then apply
pnpm payload migrate

Then run the app locally, click through the builder, and deploy. Notes:

• Read the release notes first - breaking changes and required config updates are called out per release.
• Migrations also run on boot in production (prodMigrations), so a deployed upgrade applies its own migrations - generating and reviewing them locally first is still the safe path.
• Pin and upgrade deliberately. Use exact versions in package.json and upgrade on your schedule rather than floating with a range.

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 where to ask upgrade questions.

Related

• Trial & Licensing - the license window model.
• Database Setup - the migration pipeline.
• Migration - moving existing sites into ChaiBuilder.