-
Notifications
You must be signed in to change notification settings - Fork 2.6k
chore: add changeset for v3.25.18 #7223
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,9 @@ | ||
| --- | ||
| "roo-cline": patch | ||
| --- | ||
|
|
||
| - Fix: respect enableReasoningEffort setting when determining reasoning usage (#7048 by @ikbencasdoei, PR by @app/roomote) | ||
| - Fix: prevent duplicate LM Studio models with case-insensitive deduplication (#6954 by @fbuechler, PR by @daniel-lxs) | ||
| - Add support for Sonic model (thanks @mrubens!) | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. These feature entries don't include issue or PR references like the fixes above do. Including references (if they exist) would help with traceability. For instance:
|
||
| - Feat: simplify ask_followup_question prompt documentation (thanks @daniel-lxs!) | ||
| - Feat: simple read_file tool for single-file-only models (thanks @daniel-lxs!) | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Consider adding more context to this feature description? For example, what specific use case does this enable or what problem does it solve for single-file-only models? This would help users understand the value of this addition. |
||
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.
I noticed the attribution format varies between entries. The first two use "by @username, PR by @app/roomote" while the last three use "thanks @username!". Would it be better to standardize this for consistency?
For example, all entries could follow either:
What do you think?