-
Notifications
You must be signed in to change notification settings - Fork 2.5k
chore: add changeset for v3.25.3 #6435
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,14 @@ | ||
| --- | ||
| "roo-cline": patch | ||
| --- | ||
|
|
||
| - Fix: Prevent input clearing when clicking chat buttons (thanks @hassoncs!) | ||
| - Increase Claude Code default max output tokens to 16k (#6125 by @bpeterson1991, PR by @app/roomote) | ||
|
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. Is this the preferred format for including both issue references and contributor credits in the same line? Other entries separate these concerns - should we follow a consistent pattern? |
||
| - Update PR reviewer rules and mode configuration (thanks @daniel-lxs!) | ||
| - Add translation check action to pull_request.opened event (thanks @app/roomote!) | ||
| - Add docs link for slash commands | ||
| - Allow queueing images | ||
| - Hide Gemini checkboxes on the welcome view | ||
| - Remove "(prev Roo Cline)" from extension title in all languages (thanks @app/roomote!) | ||
| - Remove event types mention from PR reviewer rules (thanks @daniel-lxs!) | ||
| - Clarify apply_diff tool descriptions to emphasize surgical edits | ||
|
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. Should all changelog entries follow the same punctuation pattern? Most entries don't end with periods, but consistency would improve readability. |
||
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.
Could we standardize the formatting style for consistency? Some entries start with action prefixes like "Fix:", "Update", "Add" while others don't. Is there a preferred format for changelog entries in this project?