Skip to content

docs(readme): replace stale v0.7.0 with the v0.x line #645

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kyle-sexton merged 1 commit into from
Oct 1, 2026
Merged

docs(readme): replace stale v0.7.0 with the v0.x line #645

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -96,7 +96,7 @@ which the current SHA-pin governance model gives no reason to expect.
**`v0.x` carries no stability guarantee.** Per SemVer's own terms, "Major
version zero (0.y.z) is for initial development. Anything MAY change at any
time. The public API SHOULD NOT be considered stable" ([SemVer, item
4][semver]). This repository is `v0.7.0` at the time of writing: a release may
4][semver]). This repository is on the `v0.x` line: a release may
still ship a change a post-1.0 line would have to treat as its own
minor/patch distinction. Committing to `v1.0.0` — SemVer's "defines the public
API" milestone ([SemVer, item 5][semver]) — is a deliberate, separate decision
Expand Down