Skip to content

[Docs] Clarify stable release version lane after prereleases #260

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
edelauna merged 2 commits into from
May 23, 2026
Merged

[Docs] Clarify stable release version lane after prereleases #260

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7db3a0c
docs: clarify stable release version lane
roomote May 22, 2026
83e03f7
docs: use generic release version placeholders
roomote May 23, 2026
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
5 changes: 5 additions & 0 deletions .roo/commands/release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,11 @@ mode: code

4. Summarize the changes. If the user did not specify a release type, ask whether this should be a major, minor, or patch release.

- Before choosing the target release version, treat the nightly pre-release lane as separate from the stable lane.
- Zoo Code nightlies should stay on `major.ODD_NUMBER.patch` and use a large patch number for CI-generated pre-releases.
- Stable releases should stay on `major.EVEN_NUMBER.patch`.
- When preparing a stable release after an odd-minor pre-release line, advance to the next even minor instead of reusing the odd-minor pre-release lane.

5. Review and update the Marketplace-facing root `README.md`.

- Treat root `README.md` as the source of truth for Marketplace content.
Expand Down
Loading