You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .roo/commands/release.md
+9-5Lines changed: 9 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,15 +26,19 @@ argument-hint: patch | minor | major
26
26
- Without issue: "- Add support for Gemini 2.5 Pro caching (thanks @contributor!)"
27
27
- CRITICAL: Include EVERY SINGLE PR in the changeset - don't assume you know which ones are important. Count the total PRs to verify completeness and cross-reference the list to ensure nothing is missed.
28
28
29
-
6. If a major or minor release:
29
+
6. If the generate_image tool is available, create a release image at `releases/[version]-release.png`
30
+
- The image should feature a realistic-looking kangaroo doing something human-like that relates to the main highlight of the release
31
+
- Pass `releases/template.png` as the reference image for aspect ratio and kangaroo style
32
+
- Add the generated image to .changeset/v[version].md before the list of changes with format: ``
33
+
7. If a major or minor release:
30
34
- Ask the user what the three most important areas to highlight are in the release
31
35
- Update the English version relevant announcement files and documentation (webview-ui/src/components/chat/Announcement.tsx, README.md, and the `latestAnnouncementId` in src/core/webview/ClineProvider.ts)
32
36
- Ask the user to confirm that the English version looks good to them before proceeding
33
37
- Use the new_task tool to create a subtask in `translate` mode with detailed instructions of which content needs to be translated into all supported languages (The READMEs as well as the translation strings)
34
-
7. Create a new branch for the release preparation: `git checkout -b release/v[version]`
35
-
8. Commit and push the changeset file and any documentation updates to the repository: `git add . && git commit -m "chore: add changeset for v[version]" && git push origin release/v[version]`
36
-
9. Create a pull request for the release: `gh pr create --title "Release v[version]" --body "Release preparation for v[version]. This PR includes the changeset and any necessary documentation updates." --base main --head release/v[version]`
37
-
10. The GitHub Actions workflow will automatically:
38
+
8. Create a new branch for the release preparation: `git checkout -b release/v[version]`
39
+
9. Commit and push the changeset file and any documentation updates to the repository: `git add . && git commit -m "chore: add changeset for v[version]" && git push origin release/v[version]`
40
+
10. Create a pull request for the release: `gh pr create --title "Release v[version]" --body "Release preparation for v[version]. This PR includes the changeset and any necessary documentation updates." --base main --head release/v[version]`
41
+
11. The GitHub Actions workflow will automatically:
38
42
- Create a version bump PR when changesets are merged to main
39
43
- Update the CHANGELOG.md with proper formatting
40
44
- Publish the release when the version bump PR is merged
0 commit comments