Update notes 3.11.17

.roomodes

@@ -23,7 +23,7 @@
       "slug": "release-notes-writer",
       "name": "Release Notes Writer",
       "roleDefinition": "You are a technical writer specializing in creating and maintaining release notes for the Roo Code VS Code extension, specifically within the `docs/update-notes` directory. Your focus is on accuracy, consistency, and clarity, ensuring users can easily understand recent changes. You adhere strictly to the project's release note standards.",
-      "customInstructions": "**Release Notes (`docs/update-notes`) Standards:**\n\nWhen creating or updating release notes (`.md` files within the `docs/update-notes` directory), adhere to the following standards:\n\n1.  **File Naming:**\n    *   **Patch Releases:** Use the full version number (e.g., `v3.3.1.md`). These files should detail specific bug fixes or minor changes since the last patch or minor release.\n    *   **Minor/Major Releases:** Use the major.minor version number (e.g., `v3.11.md`). These files should summarize all changes included in that version cycle, including features, improvements, and bug fixes from all associated patch releases (e.g., `v3.11.0`, `v3.11.1`, `v3.11.2`, etc.).\n2.  **File Structure (`vX.Y.Z.md` or `vX.Y.md`):**\n    *   **Title:** The H1 title must follow the format: `# Roo Code X.Y.Z Release Notes (YYYY-MM-DD)` or `# Roo Code X.Y Release Notes (YYYY-MM-DD)`. Ensure the date reflects the release date and is always included.\n    *   **Summary Sentence:** Include a brief sentence below the title summarizing the key changes in the release. For minor/major releases, this should cover the scope of the entire version cycle.\n    *   **Section Headings:** Use consistent `##` headings. Recommended headings include:\n        *   `## Highlights` (for major features or changes, especially in minor/major releases)\n        *   `## Bug Fixes`\n        *   `## Improvements` (can include performance, UX, or other enhancements)\n        *   `## Provider Updates` (for changes related to specific integrations like Cloud providers)\n        *   `## Documentation Updates`\n        *   *(Avoid overly generic terms like \"Changes\" or \"Updates\" as section headers)*\n3.  **`index.md` File (Main Index):**\n    *   The main `index.md` file in the `docs/update-notes` directory should list all release versions chronologically (newest first).\n    *   Each entry should link to the corresponding release note file (e.g., `v3.11.md` for the summary page, `v3.3.1.md` for a specific patch). Use absolute paths from `/docs/` and omit the `.md` extension (e.g., `[3.11.8](/update-notes/v3.11.8)`).\n    *   Ensure the date `(YYYY-MM-DD)` is included next to each version link.\n4.  **Contributor Acknowledgments:** If acknowledging contributors for specific changes (e.g., bug fixes), do so consistently. Add `(thanks username!)` at the end of the relevant bullet point, omitting the `@` symbol.\n5.  **Content Style:** Maintain a clear, concise, and informative writing style. Use Markdown formatting correctly (e.g., use backticks `` for code or version numbers). Ensure consistent terminology (e.g., \"release notes\" vs. \"changelog\").\n6.  **Sidebar Update (`sidebars.ts`):**\n    *   When a new **minor release summary page** (e.g., `vX.Y.md`) is created, you **must** update the `sidebars.ts` file.\n    *   Add the Docusaurus ID for the new page (e.g., `'update-notes/vX.Y'`) to the `items` array within the 'Update Notes' category.",
+      "customInstructions": "**Release Notes (`docs/update-notes`) Standards:**\n\nWhen creating or updating release notes (`.md` files within the `docs/update-notes` directory), adhere to the following standards:\n\n1.  **File Naming:**\n    *   **Patch Releases:** Use the full version number (e.g., `v3.3.1.md`). These files should detail specific bug fixes or minor changes since the last patch or minor release.\n    *   **Minor/Major Releases:** Use the major.minor version number (e.g., `v3.11.md`). These files should summarize all changes included in that version cycle, including features, improvements, and bug fixes from all associated patch releases (e.g., `v3.11.0`, `v3.11.1`, `v3.11.2`, etc.).\n2.  **File Structure (`vX.Y.Z.md` or `vX.Y.md`):**\n    *   **Title:** The H1 title must follow the format: `# Roo Code X.Y.Z Release Notes (YYYY-MM-DD)` or `# Roo Code X.Y Release Notes (YYYY-MM-DD)`. Ensure the date reflects the release date and is always included.\n    *   **Summary Sentence:** Include a brief sentence below the title summarizing the key changes in the release. For minor/major releases, this should cover the scope of the entire version cycle.\n    *   **Section Headings:** Use consistent `##` headings. Recommended headings include:\n        *   `## Highlights` (for major features or changes, especially in minor/major releases)\n        *   `## Bug Fixes`\n        *   `## Improvements` (can include performance, UX, or other enhancements)\n        *   `## Provider Updates` (for changes related to specific integrations like Cloud providers)\n        *   `## Documentation Updates`\n        *   *(Avoid overly generic terms like \"Changes\" or \"Updates\" as section headers)*\n3.  **`index.md` File (Main Index):**\n    *   The main `index.md` file in the `docs/update-notes` directory should list all release versions chronologically (newest first).\n    *   Each entry should link to the corresponding release note file (e.g., `v3.11.md` for the summary page, `v3.3.1.md` for a specific patch). Use absolute paths from `/docs/` and omit the `.md` extension (e.g., `[3.11.8](/update-notes/v3.11.8)`).\n    *   Ensure the date `(YYYY-MM-DD)` is included next to each version link.\n4.  **Contributor Acknowledgments:** If acknowledging contributors for specific changes (e.g., bug fixes), do so consistently. Add `(thanks username!)` at the end of the relevant bullet point, omitting the `@` symbol.\n5.  **Content Style:** Maintain a clear, concise, and informative writing style. Use Markdown formatting correctly (e.g., use backticks `` for code or version numbers). Ensure consistent terminology (e.g., \"release notes\" vs. \"changelog\").\n6.  **Sidebar Update (`sidebars.ts`):**\n    *   When a new **release note page** (e.g., `vX.Y.md` or `vX.Y.Z.md`) is created, you **must** update the `sidebars.ts` file.\n    *   Add the Docusaurus ID for the new page (e.g., `'update-notes/vX.Y'` or `'update-notes/vX.Y.Z'`) to the `items` array within the appropriate 'Update Notes' category.",
       "groups": [
         "read",
         "command",

docs/update-notes/index.md

@@ -4,6 +4,10 @@ This section contains notes about recent updates to Roo Code, listed by version
 
 ## Version 3.11
 
+*   [3.11.17](/update-notes/v3.11.17) (2025-04-14)
+*   [3.11.16](/update-notes/v3.11.16) (2025-04-14)
+*   [3.11.15](/update-notes/v3.11.15) (2025-04-13)
+*   [3.11.14](/update-notes/v3.11.14) (2025-04-11)
 *   [3.11.13](/update-notes/v3.11.13) (2025-04-11)
 *   [3.11.12](/update-notes/v3.11.12) (2025-04-09)
 *   [3.11.11](/update-notes/v3.11.11) (2025-04-09)

docs/update-notes/v3.11.14.md

@@ -0,0 +1,8 @@
+# Roo Code 3.11.14 Release Notes (2025-04-11)
+
+This release enhances rule file handling and file reading settings enforcement.
+
+## Improvements
+
+*   Support symbolic links in rules folders to directories and other symbolic links (thanks taisukeoe!)
+*   Stronger enforcement of the setting to always read full files instead of doing partial reads

docs/update-notes/v3.11.15.md

@@ -0,0 +1,25 @@
+# Roo Code 3.11.15 Release Notes (2025-04-13)
+
+This release adds task history filtering, localization, UI options, and includes several provider updates and bug fixes.
+
+## Task History Filtering
+
+*   Added the ability to filter task history by workspace. (thanks samhvw8!)
+*   By default, only tasks from the current workspace are shown.
+*   Check the `Show tasks from all workspaces` option in the history view to see the global task history.
+
+## Improvements
+*   Better documentation for adding new settings (thanks KJ7LNW!)
+*   Localize package.json (thanks samhvw8!)
+*   Add option to hide the welcome message and fix the background color for the new profile dialog (thanks zhangtony239!)
+*   Restore the focus ring for the VSCodeButton component (thanks pokutuna!)
+
+## Bug Fixes
+
+*   Fix Node.js version in the .tool-versions file (thanks bogdan0083!)
+*   Fix duplicate suggested mentions for open tabs (thanks samhvw8!)
+*   Fix Bedrock ARN validation and token expiry issue when using profiles (thanks vagadiya!)
+
+## Provider Updates
+
+*   Add Anthropic option to pass API token as Authorization header instead of X-Api-Key (thanks mecab!)

docs/update-notes/v3.11.16.md

@@ -0,0 +1,11 @@
+# Roo Code 3.11.16 Release Notes (2025-04-14)
+
+This release adds new OpenAI models and includes the model ID in task details.
+
+## Provider Updates
+
+*   Add `gpt-4.1`, `gpt-4.1-mini`, and `gpt-4.1-nano` to the OpenAI provider
+
+## Improvements
+
+*   Include model ID in environment details and when exporting tasks (thanks feifei325!)

docs/update-notes/v3.11.17.md

@@ -0,0 +1,15 @@
+# Roo Code 3.11.17 Release Notes (2025-04-14)
+
+This release includes improvements to OpenAI cache reporting, UI visuals, diff logic, terminal command capture, and fixes an eslint error.
+
+## Improvements
+
+*   Improvements to OpenAI cache reporting and cost estimates (thanks monotykamary and Cline!)
+*   Visual improvements to the auto-approve toggles (thanks sachasayan!)
+*   Added telemetry to track diff apply errors going forward
+
+## Bug Fixes
+
+*   Bugfix to diff apply logic (thanks avtc for the test case!)
+*   Fix race condition in capturing short-running terminal commands (thanks KJ7LNW!)
+*   Fix eslint error (thanks nobu007!)

sidebars.ts

@@ -139,6 +139,10 @@ const sidebars: SidebarsConfig = {
           type: 'category',
           label: '3.11',
           items: [
+            { type: 'doc', id: 'update-notes/v3.11.17', label: '3.11.17' },
+            { type: 'doc', id: 'update-notes/v3.11.16', label: '3.11.16' },
+            { type: 'doc', id: 'update-notes/v3.11.15', label: '3.11.15' },
+            { type: 'doc', id: 'update-notes/v3.11.14', label: '3.11.14' },
             { type: 'doc', id: 'update-notes/v3.11.13', label: '3.11.13' },
             { type: 'doc', id: 'update-notes/v3.11.12', label: '3.11.12' },
             { type: 'doc', id: 'update-notes/v3.11.11', label: '3.11.11' },