6.2 upgrade guide
Current stable package versions, feature changes, and database migration requirements.
The 6.2 release includes the changes since Core 6.0.0. Install the exact package versions
below together. Stable packages use npm's latest channel.
pnpm dlx @btst/codegen@6.2.1 initFor an existing application, update only its selected packages and required code
dependencies. Keep runtime registration keys unchanged. The optional Better Auth
UI companion is @btst/better-auth-ui@3.0.3; database adapters remain 3.0.1.
Tested package versions
| Package | Stable version |
|---|---|
@btst/stack, @btst/codegen | 6.2.1 |
@btst/components, @btst/plugin-open-api, @btst/plugin-route-docs | 1.0.1 |
@btst/plugin-affiliate | 1.1.1 |
@btst/plugin-blog | 1.1.1 |
@btst/plugin-ai-chat, @btst/plugin-comments, @btst/plugin-crm | 1.1.0 |
@btst/plugin-feedback, @btst/plugin-job-board, @btst/plugin-kanban, @btst/plugin-media | 1.1.0 |
@btst/plugin-notifications, @btst/plugin-ui-builder | 1.1.0 |
@btst/plugin-analytics, @btst/plugin-cms, @btst/plugin-ecommerce, @btst/plugin-feature-flags | 1.2.0 |
@btst/plugin-form-builder, @btst/plugin-newsletter | 1.2.0 |
@btst/plugin-calendar | 1.3.0 |
@btst/plugin-school | 2.1.1 |
@btst/plugin-helpdesk, @btst/plugin-search | 1.0.0 |
The CLI installation set
records individual pins. Use this set with Core >=6.2.1 <6.3.0;
prerelease packages retain their separate beta compatibility ranges.
Core 6.2.1 and Blog 1.1.1 fix native Blog static rendering: prefetched list,
article, and tag content remains visible before JavaScript runs. Use the
direct page entries with hydrated
route data. Keep prefetched published content outside page-wide Suspense
boundaries. This rendering patch requires no schema migration.
Changes since 6.0
- Blog adds revision history, editorial review, scheduling, and page-specific cards. CMS adds publication policies, scheduled dispatch, and revision history.
- Feedback, Helpdesk, Notifications, and Search add independent packages with application-owned authorization. Optional bridges connect notifications, support tickets, CRM contacts, and Kanban work.
- Calendar adds provider synchronization, team assignment, group capacity, and waitlists. School uses the shared asynchronous payment contract and connects course discussions.
- Ecommerce adds digital delivery, protected downloads, authorized refunds, and recovery after uncertain provider responses. Affiliate supports shared payment attribution.
- CRM adds duplicate review and transactional merges, deal ownership, and owner filters. Newsletter adds campaign recovery and forms integration.
- Analytics adds funnels and experiment conversion attribution; Feature Flags exposes experiment reporting.
- Form Builder adds conditional fields, file uploads, and shared server validation. Page component slots and route-scoped AI authoring context extend existing plugin pages.
Upgrade persistent databases first
Generate the schema from the application's registered backend stack, review the SQL, and apply additive migrations before serving the upgraded packages. Installing packages alone does not migrate an application database.
| Selected feature | Required upgrade review |
|---|---|
| Blog | Add revision and editorial workflow models and fields. Follow the revision migration before enabling history or review. |
| CMS | Add publication fields and revision models; review existing records before enabling a publication policy. |
| CRM | Add normalization and revision fields, backfill populated tables, and verify isolated transactions and foreign keys before enabling duplicate merges. Deal ownership reuses Kanban assignees. |
| School | Apply nullable enrollment payment-state columns and migrate synchronous payment callbacks to the shared asynchronous provider contract. |
| Calendar | Apply provider, team, capacity, waitlist, and payment-hold schema additions before serving the updated endpoints. |
| Ecommerce | Apply tax, verified-payment, digital-grant, and refund-attempt schema changes. Existing paid orders do not automatically become verified digital purchases. |
| New plugins | Generate the selected plugin's tables and configure its identity, permissions, storage, and delivery providers before exposing routes. |
Provider credentials, protected file storage, scheduled dispatch, email delivery, and payment webhooks remain application responsibilities. Follow each selected plugin's configuration guide. Keep the previous application artifact and lockfile available while checking sign-in, public content, administrative writes, and any enabled payment or background-dispatch flows.
Screens and demonstrations
The current feature evidence includes real generated-app screens and captioned walkthroughs. Each capture describes its fixtures and verification limits: