Compatibility and releases

Nuxt Customer Portal is an MIT-licensed monorepo. Copyright belongs to “Nuxt Customer Portal contributors”; the repository root LICENSE governs the reusable packages and source unless a file says otherwise.

The public packages use linked version 0.1.0-alpha.0. This milestone pack-tests the package artifacts without publishing them. Alpha releases may make intentional breaking changes before 1.0.0; Changesets records user-visible package changes and keeps the official versions aligned.

Supported baseline

• Nuxt 4 and compatible Vue/framework peers;
• PostgreSQL;
• English and Dutch;
• npm, pnpm, Yarn, and Bun consumers.

Documented package exports are the compatibility surface. Host aliases, physical paths across packages, demo shell components, raw internal records, and direct changes to official database tables are not.

Upgrading

1. Read package Changesets and compare manifests.
2. Run nuxt-customer-portal doctor.
3. Inspect nuxt-customer-portal db status and the pending SQL.
4. Test a fresh database and an upgrade copy.
5. Run typecheck, builds, package tests, and critical portal workflows.
6. Deploy with a restorable backup and a forward-repair plan.

Checksums make published migration files immutable. Disabling a package leaves its data intact. A host that alters an official table must fork or explicitly take over that provider's migration stream and cannot assume upstream compatibility.

Publication boundary

The first milestone does not publish npm packages, change DNS, migrate production databases, or modify Ludulicious. Registry scope ownership and package-name availability must be verified before a public prerelease.