Compatibility

Mizu components become part of your application source. Versions still matter because updates can change props, exports, behavior, markup assumptions, and design tokens.

Pinned by default

Documentation commands use the immutable v0.1.4 registry. The same URL will always return the same source, dependency ranges, and integrity manifest.

Following latest

Use the latest channel when you intentionally want the newest release. Review the changelog before rerunning it because copied source may change.

Versioning contract

• Patch releases fix defects without intentionally breaking the public contract.
• Before 1.0, minor releases may contain documented breaking changes and migration notes.
• After 1.0, breaking changes require a major release.
• Public contracts include prop and callback names, compound exports, documented behavior, accessibility semantics, CSS token names, and documented markup assumptions.
• Deprecated APIs remain available for at least one minor release when security or correctness does not require immediate removal.

Release records

Each pinned directory includes a manifest.json with its version, source commit, file sizes, and SHA-256 integrity values. Old pinned directories are never rewritten or removed during a normal release. Breaking changes and any exceptional yanks are recorded in the changelog.