-
Notifications
You must be signed in to change notification settings - Fork 2.6k
chore: bump @roo-code/types to v1.41.0 #6568
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.
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,6 @@ | ||
| { | ||
| "name": "@roo-code/types", | ||
| "version": "1.40.0", | ||
| "version": "1.41.0", | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Since this is a minor version bump (1.40.0 → 1.41.0), it would be helpful to understand what new features or changes are included. The PR description mentions this was requested via Slack, but could we add more context about what's changing in the types package? Minor version bumps typically indicate new functionality that's backwards compatible. What new types or features are we adding? |
||
| "description": "TypeScript type definitions for Roo Code.", | ||
| "publishConfig": { | ||
| "access": "public", | ||
|
|
||
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.
Is this version bump intentional without a changeset file? This project uses changesets for version management (as configured in ), so typically version bumps should be accompanied by a changeset file that documents what changed.
If this is a manual version bump for a specific reason, could you clarify why we're bypassing the changeset workflow?