chore: add changeset for v3.25.23 #7338
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,7 @@ | ||
| --- | ||
| "roo-cline": patch | ||
| --- | ||
|
|
||
| - feat: add custom base URL support for Requesty provider (#7274 by @requesty-JohnCosta27, PR by @daniel-lxs) | ||
|
Contributor
There was a problem hiding this comment. Could we consider a more concise attribution format for future changesets? For example: instead of the current format. This would make the changeset entries more readable while still giving proper credit. |
||
| - feat: add DeepSeek V3.1 model to Chutes AI provider (#7294 by @dmarkey, PR by @app/roomote) | ||
| - Revert "feat: enable loading Roo modes from multiple files in .roo/roo_modes directory" (thanks @hannesrudolph!) | ||
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is using the version number as the changeset filename intentional? Typically, changesets use random adjective-noun combinations (like ) to avoid conflicts and follow the standard changeset conventions. This might be worth considering for future changesets to ensure compatibility with changeset tooling.