Merge branch 'main' into cte/monorepo

Author: cte

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -5,32 +5,32 @@ body:
   - type: markdown
     attributes:
       value: |
-        **Thank you for taking the time to fill out this bug report!**
+        **Thanks for your report!** Please check existing issues first:  
+        👉 https://github.com/RooVetGit/Roo-Code/issues
 
-        Please ensure this bug hasn't been reported already by searching existing [GitHub Issues](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:
         - Anthropic
         - AWS Bedrock
         - Chutes AI
         - DeepSeek
         - Glama
         - Google Gemini
+        - Google Vertex AI
         - Groq
         - Human Relay Provider
+        - LiteLLM
         - LM Studio
         - Mistral AI
         - Ollama
@@ -49,44 +49,38 @@ body:
     id: model
     attributes:
       label: Model Used
-      description: Clearly specify the exact model (e.g., Claude 3.7 Sonnet). If not applicable, enter N/A.
-    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 or Error Logs
-      description: Paste relevant API logs, console outputs, or error messages 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/pull_request_template.md

@@ -3,7 +3,7 @@ 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).
+- You've reviewed our [Contributing Guidelines](../CONTRIBUTING.md).
 -->
 
 ### Related GitHub Issue
@@ -61,7 +61,7 @@ Detail the steps to test your changes. This helps reviewers verify your work.
 - [ ] **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).
+- [ ] **Contribution Guidelines**: I have read and agree to the [Contributor Guidelines](../CONTRIBUTING.md).
 
 ### Screenshots / Videos
 

CHANGELOG.md

@@ -1,5 +1,16 @@
 # Roo Code Changelog
 
+## [3.16.6] - 2025-05-12
+
+- Restore "Improve provider profile management in the external API"
+- Fix to subtask sequencing (thanks @wkordalski!)
+- Fix webview terminal output processing error (thanks @KJ7LNW!)
+- Fix textarea empty string fallback logic (thanks @elianiva!)
+
+## [3.16.5] - 2025-05-10
+
+- Revert "Improve provider profile management in the external API" until we track down a bug with defaults
+
 ## [3.16.4] - 2025-05-09
 
 - Improve provider profile management in the external API

CONTRIBUTING.md

@@ -12,12 +12,9 @@ This guide outlines how to contribute to Roo Code, whether you're fixing bugs, a
 - [I. Before You Contribute](#i-before-you-contribute)
     - [1. Code of Conduct](#1-code-of-conduct)
     - [2. Understand the Project Roadmap](#2-understand-the-project-roadmap)
-        - [Provider Support](#provider-support)
-        - [Model Support](#model-support)
-        - [System Support](#system-support)
-        - [Documentation](#documentation)
-        - [Stability](#stability)
-        - [Internationalization](#internationalization)
+        - [Reliability First](#reliability-first)
+        - [Enhanced User Experience](#enhanced-user-experience)
+        - [Leading on Agent Performance](#leading-on-agent-performance)
     - [3. Join the Roo Code Community](#3-join-the-roo-code-community)
 - [II. Finding & Planning Your Contribution](#ii-finding--planning-your-contribution)
     - [1. Types of Contributions](#1-types-of-contributions)
@@ -56,55 +53,25 @@ Roo Code has a clear development roadmap that guides our priorities and future d
 - Understand the context behind certain design decisions
 - Find inspiration for new features that support our vision
 
-Our current roadmap focuses on six key pillars:
+We're focused on making Roo Code the top choice for developers building with AI-driven coding tools. Here's how we'll get there:
 
-#### Provider Support
+#### Reliability First
 
-We aim to support as many providers well as we can:
+- Ensure diff editing and command execution are consistently reliable.
+- Reduce friction points that deter regular usage.
+- Guarantee smooth operation across all locales and platforms.
+- Expand robust support for a wide variety of AI providers and models.
 
-- More versatile "OpenAI Compatible" support
-- xAI, Microsoft Azure AI, Alibaba Cloud Qwen, IBM Watsonx, Together AI, DeepInfra, Fireworks AI, Cohere, Perplexity AI, FriendliAI, Replicate
-- Enhanced support for Ollama and LM Studio
+#### Enhanced User Experience
 
-#### Model Support
+- Streamline the UI/UX for clarity and intuitiveness.
+- Continuously improve the workflow to meet the high expectations developers have for daily-use tools.
 
-We want Roo to work as well on as many models as possible, including local models:
+#### Leading on Agent Performance
 
-- Local model support through custom system prompting and workflows
-- Benchmarking evals and test cases
-
-#### System Support
-
-We want Roo to run well on everyone's computer:
-
-- Cross platform terminal integration
-- Strong and consistent support for Mac, Windows, and Linux
-
-#### Documentation
-
-We want comprehensive, accessible documentation for all users and contributors:
-
-- Expanded user guides and tutorials
-- Clear API documentation
-- Better contributor guidance
-- Multilingual documentation resources
-- Interactive examples and code samples
-
-#### Stability
-
-We want to significantly decrease the number of bugs and increase automated testing:
-
-- Debug logging switch
-- "Machine/Task Information" copy button for sending in with bug/support requests
-
-#### Internationalization
-
-We want Roo to speak everyone's language:
-
-- 我们希望 Roo Code 说每个人的语言
-- Queremos que Roo Code hable el idioma de todos
-- हम चाहते हैं कि Roo Code हर किसी की भाषा बोले
-- نريد أن يتحدث Roo Code لغة الجميع
+- Establish comprehensive evaluation benchmarks (evals) to measure real-world productivity.
+- Make it easy for everyone to easily run and interpret these evals.
+- Ship improvements to Roo Code that demonstrate clear increases in eval scores.
 
 We especially welcome contributions that advance our roadmap goals. If you're working on something that aligns with these pillars, please mention it in your PR description.
 

evals/apps/web/package.json

@@ -31,7 +31,7 @@
 		"clsx": "^2.1.1",
 		"cmdk": "^1.1.0",
 		"fuzzysort": "^3.1.0",
-		"lucide-react": "^0.479.0",
+		"lucide-react": "^0.510.0",
 		"next": "15.2.2",
 		"next-themes": "^0.4.6",
 		"p-map": "^7.0.3",

evals/packages/db/package.json

@@ -22,7 +22,7 @@
 	"dependencies": {
 		"@evals/types": "workspace:^",
 		"@libsql/client": "^0.15.0",
-		"drizzle-orm": "^0.40.0",
+		"drizzle-orm": "^0.43.0",
 		"drizzle-zod": "^0.7.0",
 		"p-map": "^7.0.3",
 		"zod": "^3.24.2"