Anabaai
diff --git a/‎.dockerignore‎
Lines changed: 0 additions & 1 deletion b/‎.dockerignore‎
Lines changed: 0 additions & 1 deletion
diff --git a/‎.gitattributes‎
Lines changed: 14 additions & 0 deletions b/‎.gitattributes‎
Lines changed: 14 additions & 0 deletions
diff --git a/‎.github/ISSUE_TEMPLATE/bug_report.yml‎
Lines changed: 2 additions & 0 deletions b/‎.github/ISSUE_TEMPLATE/bug_report.yml‎
Lines changed: 2 additions & 0 deletions
diff --git a/‎.github/workflows/update-contributors.yml‎
Lines changed: 1 addition & 1 deletion b/‎.github/workflows/update-contributors.yml‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎.gitignore‎
Lines changed: 1 addition & 0 deletions b/‎.gitignore‎
Lines changed: 1 addition & 0 deletions
diff --git a/‎.roo/commands/release.md‎
Lines changed: 40 additions & 0 deletions b/‎.roo/commands/release.md‎
Lines changed: 40 additions & 0 deletions
diff --git a/‎.roo/roomotes.yml‎
Lines changed: 33 additions & 0 deletions b/‎.roo/roomotes.yml‎
Lines changed: 33 additions & 0 deletions
@@ -80,7 +80,6 @@ src/node_modules
 !webview-ui/
 !packages/evals/.docker/entrypoints/runner.sh
 !packages/build/
-!packages/cloud/
 !packages/config-eslint/
 !packages/config-typescript/
 !packages/evals/
 
@@ -4,3 +4,17 @@ src/assets/docs/demo.gif filter=lfs diff=lfs merge=lfs -text
 
 # Test snapshot files - mark as linguist-generated to exclude from GitHub language statistics
 *.snap linguist-generated=true
+
+# Non-English translation files - mark as linguist-generated to exclude from GitHub language statistics
+# Root locales directory (contains only non-English translations)
+locales/** linguist-generated=true
+
+# Mark all locale directories as generated first
+src/i18n/locales/** linguist-generated=true
+webview-ui/src/i18n/locales/** linguist-generated=true
+
+# Then explicitly mark English directories as NOT generated (override the above)
+src/i18n/locales/en/** linguist-generated=false
+webview-ui/src/i18n/locales/en/** linguist-generated=false
+
+# This approach uses gitattributes' last-match-wins rule to exclude English while including all other locales
@@ -25,6 +25,7 @@ body:
         - AWS Bedrock
         - Chutes AI
         - DeepSeek
+        - Fireworks AI
         - Glama
         - Google Gemini
         - Google Vertex AI
@@ -38,6 +39,7 @@ body:
         - OpenAI Compatible
         - OpenRouter
         - Requesty
+        - SambaNova
         - Unbound
         - VS Code Language Model API
         - xAI (Grok)
 
@@ -24,7 +24,7 @@ jobs:
       - name: Update contributors and format
         run: |
           pnpm update-contributors
-          npx prettier --write README.md
+          npx prettier --write README.md locales/*/README.md
           if git diff --quiet; then echo "changes=false" >> $GITHUB_OUTPUT; else echo "changes=true" >> $GITHUB_OUTPUT; fi
         id: check-changes
         env:
 
@@ -3,6 +3,7 @@ dist
 out
 out-*
 node_modules
+package-lock.json
 coverage/
 mock/
 
 
@@ -0,0 +1,40 @@
+---
+description: "Create a new release of the Roo Code extension"
+argument-hint: patch | minor | major
+---
+
+1. Identify the SHA corresponding to the most recent release using GitHub CLI: `gh release view --json tagName,targetCommitish,publishedAt`
+2. Analyze changes since the last release using: `gh pr list --state merged --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)'`
+3. For each PR with linked issues, fetch the issue details to get the issue reporter: `gh issue view ISSUE_NUMBER --json number,author -q '{number, reporter: .author.login}'`
+4. Summarize the changes. If the user did not specify, ask them whether this should be a major, minor, or patch release.
+5. Create a changeset in .changeset/v[version].md instead of directly modifying package.json. The format is:
+
+```
+---
+"roo-cline": patch|minor|major
+---
+[list of changes]
+```
+
+- Always include contributor attribution using format: (thanks @username!)
+- For PRs that close issues, also include the issue number and reporter: "- Fix: Description (#123 by @reporter, PR by @contributor)"
+- For PRs without linked issues, use the standard format: "- Add support for feature (thanks @contributor!)"
+- Provide brief descriptions of each item to explain the change
+- Order the list from most important to least important
+- Example formats:
+    - With issue: "- Fix: Resolve memory leak in extension (#456 by @issueReporter, PR by @prAuthor)"
+    - Without issue: "- Add support for Gemini 2.5 Pro caching (thanks @contributor!)"
+- 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.
+
+6. If a major or minor release:
+    - Ask the user what the three most important areas to highlight are in the release
+    - 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)
+    - Ask the user to confirm that the English version looks good to them before proceeding
+    - 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)
+7. Create a new branch for the release preparation: `git checkout -b release/v[version]`
+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]`
+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]`
+10. The GitHub Actions workflow will automatically:
+    - Create a version bump PR when changesets are merged to main
+    - Update the CHANGELOG.md with proper formatting
+    - Publish the release when the version bump PR is merged
@@ -0,0 +1,33 @@
+version: "1.0"
+
+commands:
+    - name: Pull latest changes
+      run: git pull
+      timeout: 60
+      execution_phase: task_run
+    - name: Install dependencies
+      run: pnpm install
+      timeout: 60
+      execution_phase: task_run
+
+github_events:
+    - event: issues.opened
+      action:
+          name: github.issue.fix
+    - event: issue_comment.created
+      action:
+          name: github.issue.comment.respond
+    - event: pull_request.opened
+      action:
+          name: github.pr.review
+    - event: pull_request.opened
+      action:
+          name: general.task
+          prompt: |
+              1. Run the script `node scripts/find-missing-translations.js` and carefully review its output for any missing translations.
+              2. If the script reports missing translations, switch into `translate` mode and add them in all supported languages.
+              3. If you've added new translations, commit and push them to the existing PR.
+              4. If you get a permission error trying to push to the PR just give up (i.e don't create a new PR instead).
+    - event: pull_request_review_comment.created
+      action:
+          name: github.pr.comment.respond