Skip to content
Merged
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
7 changes: 7 additions & 0 deletions .changeset/v3.25.6.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
---
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Is this filename convention intentional for release PRs? Typically changesets use descriptive names like rather than version numbers. Just curious if this is a special pattern for release preparation!

"roo-cline": patch
---

- Add support for syncing provider profiles from the cloud (thanks @jr!)
Copy link
Contributor Author

Choose a reason for hiding this comment

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

The attribution is great, but it might be helpful to clarify which contributor worked on which feature. For example:

  • Cloud sync support (@jr)
  • Horizon-beta token limit (@hannesrudolph, @app/roomote)
  • Types package bump (@app/roomote)

This would make the changelog more informative for users checking who to thank for specific features.

- Set horizon-beta model max tokens to 32k for OpenRouter (requested by @hannesrudolph, PR by @app/roomote)
- Bump @roo-code/types to v1.41.0 (thanks @app/roomote!)
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I notice this PR only contains the changeset file. Are the actual implementations for these three features already merged to main? If so, this follows the standard changeset workflow perfectly. If not, should we expect those changes to be added to this PR?

Loading