Versioning and stability

Check Core compatibility, component status, public entry points, and release notes before upgrading Tavo.js UI.

Current package contract

The current web package is in the 0.1 release line and declares @tavojs/core ^0.1.0 as a peer dependency.
Every component in the current public metadata catalog is marked stable.
The metadata type supports stable and experimental component status.
Only package.json entry points are public; source-internal paths are not application APIs.
The package changelog is the source of release additions and breaking changes.

Read the changelog and confirm the matching @tavojs/core peer range.
Upgrade @tavojs/ui as one unit; its bundled tavo-ui command follows the same package version and is not upgraded separately.
Keep imports on root, grouped, focused, theme, plugin, metadata, or accessibility package entry points.
Run type checking, theme checks, CSS token validation, SSR tests, and full browser flows.
Regenerate physical theme assets when the project does not use plugin injection.
Inspect metadata status when tooling automatically recommends or scaffolds components.