release

Identify the most recent stable extension release:

gh release view --json tagName,targetCommitish,publishedAt

Analyze changes since that release:

gh pr list --state merged --base main --json number,title,author,url,mergedAt,closingIssuesReferences --limit 1000 -q '[.[] | select(.mergedAt > "TIMESTAMP") | {number, title, author: .author.login, url, mergedAt, issues: .closingIssuesReferences}] | sort_by(.number)'

For each PR with linked issues, fetch the issue reporter:

gh issue view ISSUE_NUMBER --json number,author -q '{number, reporter: .author.login}'

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.

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

• Treat root README.md as the source of truth for Marketplace content.
• Update the "What's New" section for the release when appropriate.
• Do not manually edit src/README.md; the extension bundle step copies root README.md into src/README.md.
• Check for stale upstream Roo Code wording that should now say Zoo Code.

Write the release notes directly into CHANGELOG.md on the release branch.

• Use the heading format ## [version] (with square brackets) — e.g. ## [3.58.1]. The publish workflow at .github/workflows/marketplace-publish.yml extracts release notes by matching this exact pattern; headings without brackets will be missed and the GitHub release will fall back to a generic message.
• Always include contributor attribution and the PR number: use (PR #<prNumber> by @username).
• For PRs that close issues, include both issue and PR authors: - Fix: Description (#123 by @reporter, PR #456 by @contributor).
• For PRs without linked issues, include the PR number and author: - Add support for feature (PR #456 by @contributor).
• Provide brief descriptions of each item to explain the change.
• Order the list from most important to least important.
• Include every PR in the release window. Count the PRs and cross-reference the list before continuing.

For a major or minor release:

• Ask the user what three areas should be highlighted.
• Update relevant announcement files and documentation, including webview-ui/src/components/chat/Announcement.tsx, README.md, and the latestAnnouncementId in src/core/webview/ClineProvider.ts.
• Ask the user to confirm the English announcement before proceeding.
• Arrange translation updates for all supported locales affected by README, announcement, or package localization changes. Use the /roo-translate skill to propagate the updated chat.json announcement highlight keys and the "What's New" section to all supported locales.
• All 17 locale READMEs should contain a translated "What's New" section. Check each one and add a translated section where missing.

Create the release branch:

git checkout -b release/v[version]

Bump the version in src/package.json to the target release version and ensure CHANGELOG.md and src/CHANGELOG.md are up to date.

• Verify the CHANGELOG.md heading uses ## [version] (with brackets).
• Copy or sync CHANGELOG.md to src/CHANGELOG.md if the project keeps both.
• Review the generated version and changelog before opening the PR.

Open a single release PR with the fully generated release state.

git add CHANGELOG.md src/CHANGELOG.md src/package.json README.md locales/*/README.md src/package.nls*.json
# If generated or updated:
git add webview-ui/src/components/chat/Announcement.tsx src/core/webview/ClineProvider.ts
git commit -m "chore: prepare v[version] release"
git push origin release/v[version]
gh pr create --title "Release v[version]" --body "Release preparation for v[version]. This PR includes the final version bump, changelog updates, Marketplace README updates, and any announcement changes." --base main --head release/v[version]