Skip to content

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

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
ShotaroKataoka merged 1 commit into from
Aug 1, 2026
+3 −0
Merged

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

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
3 changes: 3 additions & 0 deletions .kiro/steering/versioning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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`)
Expand Down
Loading