Versioning and Upgrade Policy
Widgemo Core is currently in its first public release line.
There are no migration guides yet because there are no prior released versions to migrate from.
Current State
| Item | Status |
|---|---|
| First released version | 0.1.0 |
| Available migration guides | None yet |
| Backward-compatibility baseline | Starts at 0.1.0 |
What Will Appear Here Later
This page will be expanded when a released version introduces a migration-relevant change. Future entries will include:
- affected versions (
from->to) - impacted APIs and config contracts
- required vs optional migration steps
- deprecation timelines
- verification checklist
Upgrade Policy (Current)
- No upgrade playbook is required for
0.1.0adopters yet. - Until migration notes exist, use the latest docs as the source of truth for current contracts.
- If a future release requires changes, this page will contain version-scoped instructions.
Integration Safety Baseline
For long-term stability:
- prefer root exports from
@widgemo/widgemo-core - treat advanced subpath usage as deliberate and version-sensitive
- keep extension registrations namespaced to reduce collisions
- rely on documented config contracts in the Reference section