Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions .changeset/v3.26.5.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
---
Copy link
Contributor

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 randomly generated names (e.g., 'brave-pandas-dance.md') to avoid conflicts when multiple changesets are created for the same version. This approach might work for release changesets, but wanted to check if this follows your established pattern.

"roo-cline": patch
---

![3.26.5 Release - Enhanced AI Thinking Capabilities](/releases/3.26.5-release.png)

- feat: Add support for Qwen3 235B A22B Thinking 2507 model in chutes (thanks @mohammad154!)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we standardize the attribution format for better consistency? I notice some entries use 'thanks @username!' while others use 'by @username, PR by @username'. A consistent format would make the changelog more uniform.

- feat: Add auto-approve support for MCP access_resource tool (#7565 by @m-ibm, PR by @daniel-lxs)
- feat: Add configurable embedding batch size for code indexing (#7356 by @BenLampson, PR by @app/roomote)
- fix: Add cache reporting support for OpenAI-Native provider (thanks @hannesrudolph!)
- feat: Move message queue to the extension host for better performance (thanks @cte!)
Binary file added releases/3.26.5-release.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading