chore: drop release image references

Author: roomote

.roo/commands/release.md

@@ -53,29 +53,20 @@ mode: code
     - 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.
 
-7. If an image generation tool is available, create a release image at `releases/[version]-release.png`.
-
-    - The image should relate to the main release highlight and fit the existing release-image style.
-    - Add the generated image to `.changeset/v[version].md` before the list of changes:
-
-        ```md
-        ![X.Y.Z Release - Description](/releases/X.Y.Z-release.png)
-        ```
-
-8. For a major or minor release:
+7. 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.
 
-9. Create the release branch:
+8. Create the release branch:
 
     ```bash
     git checkout -b release/v[version]
     ```
 
-10. Generate the final release state on that branch:
+9. Generate the final release state on that branch:
 
     ```bash
     pnpm changeset:version
@@ -84,23 +75,23 @@ mode: code
     - This should update `src/package.json`, `CHANGELOG.md`, and `src/CHANGELOG.md`, then consume the `.changeset` file.
     - Review the generated version and changelog before opening the PR.
 
-11. Open a single release PR with the fully generated release state.
+10. Open a single release PR with the fully generated release state.
 
     ```bash
     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 releases/[version]-release.png webview-ui/src/components/chat/Announcement.tsx src/core/webview/ClineProvider.ts
+    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 release assets or announcement changes." --base main --head 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]
     ```
 
     - There is no separate version-bump PR in this flow.
     - The release PR should already contain the final version number and generated changelog updates.
     - If the release includes translated README or package-localization updates, include those files in the same PR.
     - Let the release validation workflow and normal PR checks run before merge.
 
-12. After the release PR is merged, stop for a release review on the resulting `main` commit.
+11. After the release PR is merged, stop for a release review on the resulting `main` commit.
 
     ```bash
     git switch main
@@ -115,7 +106,7 @@ mode: code
     - Share that review summary, including `REVIEWED_SHA`, with the user and wait for explicit confirmation before creating the tag.
     - Do not create the tag or trigger publishing until the user says to proceed.
 
-13. Only after explicit confirmation, create the release tag on that reviewed `main` commit:
+12. Only after explicit confirmation, create the release tag on that reviewed `main` commit:
 
     ```bash
     git tag v[version] "$REVIEWED_SHA"
@@ -124,7 +115,7 @@ mode: code
 
     - If `main` advances after the review pause, keep using the pinned `REVIEWED_SHA` for the tag instead of silently tagging a newer commit.
 
-14. The stable publish workflow runs from the `v[version]` tag.
+13. The stable publish workflow runs from the `v[version]` tag.
 
     - Do not create the tag before the release PR is merged.
     - The publish workflow validates that the tag version matches `src/package.json`.

CHANGELOG.md

@@ -4,7 +4,6 @@
 
 ### Patch Changes
 
-- ![3.55.1 Release - VS Code 1.122 ripgrep hotfix](/releases/3.55.1-release.png)
 - Fix API requests hanging indefinitely on VS Code 1.122.0+ when Zoo Code could not find the bundled ripgrep binary after the `@vscode/ripgrep-universal` rename (#381 by @greatgradz-svg, PR #248 by @0xMink).
 
 All notable changes to Zoo Code will be documented in this file.