3.15#165
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
dosubot
Bot
added
the
size:M
![ellipsis-dev[bot]](https://avatars.githubusercontent.com/in/64358?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Caution
Changes requested ❌
Reviewed everything up to 314a51f in 2 minutes and 8 seconds. Click for details.
- Reviewed
88lines of code in4files - Skipped
0files when reviewing. - Skipped posting
7draft 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/update-notes/index.md:1
- Draft comment:
Ensure that the new [3.15] entry is consistently ordered with the other versions. It’s best if the newest release appears at the top consistently. - Reason this comment was not posted:
Confidence changes required:30%<= threshold50%None
2. docs/update-notes/v3.15.md:41
- Draft comment:
Add a newline at the end of the file to comply with file formatting best practices. - Reason this comment was not posted:
Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% While having a trailing newline is a good practice, this kind of formatting issue should be handled automatically by ESLint/Prettier which are required by our standards. The comment is about a purely mechanical formatting issue that should be automated rather than manually reviewed. The comment is technically correct about best practices. Not having a trailing newline could cause issues in some Unix tools. While technically correct, our standards explicitly state that ESLint and Prettier should be set up to handle code style rules automatically. This kind of mechanical formatting feedback should be handled by automation, not manual review. Delete this comment as it addresses a formatting issue that should be handled by automated tools per our development standards.
3. sidebars.ts:169
- Draft comment:
Consider aligning the label for the new version 3.15 entry with the title in the release notes file (e.g., use '3.15 Release Notes' instead of '3.15 Combined') for clarity. - Reason this comment was not posted:
Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% This appears to be a purely cosmetic suggestion that doesn't affect functionality. Looking at the rest of the file, I notice that other version entries use "Combined" consistently (e.g. "3.14 Combined"). This suggests it's an intentional naming pattern, not a mistake. The comment is suggesting a change that would break consistency with the established pattern. I could be wrong about the importance of consistency - maybe the newer format is intentionally different and meant to be clearer. While clarity is important, breaking an established pattern across the codebase would create inconsistency, which could be more confusing for users. The current label matches the pattern used throughout the file. The comment should be deleted as it suggests breaking an established naming pattern without clear benefit.
4. .roomodes:23
- Draft comment:
Updated the customInstructions for the Release Notes Writer. The new guidelines remove the 'Highlights' header and specify sections like 'QOL Improvements' and 'Misc Improvements'. Ensure that release note files later follow these specific headings consistently. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%This comment is purely informative, providing details about changes to the release notes guidelines. It doesn't suggest any code changes or improvements, nor does it ask for tests or confirmation of intentions. It violates the rule against making purely informative comments.
5. docs/update-notes/v3.15.md:1
- Draft comment:
The new release note for version 3.15 is well structured. Verify that all section headings align with the updated guidelines in customInstructions. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%This comment is asking the PR author to verify alignment with guidelines, which is against the rules. It doesn't provide a specific code suggestion or point out a specific issue in the code.
6. sidebars.ts:169
- Draft comment:
A new sidebar category for release notes version 3.15 has been added. Confirm that the doc id 'update-notes/v3.15' and label '3.15 Combined' are correct and consistent with naming conventions used elsewhere. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%The comment is asking the PR author to confirm the correctness and consistency of a doc id and label, which violates the rule against asking the author to confirm or double-check things. It doesn't provide a specific suggestion or point out a clear issue.
7. .roomodes:7
- Draft comment:
In the Documentation Writer's customInstructions, the markdown code block example (starting withmd) appears to be missing a closing triple backtick. It would be clearer and ensure proper formatting if a closingis added. - 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.
Workflow ID: wflow_EbXOD5tVn8FRzmUD
You can customize 
| @@ -1,3 +1,4 @@ | |||
| - [3.15](/update-notes/v3.15) (2025-04-30) | |||
Contributor
There was a problem hiding this comment.
A new 3.15 entry is added above the header. Consider grouping it under its own version header for consistency with other versions.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Important
Add release notes and sidebar updates for Roo Code version 3.15, introducing new features and improvements.
v3.15.mdwith new features like prompt caching for Google Vertex, improved terminal command handling, and UI/UX enhancements.index.mdto include version 3.15.sidebars.tsto include a new category for version 3.15 under 'Update Notes'..roomodesto update release note standards, removing## Highlightsand adding## QOL Improvementsand## Misc Improvements.This description was created by
for 314a51f. You can customize this summary. It will automatically update as commits are pushed.