upstream/v3.17.2

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -2,79 +2,85 @@ name: Bug Report
 description: Clearly report a bug with detailed repro steps
 labels: ["bug"]
 body:
+  - type: markdown
+    attributes:
+      value: |
+        **Thanks for your report!** Please check existing issues first:  
+        👉 https://github.com/RooVetGit/Roo-Code/issues
+
   - type: input
     id: version
     attributes:
       label: App Version
-      description: Specify exactly which version you're using (e.g., v3.3.1)
+      description: What version of Roo Code are you using? (e.g., v3.3.1)
     validations:
       required: true
 
   - type: dropdown
     id: provider
     attributes:
       label: API Provider
-      description: Choose the API provider involved
-      multiple: false
       options:
-        - OpenRouter
         - Anthropic
-        - Google Gemini
+        - AWS Bedrock
+        - Chutes AI
         - DeepSeek
-        - OpenAI
-        - OpenAI Compatible
-        - GCP Vertex AI
-        - Amazon Bedrock
-        - Requesty
         - Glama
-        - VS Code LM API
+        - Google Gemini
+        - Google Vertex AI
+        - Groq
+        - Human Relay Provider
+        - LiteLLM
         - LM Studio
+        - Mistral AI
         - Ollama
+        - OpenAI
+        - OpenAI Compatible
+        - OpenRouter
+        - Requesty
+        - Unbound
+        - VS Code Language Model API
+        - xAI (Grok)
+        - Not Applicable / Other
     validations:
       required: true
 
   - type: input
     id: model
     attributes:
       label: Model Used
-      description: Clearly specify the exact model (e.g., Claude 3.7 Sonnet)
-    validations:
-      required: true
-
-  - type: textarea
-    id: what-happened
-    attributes:
-      label: Actual vs. Expected Behavior
-      description: Clearly state what actually happened and what you expected instead.
-      placeholder: Provide precise details of the issue here.
+      description: Exact model name (e.g., Claude 3.7 Sonnet). Use N/A if irrelevant.
     validations:
       required: true
 
   - type: textarea
     id: steps
     attributes:
-      label: Detailed Steps to Reproduce
+      label: 🔁 Steps to Reproduce
       description: |
-        List the exact steps someone must follow to reproduce this bug:
-        1. Starting conditions (software state, settings, environment)
-        2. Precise actions taken (every click, selection, input)
-        3. Clearly observe and report outcomes
-      value: |
-        1.
-        2.
-        3.
+        Help us see what you saw. Give clear, numbered steps:
+
+        1. Setup (OS, extension version, settings)
+        2. Exact actions (clicks, input, files, commands)
+        3. What happened after each step
+
+        Think like you're writing a recipe. Without this, we can't reproduce the issue.
     validations:
       required: true
 
   - type: textarea
-    id: logs
+    id: what-happened
     attributes:
-      label: Relevant API Request Output
-      description: Paste relevant API logs or outputs here (formatted automatically as code)
-      render: shell
+      label: 💥 Outcome Summary (Optional)
+      description: |
+        Recap what went wrong in one or two lines. Use this if the bug is weird, unexpected, or needs extra context.
+
+        Example: "Expected code to run, but got an empty response and no error."
+      placeholder: Expected ___, but got ___.
 
   - type: textarea
-    id: additional-context
+    id: logs
     attributes:
-      label: Additional Context
-      description: Include extra details, screenshots, or related issues.
+      label: 📄 Relevant Logs or Errors
+      description: Paste API logs, terminal output, or errors here. Use triple backticks (```) for code formatting.
+      render: shell

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,76 @@
+name: Detailed Feature Proposal
+description: Propose a specific, actionable feature or enhancement for implementation
+labels: ["proposal", "enhancement"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        **Thank you for proposing a detailed feature for Roo Code!**
+
+        This template is for submitting specific, actionable proposals that you or others intend to implement after discussion and approval. It's a key part of our [Issue-First Approach](../../CONTRIBUTING.md).
+
+        - **For general ideas or less defined suggestions**, please use [GitHub Discussions](https://github.com/RooVetGit/Roo-Code/discussions/categories/feature-requests?discussions_q=is%3Aopen+category%3A%22Feature+Requests%22+sort%3Atop) first.
+        - **Before submitting**, please search existing [GitHub Issues](https://github.com/RooVetGit/Roo-Code/issues) and [Discussions](https://github.com/RooVetGit/Roo-Code/discussions) to avoid duplicates.
+
+        For guidance or to discuss your idea, join the [Roo Code Discord](https://discord.gg/roocode) and DM **Hannes Rudolph** (`hrudolph`).
+
+        A maintainer (especially @hannesrudolph) will review this proposal. **Do not start implementation until this proposal is approved and assigned.**
+  - type: textarea
+    id: problem-description
+    attributes:
+      label: What problem does this proposed feature solve?
+      description: Clearly describe the problem, use case, or opportunity this feature addresses. Why is this change needed?
+      placeholder: e.g., "Users currently cannot..." or "It would be beneficial if..."
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposed-solution
+    attributes:
+      label: Describe the proposed solution in detail
+      description: Provide a clear and comprehensive description of the feature or enhancement. How should it work? What are the key functionalities?
+      placeholder: Include details on user interaction, expected behavior, and potential impact.
+    validations:
+      required: true
+
+  - type: textarea
+    id: technical-details
+    attributes:
+      label: Technical considerations or implementation details (optional)
+      description: If you have thoughts on how this could be implemented, or specific technical aspects to consider, please share them.
+      placeholder: e.g., "This might involve changes to X component..." or "We should consider Y library..."
+
+  - type: textarea
+    id: alternatives-considered
+    attributes:
+      label: Describe alternatives considered (if any)
+      description: What other ways could this problem be solved or this functionality be achieved? Why is your proposed solution preferred?
+      placeholder: Briefly outline any alternative approaches and why they were not chosen.
+
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional Context & Mockups
+      description: Add any other context, mockups, screenshots, or links that help illustrate the proposal.
+
+  - type: checkboxes
+    id: checklist
+    attributes:
+      label: Proposal Checklist
+      description: Please confirm the following before submitting.
+      options:
+        - label: I have searched existing Issues and Discussions to ensure this proposal is not a duplicate.
+          required: true
+        - label: This proposal is for a specific, actionable change intended for implementation (not a general idea).
+          required: true
+        - label: I understand that this proposal requires review and approval before any development work begins.
+          required: true
+
+  - type: checkboxes
+    id: willingness-to-contribute
+    attributes:
+      label: Are you interested in implementing this feature if approved?
+      description: (This is optional and does not affect the proposal's consideration)
+      options:
+        - label: Yes, I would like to contribute to implementing this feature.
+          required: false

.github/pull_request_template.md

@@ -1,35 +1,83 @@
-## Context
+<!--
+Thank you for contributing to Roo Code!
+
+Before submitting your PR, please ensure:
+- It's linked to an approved GitHub Issue.
+- You've reviewed our [Contributing Guidelines](../CONTRIBUTING.md).
+-->
+
+### Related GitHub Issue
 
-<!-- Brief description of WHAT you’re doing and WHY. -->
+<!-- Every PR MUST be linked to an approved issue. -->
 
-## Implementation
+Closes: # <!-- Replace with the issue number, e.g., Closes: #123 -->
+
+### Description
 
 <!--
+Briefly summarize the changes in this PR and how they address the linked issue.
+The issue should cover the "what" and "why"; this section should focus on:
+- The "how": key implementation details, design choices, or trade-offs made.
+- Anything specific reviewers should pay attention to in this PR.
+-->
 
-Some description of HOW you achieved it. Perhaps give a high level description of the program flow. Did you need to refactor something? What tradeoffs did you take? Are there things in here which you’d particularly like people to pay close attention to?
+### Test Procedure
 
+<!--
+Detail the steps to test your changes. This helps reviewers verify your work.
+- How did you test this specific implementation? (e.g., unit tests, manual testing steps)
+- How can reviewers reproduce your tests or verify the fix/feature?
+- Include relevant testing environment details if applicable.
 -->
 
-## Screenshots
+### Type of Change
 
-| before | after |
-| ------ | ----- |
-|        |       |
+<!-- Mark all applicable boxes with an 'x'. -->
 
-## How to Test
+- [ ] 🐛 **Bug Fix**: Non-breaking change that fixes an issue.
+- [ ] ✨ **New Feature**: Non-breaking change that adds functionality.
+- [ ] 💥 **Breaking Change**: Fix or feature that would cause existing functionality to not work as expected.
+- [ ] ♻️ **Refactor**: Code change that neither fixes a bug nor adds a feature.
+- [ ] 💅 **Style**: Changes that do not affect the meaning of the code (white-space, formatting, etc.).
+- [ ] 📚 **Documentation**: Updates to documentation files.
+- [ ] ⚙️ **Build/CI**: Changes to the build process or CI configuration.
+- [ ] 🧹 **Chore**: Other changes that don't modify `src` or test files.
 
-<!--
+### Pre-Submission Checklist
+
+<!-- Go through this checklist before marking your PR as ready for review. -->
+
+- [ ] **Issue Linked**: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
+- [ ] **Scope**: My changes are focused on the linked issue (one major feature/fix per PR).
+- [ ] **Self-Review**: I have performed a thorough self-review of my code.
+- [ ] **Code Quality**:
+    - [ ] My code adheres to the project's style guidelines.
+    - [ ] There are no new linting errors or warnings (`npm run lint`).
+    - [ ] All debug code (e.g., `console.log`) has been removed.
+- [ ] **Testing**:
+    - [ ] New and/or updated tests have been added to cover my changes.
+    - [ ] All tests pass locally (`npm test`).
+    - [ ] The application builds successfully with my changes.
+- [ ] **Branch Hygiene**: My branch is up-to-date (rebased) with the `main` branch.
+- [ ] **Documentation Impact**: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
+- [ ] **Changeset**: A changeset has been created using `npm run changeset` if this PR includes user-facing changes or dependency updates.
+- [ ] **Contribution Guidelines**: I have read and agree to the [Contributor Guidelines](../CONTRIBUTING.md).
 
-A straightforward scenario of how to test your changes will help reviewers that are not familiar with the part of the code that you are changing but want to see it in action. This section can include a description or step-by-step instructions of how to get to the state of v2 that your change affects.
+### Screenshots / Videos
 
-A "How To Test" section can look something like this:
+<!--
+For UI changes, please provide before-and-after screenshots or a short video of the *actual results*.
+This greatly helps in understanding the visual impact of your changes.
+-->
 
-- Sign in with a user with tracks
-- Activate `show_awesome_cat_gifs` feature (add `?feature.show_awesome_cat_gifs=1` to your URL)
-- You should see a GIF with cats dancing
+### Documentation Updates
 
+<!--
+Does this PR necessitate updates to user-facing documentation?
+- [ ] No documentation updates are required.
+- [ ] Yes, documentation updates are required. (Please describe what needs to be updated or link to a PR in the docs repository).
 -->
 
-## Get in Touch
+### Additional Notes
 
-<!-- We'd love to have a way to chat with you about your changes if necessary. If you're in the [Roo Code Discord](https://discord.gg/roocode), please share your handle here. -->
+<!-- Add any other context, questions, or information for reviewers here. -->

.github/workflows/build-vsix.yml

@@ -0,0 +1,45 @@
+name: Build VSIX
+
+on:
+  pull_request:
+    types: [labeled]
+    branches: [ main ]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    if: github.event.label.name == 'build'
+
+    steps:
+    - name: Checkout code
+      uses: actions/checkout@v4
+
+    - name: Set up Node.js
+      uses: actions/setup-node@v4
+      with:
+        node-version-file: 'package.json'
+        cache: 'npm'
+
+    - name: Install dependencies
+      run: npm ci
+
+    - name: Install all dependencies
+      run: npm run install:all
+
+    - name: Build Extension
+      run: npm run build
+
+    - name: Upload VSIX artifact
+      uses: actions/upload-artifact@v4
+      with:
+        name: extension-vsix
+        path: bin/*.vsix
+
+    - name: Comment PR with artifact link
+      if: github.event_name == 'pull_request'
+      uses: peter-evans/create-or-update-comment@v4
+      with:
+        issue-number: ${{ github.event.pull_request.number }}
+        body: |
+          Build successful! 🚀
+          You can download the VSIX extension [here](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}).

.github/workflows/code-qa.yml

@@ -78,8 +78,10 @@ jobs:
         run: npm run install:all
       - name: Compile (to build and copy WASM files)
         run: npm run compile
-      - name: Run unit tests
+      - name: Run jest unit tests
         run: npx jest --silent
+      - name: Run vitest unit tests
+        run: npx vitest run --silent
 
   test-webview:
     runs-on: ${{ matrix.os }}

.github/workflows/marketplace-publish.yml

@@ -29,9 +29,7 @@ jobs:
           git config user.name "github-actions[bot]"
           git config user.email "github-actions[bot]@users.noreply.github.com"
       - name: Install Dependencies
-        run: |
-          npm install -g vsce ovsx
-          npm run install:all
+        run: npm run install:all
       - name: Create .env file
         run: echo "POSTHOG_API_KEY=${{ secrets.POSTHOG_API_KEY }}" >> .env
       - name: Package Extension

.github/workflows/update-contributors.yml

@@ -14,10 +14,10 @@ jobs:
       pull-requests: write  # Needed for creating PRs
     steps:
       - name: Checkout code
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
 
       - name: Setup Node.js
-        uses: actions/setup-node@v3
+        uses: actions/setup-node@v4
         with:
           node-version: '18'
           cache: 'npm'

.gitignore

@@ -4,6 +4,7 @@ out
 out-*
 node_modules
 coverage/
+mock/
 
 .DS_Store