Release v3.58.1 (#495)

* chore: prepare v3.58.1 release

* Apply suggestion from @edelauna

Co-authored-by: edelauna <54631123+edelauna@users.noreply.github.com>

* review fixes

* Update locale readmes

---------

Co-authored-by: edelauna <54631123+edelauna@users.noreply.github.com>

Author: navedmerchant

.roo/commands/release.md

@@ -36,16 +36,9 @@ mode: code
     - 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.
 
-6. Create the release notes as a changeset file at `.changeset/v[version].md`, then run `pnpm changeset:version` on the release branch before opening the PR.
-
-    ```md
-    ---
-    "zoo-code": patch|minor|major
-    ---
-
-    [list of changes]
-    ```
+6. 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)`.
@@ -67,13 +60,10 @@ mode: code
     git checkout -b release/v[version]
     ```
 
-9. Generate the final release state on that branch:
-
-    ```bash
-    pnpm changeset:version
-    ```
+9. Bump the version in `src/package.json` to the target release version and ensure `CHANGELOG.md` and `src/CHANGELOG.md` are up to date.
 
-    - This should update `src/package.json`, `CHANGELOG.md`, and `src/CHANGELOG.md`, then consume the `.changeset` file.
+    - 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.
 
 10. Open a single release PR with the fully generated release state.

CHANGELOG.md

@@ -1,5 +1,11 @@
 # Zoo Code Changelog
 
+## [3.58.1]
+
+### Patch Changes
+
+- Fix: Remove unsupported `--no-absolute-filenames` tar argument (#491 by @kazenshi, PR #492 by @kazenshi)
+
 ## 3.58.0
 
 ### Minor Changes

src/package.json

@@ -3,7 +3,7 @@
 	"displayName": "%extension.displayName%",
 	"description": "%extension.description%",
 	"publisher": "ZooCodeOrganization",
-	"version": "3.58.0",
+	"version": "3.58.1",
 	"icon": "assets/icons/icon.png",
 	"galleryBanner": {
 		"color": "#617A91",