Skip to content

chore: add changeset for v3.25.19 #7242

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Aug 20, 2025
Merged

chore: add changeset for v3.25.19 #7242

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
5 changes: 5 additions & 0 deletions .changeset/v3.25.19.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
Copy link
Contributor

@roomote roomote bot Aug 20, 2025

Choose a reason for hiding this comment

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

I noticed this changeset uses the version number as the filename. Could we consider using the standard changeset naming convention instead? Typically, changesets use randomly generated names (like brave-pandas-dance.md) to avoid potential conflicts when multiple changesets need to be included in the same release.

You could rename this using:

mv .changeset/v3.25.19.md .changeset/add-roo-provider.md

Or generate a standard name with:

npx changeset

This would help maintain consistency with the changeset workflow and prevent any issues if additional fixes need to be included in v3.25.19.

"roo-cline": patch
---

- Fix: Add 'roo' provider to checkExistKey function (thanks @daniel-lxs!)
Loading