Versions & releases
A schema's content lives in immutable, SemVer-numbered versions. You never edit a published version — you release a new one. Consumers pin an exact version with @vX.Y.Z, or track the latest.
- Immutable and numbered
- Each version is frozen once published; the first is 0.1.0. Pinned versions are served as permanent, cached artifacts.
- The bump is derived
- Rusl computes the minimum SemVer bump from the change — a breaking change to an existing example forces a major. You can release a higher number, never a lower one.
- Every version carries examples
- A version ships with at least one example, validated against its content. The registry also shows shape analysis: root type, field and $ref counts, and dependencies.
- Lifecycle
- An active version can be deprecated (consumers are warned to upgrade) or yanked (no longer resolvable), and either can be reactivated.
You don't create a version directly — accepting a proposal does.