mirror of
https://github.com/RooVetGit/Roo-Code.git
synced 2026-08-28 05:27:24 +00:00
Release v3.25.11 (#6952)
This commit is contained in:
parent
b30372d5ca
commit
6cc4b20bf3
2 changed files with 12 additions and 1 deletions
11
.changeset/v3.25.11.md
Normal file
11
.changeset/v3.25.11.md
Normal file
|
|
@ -0,0 +1,11 @@
|
|||
---
|
||||
"roo-cline": patch
|
||||
---
|
||||
|
||||
- Fix: Token usage and cost often being underreported (thanks @chrarnoldus!)
|
||||
- Add: Native OpenAI provider support for Codex Mini model (#5386 by @KJ7LNW, PR by @daniel-lxs)
|
||||
- Add: IO Intelligence Provider support (thanks @ertan2002!)
|
||||
- Fix: MCP startup issues and remove refresh notifications (thanks @hannesrudolph!)
|
||||
- Fix: GPT5 OpenAI provider configuration (thanks @hannesrudolph!)
|
||||
- Fix: Clarify codebase_search path parameter as optional and improve tool descriptions (thanks @app/roomote!)
|
||||
- Fix: Bedrock provider workaround for LiteLLM passthrough issues (thanks @jr!)
|
||||
|
|
@ -4,7 +4,7 @@ argument-hint: patch | minor | major
|
|||
---
|
||||
|
||||
1. Identify the SHA corresponding to the most recent release using GitHub CLI: `gh release view --json tagName,targetCommitish,publishedAt`
|
||||
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)'`
|
||||
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)'`
|
||||
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}'`
|
||||
4. Summarize the changes. If the user did not specify, ask them whether this should be a major, minor, or patch release.
|
||||
5. Create a changeset in .changeset/v[version].md instead of directly modifying package.json. The format is:
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue