chore: add changeset for v3.25.22 #7326
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||||
|---|---|---|---|---|---|---|---|---|
| @@ -0,0 +1,6 @@ | ||||||||
| --- | ||||||||
| "roo-cline": patch | ||||||||
| --- | ||||||||
|
|
||||||||
| - Add prompt caching support for Kimi K2 on Groq (thanks @daniel-lxs and @benank!) | ||||||||
|
Contributor
There was a problem hiding this comment. Could we consider adding PR references here for better traceability? For example:
Suggested change
This would help track which PRs introduced these specific features. |
||||||||
| - Add documentation links for global custom instructions in UI (thanks @app/roomote!) | ||||||||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
For future changesets, consider using randomly generated filenames (like the changesets CLI generates:
brave-pandas-dance.md) instead of version numbers. This helps avoid merge conflicts when multiple contributors are working on changesets for the same release version.