docs: Update release notes for versions 3.15.0 and 3.15.1, add new im…

[hannesrudolph]

…ages, and enhance code actions documentation

---

Important

Update release notes for versions 3.15.0 and 3.15.1, enhance code actions and shell integration documentation, and update sidebar configuration.

• Release Notes:
  • Added release notes for versions 3.15.0 and 3.15.1 in docs/update-notes/v3.15.0.md and docs/update-notes/v3.15.1.md.
  • Updated docs/update-notes/index.md to include links to 3.15.0 and 3.15.1.
• Documentation Enhancements:
  • Updated docs/features/code-actions.md to include filename in "Add to Context" action and removed redundant task options.
  • Enhanced docs/features/shell-integration.md with new command execution fallback mechanism and stop command button image.
• Sidebar Configuration:
  • Updated sidebars.ts to include new release notes for 3.15.0 and 3.15.1.

^{This description was created by for d377259. You can customize this summary. It will automatically update as commits are pushed.}

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
roo-code-docs	🔄 Building (Inspect)	Visit Preview	💬 Add feedback	Apr 30, 2025 9:58pm

[ellipsis-dev]

Caution

Changes requested ❌

Reviewed everything up to d377259 in 2 minutes and 32 seconds. Click for details.

• Reviewed 232 lines of code in 7 files
• Skipped 5 files when reviewing.
• Skipped posting 11 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. docs/features/code-actions.md:19

• Draft comment:
  Good clarification: including the filename improves context clarity.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

2. docs/features/code-actions.md:20

• Draft comment:
  Removal of the 'Fix Code' action; ensure this removal is intentional and documented in feature updates.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is asking the PR author to ensure the removal is intentional and documented, which violates the rule against asking for confirmation or documentation updates. It doesn't provide a specific code suggestion or highlight a potential issue directly related to the code itself.

3. docs/update-notes/v3.15.1.md:9

• Draft comment:
  Typo: replace 'intigrated' with 'integrated'.
• Reason this comment was not posted:
  Marked as duplicate.

4. sidebars.ts:172

• Draft comment:
  New update note entries for 3.15.1 and 3.15.0 are added; confirm that their order aligns with the intended release sequence.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is asking the PR author to confirm the order of update note entries, which violates the rule against asking for confirmation of intentions or ensuring behavior is intended. It does not provide a specific code suggestion or request for tests, nor does it align with any of the additional rules provided.

5. docs/features/shell-integration.md:38

• Draft comment:
  Verify that the fallback mechanism screenshot (/img/v3.15.0/v3.15.0.png) accurately reflects the current UI.
• Reason this comment was not posted:
  Confidence changes required: 50% <= threshold 50% None

6. docs/features/shell-integration.md:45

• Draft comment:
  The description for 'Terminal Output Limit' is repeated (lines 47 and 48). Consider removing or merging the duplicate text for clarity.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

7. docs/features/shell-integration.md:20

• Draft comment:
  The 'Troubleshooting Shell Integration' section header appears twice (at line 20 and then again at line 125). This duplicate header could confuse readers. Consider consolidating them into one section or renaming one of them.
• Reason this comment was not posted:
  Comment was on unchanged code.

8. docs/features/shell-integration.md:72

• Draft comment:
  The info block marker '::::info Important' at line 72 seems non-standard; typically, such blocks use ':::info'. Please verify if the extra colon is intentional or a typo.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

9. docs/update-notes/v3.15.1.md:9

• Draft comment:
  Typographical error: 'intigrated' should be corrected to 'integrated'.
• Reason this comment was not posted:
  Marked as duplicate.

10. docs/update-notes/v3.15.md:14

• Draft comment:
  The image path in this line uses '/img/v3.15.0/v3.15.0-2.png', while later in the file, the image path uses '/img/v3.15/v3.15-1.png'. Consider using a consistent version naming convention (e.g., either 'v3.15.0' or 'v3.15') for clarity and consistency.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 20% vs. threshold = 50% While the comment identifies a real inconsistency, this is a documentation file and the images likely already exist at their respective paths. Changing the path would require moving/renaming actual image files, which we can't see in this PR. The inconsistency is minor and doesn't affect functionality. The comment also makes assumptions about which format is "better" without knowing the project's conventions. The inconsistency could reflect an actual organization scheme where some images use semantic versioning (3.15.0) and others use short versions (3.15) for a reason. Without seeing the full image directory structure, we can't be certain this is actually a problem. Even if there is a reason for the different formats, having inconsistent paths in the same documentation file could be confusing for future maintainers. The comment should be deleted. While it points out a real inconsistency, changing image paths requires moving files we can't see, and the inconsistency might be intentional or harmless.

11. docs/update-notes/v3.15.md:28

• Draft comment:
  The image path in this line is '/img/v3.15/v3.15-1.png', which differs from the earlier image path in this release note file that uses 'v3.15.0'. To avoid confusion, please ensure that the version folder naming is consistent throughout the document.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 20% vs. threshold = 50% While the comment identifies a real inconsistency, this is a documentation file and the paths likely work fine as they are. The inconsistency is minor and doesn't affect functionality. According to the rules, we should not make purely informative comments or comments that are unimportant. Path consistency in documentation, while nice to have, is not a critical issue requiring immediate action. The inconsistent paths could potentially cause confusion for future maintainers or make it harder to programmatically process image references. It could be a valid maintenance concern. While path consistency is good practice, this is a minor documentation issue that doesn't affect functionality or maintainability significantly. The rules explicitly state not to make purely informative comments. The comment should be deleted as it's primarily informative and doesn't highlight a significant issue requiring action.

Workflow ID: wflow_KcgGViquaLMq7r8K

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[ellipsis-dev]

Typo: "intigrated" should be "integrated".

Suggested change

	* Fixed the new intigrated terminal to capture stderr in execa-spawned processes.
	* Fixed the new integrated terminal to capture stderr in execa-spawned processes.

[ellipsis-dev]

Typo: The image source on line 30 uses '/img/v3.15/v3.15-1.png'. Consider changing it to '/img/v3.15.0/v3.15.0-1.png' for consistency with the rest of the release notes.

Suggested change

	<img src="/img/v3.15/v3.15-1.png" width="350" />
	<img src="/img/v3.15.0/v3.15.0-1.png" width="350" />