From c67d1d6f502229d482cb1c64e6dd6aa47e2b953a Mon Sep 17 00:00:00 2001 From: Koichi ITO Date: Sun, 11 Oct 2026 04:05:59 +0900 Subject: [PATCH] [Doc] Drop the 0.x phase from the versioning policy ## Motivation and Context VERSIONING.md still opens its policy with a "Current 0.x Phase" section, written when the gem was below 1.0.0, and an "After 1.0.0" section describing the present as the future. The gem has been at 1.x since 1.0.0 shipped, so the two sections are replaced by the current rule, stated once: breaking changes ship only in major releases, with the exceptions the document goes on to describe, and the 0.x releases are mentioned as history. ## How Has This Been Tested? Docs only. ## Breaking Changes None. --- VERSIONING.md | 12 +++--------- 1 file changed, 3 insertions(+), 9 deletions(-) diff --git a/VERSIONING.md b/VERSIONING.md index 1b2cd88b..615b69ec 100644 --- a/VERSIONING.md +++ b/VERSIONING.md @@ -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