Skip to content

docs: state the pre-1.0 stability and upgrade expectations in the README #833

Description

@psamiton

The public release is deliberately not a 1.0 — the goal is to be past major refactors and UX friction, not to freeze the surface. That's fine, but it should be said out loud so early adopters know what they're signing up for. A short README section:

Small, but it converts "ambiguous stability" into "explicit expectations", and it's the public face of the #732 compat-inventory decision.

Part of the public-release readiness push.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions