-
Notifications
You must be signed in to change notification settings - Fork 3
chore: nightly SDK version bump #60
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
base: main
Are you sure you want to change the base?
Conversation
Mesa DescriptionThis PR updates Python Note Cursor Bugbot is generating a summary for commit 9a5dbfa. Configure here. Description generated by Mesa. Update settings |
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.
Performed full review of 7817ccc...d0f91a6
Analysis
-
Potential inconsistency in version constraint notation - most templates use
>=0.15.0but there's a possible discrepancy in the magnitude template where the summary indicates^0.15.0while the diff shows>=0.15.0. -
The PR appears to be implementing an automated version bump process, but may benefit from standardizing on a single versioning constraint strategy (
>=vs^) across all templates to prevent future inconsistencies.
Tip
⚡ Quick Actions
This review was generated by Mesa.
Actions:
Slash Commands:
/review- Request a full code review/review latest- Review only changes since the last review/describe- Generate PR description. This will update the PR body or issue comment depending on your configuration/help- Get help with Mesa commands and configuration options
11 files reviewed | 0 comments | Review on Mesa | Edit Reviewer Settings
a3785be to
4af289f
Compare
4af289f to
1212e88
Compare
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.
Performed full review of 2595fef...1212e88
Analysis
- Significant version jump from 0.14.2 to 0.17.0 may introduce breaking changes that could affect template functionality
- Inconsistent versioning strategies exist between templates (gemini-cua using caret versioning
^0.15.0while others use>=0.14.2) - The automated nature of the update suggests CI testing, but runtime compatibility verification may be needed
- All templates now use
>=constraints which could lead to unpredictable behavior if future SDK versions introduce compatibility issues
Tip
Help
Slash Commands:
/review- Request a full code review/review latest- Review only changes since the last review/describe- Generate PR description. This will update the PR body or issue comment depending on your configuration/help- Get help with Mesa commands and configuration options
12 files reviewed | 0 comments | Edit Agent Settings
e2353f6 to
c2da364
Compare
8cd3c2a to
d12984e
Compare
78cc82d to
9a5dbfa
Compare
9a5dbfa to
2500abc
Compare
2500abc to
c6e3b32
Compare
| requires-python = ">=3.11" | ||
| dependencies = [ | ||
| "kernel>=0.14.2", | ||
| "kernel>=0.24.0", |
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.
Bug: Lock files not updated after dependency version bump
The pyproject.toml files were updated to require kernel>=0.24.0, but the corresponding tracked uv.lock files still have old incompatible versions locked (0.5.0, 0.11.1, 0.1.0a15). When users run uv sync with these templates, it will fail because the locked versions don't satisfy the new constraint. The lock files in advanced-sample, browser-use, sample-app, and computer-use templates need to be regenerated.
This PR updates Python
kerneland TypeScript@onkernel/sdkversion constraints to the latest published releases.