From e0ce0e1a5ea6649b0b22ee0a649f3764f1732548 Mon Sep 17 00:00:00 2001 From: ShotaroKataoka Date: Sat, 1 Aug 2026 09:08:52 +0900 Subject: [PATCH] =?UTF-8?q?=F0=9F=93=9A=20docs(v0.5.x-consolidation-roadma?= =?UTF-8?q?p):=20don't=20pre-assign=20versions=20to=20refactoring=20themes?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Lesson from the elements-split theme: the v0.5.1 tag is gated on a cloud E2E check, and the next theme (internal-only, no tag needed per this policy) merged into main first — so the pre-assigned 'v0.5.2' number became a dead letter. Name roadmap themes 'Theme N' and decide the tag at release time instead. SPEC: 20260731-0820_v0.5.x-consolidation-roadmap --- .kiro/steering/versioning.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.kiro/steering/versioning.md b/.kiro/steering/versioning.md index 8bafcb94..8d1ee70a 100644 --- a/.kiro/steering/versioning.md +++ b/.kiro/steering/versioning.md @@ -17,6 +17,9 @@ ## Release - Milestone-based (manual decision) - Tag when user-facing changes have accumulated +- Do not pre-assign version numbers to refactoring themes in roadmaps — + name them "Theme N" and decide the tag at release time (a tag gated on + e.g. E2E can be overtaken by the next theme, breaking the numbering) - Breaking changes must always bump MAJOR - No release needed for internal-only refactoring - Git tag format: `v{MAJOR}.{MINOR}.{PATCH}` (e.g., `v0.1.0`)