Skip to content

[Doc] Drop the 0.x phase from the versioning policy #636

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
koic merged 1 commit into from
Oct 28, 2026
+3 −9
Merged

[Doc] Drop the 0.x phase from the versioning policy #636

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
12 changes: 3 additions & 9 deletions VERSIONING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,15 +12,9 @@ Given a version number `MAJOR.MINOR.PATCH`:
- **MINOR** is incremented for backwards-compatible new functionality.
- **PATCH** is incremented for backwards-compatible bug fixes.

### Current 0.x Phase

While the SDK is at version 0.x, the public API is not yet considered stable.
Following SemVer conventions for initial development, minor releases (0.x -> 0.y) may contain breaking changes.
All breaking changes are recorded in [CHANGELOG.md](CHANGELOG.md).

### After 1.0.0

Once 1.0.0 is released, breaking changes will only ship in major releases, with the exceptions described below.
Breaking changes ship only in major releases, with the exceptions described below.
Before 1.0.0, minor releases (0.x -> 0.y) could contain breaking changes, following SemVer conventions
for initial development; [CHANGELOG.md](CHANGELOG.md) records them.

## What Counts as a Breaking Change

Expand Down
Loading