chore: add changeset for v3.25.9 #6809
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 | ||
| --- | ||
|
|
||
| - Fix: Resolve rounding issue with max tokens (#6806 by @markp018, PR by @mrubens) | ||
| - Add support for GLM-4.5 and OpenAI gpt-oss models in Fireworks provider (#6753 by @alexfarlander, PR by @app/roomote) | ||
| - Improve UX by focusing chat input when clicking plus button in extension menu (thanks @app/roomote!) | ||
|
Contributor
There was a problem hiding this comment. Is there an associated issue number for this UX improvement? Including it would help with traceability, similar to the other entries. |
||
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.
Consider using a consistent attribution format across all entries. Currently we have:
(#6806 by @markp018, PR by @mrubens)(#6753 by @alexfarlander, PR by @app/roomote)(thanks @app/roomote!)Perhaps standardize to something like
(#issue by @author, PR by @pr-author)for all entries?