Skip to content

docs: don't pre-assign version numbers to refactoring themes - #246

Merged
ShotaroKataoka merged 1 commit into
mainfrom
docs/versioning-theme-numbering
Aug 1, 2026
Merged

docs: don't pre-assign version numbers to refactoring themes#246
ShotaroKataoka merged 1 commit into
mainfrom
docs/versioning-theme-numbering

Conversation

@ShotaroKataoka

Copy link
Copy Markdown
Contributor

Summary

Adds a release-planning rule to .kiro/steering/versioning.md, learned while landing the elements-split refactoring (#245):

  • The v0.5.1 tag is gated on a cloud E2E check, and the next roadmap theme (internal-only refactoring, which needs no tag per this policy) merged into main first — so its pre-assigned "v0.5.2" number became a dead letter.
  • New rule: name refactoring themes "Theme N" in roadmaps and decide the tag at release time. Tags stay milestone-based; a gated tag being overtaken by the next theme no longer breaks the numbering.

Testing

Docs-only change (one steering file). No code paths affected.

…factoring themes

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
@ShotaroKataoka ShotaroKataoka added the blog:skip ブログ対象外 label Aug 1, 2026
@ShotaroKataoka
ShotaroKataoka merged commit e5cd0f1 into main Aug 1, 2026
14 of 15 checks passed
@ShotaroKataoka
ShotaroKataoka deleted the docs/versioning-theme-numbering branch August 1, 2026 00:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

blog:skip ブログ対象外

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant