Skip to content

Commit 6cc4b20

Browse files
authored
Release v3.25.11 (#6952)
1 parent b30372d commit 6cc4b20

File tree

2 files changed

+12
-1
lines changed

2 files changed

+12
-1
lines changed

.changeset/v3.25.11.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
---
2+
"roo-cline": patch
3+
---
4+
5+
- Fix: Token usage and cost often being underreported (thanks @chrarnoldus!)
6+
- Add: Native OpenAI provider support for Codex Mini model (#5386 by @KJ7LNW, PR by @daniel-lxs)
7+
- Add: IO Intelligence Provider support (thanks @ertan2002!)
8+
- Fix: MCP startup issues and remove refresh notifications (thanks @hannesrudolph!)
9+
- Fix: GPT5 OpenAI provider configuration (thanks @hannesrudolph!)
10+
- Fix: Clarify codebase_search path parameter as optional and improve tool descriptions (thanks @app/roomote!)
11+
- Fix: Bedrock provider workaround for LiteLLM passthrough issues (thanks @jr!)

.roo/commands/release.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ argument-hint: patch | minor | major
44
---
55

66
1. Identify the SHA corresponding to the most recent release using GitHub CLI: `gh release view --json tagName,targetCommitish,publishedAt`
7-
2. Analyze changes since the last release using: `gh pr list --state merged --json number,title,author,url,mergedAt,closingIssuesReferences --limit 1000 -q '[.[] | select(.mergedAt > "TIMESTAMP") | {number, title, author: .author.login, url, mergedAt, issues: .closingIssuesReferences}] | sort_by(.number)'`
7+
2. Analyze changes since the last release using: `gh pr list --state merged --base main --json number,title,author,url,mergedAt,closingIssuesReferences --limit 1000 -q '[.[] | select(.mergedAt > "TIMESTAMP") | {number, title, author: .author.login, url, mergedAt, issues: .closingIssuesReferences}] | sort_by(.number)'`
88
3. For each PR with linked issues, fetch the issue details to get the issue reporter: `gh issue view ISSUE_NUMBER --json number,author -q '{number, reporter: .author.login}'`
99
4. Summarize the changes. If the user did not specify, ask them whether this should be a major, minor, or patch release.
1010
5. Create a changeset in .changeset/v[version].md instead of directly modifying package.json. The format is:

0 commit comments

Comments
 (0)