Migration
Upgrade coordinated package and editable-source consumers to the current Nerio beta without treating it as a stable Core 1.0 release.
Current status
1.0.0-beta.1 is the current public beta. It is not a stable release; external feedback and manual accessibility/device evidence remain required before 1.0.
Keep all six public Nerio packages aligned. Package and source-install consumers should upgrade the coordinated set together.
Beta.0 to beta.1 changes
Review the consumer-visible changes below, update the coordinated package set together, and then run the package verification commands.
| Area | What changed | Required action |
|---|---|---|
| Runtime support | Node.js 22 or 24 and Tailwind CSS 4.1 or newer | Update the consumer toolchain before installing the coordinated packages. |
| Calendar and DatePicker | Deterministic initial month and current-day behavior | Pass a consumer-owned today value when the product needs the current month or day marker. |
| Interactive types | Nerio-owned event and state contracts | Replace Base UI type imports and use stable string values for Tabs. |
| Registry | Source integrity and HTTPS-first remote access | Use HTTPS for production registries and declare SHA-256 integrity for custom sources. |
| CLI updates | Atomic source and lock-file transactions | Run doctor, diff, and update --dry-run before applying an editable-source update. |
| MCP | Declared output schemas and structuredContent | Prefer structured output when supported; existing JSON text consumers remain compatible. |
pnpm installpnpm typecheckpnpm buildEditable source installs
Inspect the update before writing. Unchanged files can advance automatically; a normal update preserves locally modified files so the product owner can port that intent onto the new upstream source.
pnpm exec nerio doctorpnpm exec nerio diffpnpm exec nerio update --dry-runpnpm exec nerio updatepnpm exec nerio diffConsumers still on alpha
The temporary alpha aliases were removed when the beta baseline was established. If a product still uses alpha packages, complete the alpha-to-beta migration first, then return to the beta.0-to-beta.1 changes above.
Compatibility contract
Public package exports and types, tokens, Registry data, CLI/MCP contracts, support ranges, and public documentation routes are snapshot-protected. Defaults, DOM and ARIA structure, events, and source-update behavior can also be breaking even when the visual change is small.
Read the complete public API stability policy.