-
Notifications
You must be signed in to change notification settings - Fork 68
bump to 0.2.11 #274
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?
bump to 0.2.11 #274
Conversation
WalkthroughThe dependency versions for Changes
Possibly related PRs
Suggested reviewers
Poem
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Actionable comments posted: 0
🧹 Nitpick comments (1)
pyproject.toml (1)
9-15: Consider relaxed version specifiers to ease future bumpsHard-pinning to an exact patch version (
==0.2.11) forces a PR for every subsequent micro-release and can block security fixes until bumped.
Unless strict reproducibility is required, you could move to a compatible-release specifier (e.g.~=0.2.11or^0.2.11via Poetry) so patch updates are picked up automatically.-llama-stack-client==0.2.11 -llama-stack==0.2.11 +llama-stack-client~=0.2.11 +llama-stack~=0.2.11
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
uv.lockis excluded by!**/*.lock
📒 Files selected for processing (1)
pyproject.toml(1 hunks)
🔇 Additional comments (1)
pyproject.toml (1)
9-15: Confirm availability & compatibility of 0.2.11 before mergingBoth
llama-stack-clientandllama-stackhave been bumped in lock-step to0.2.11, which is good for avoiding version skew.
Please make sure:
0.2.11is published on PyPI (sometimes the tag precedes the upload).- No breaking API/ABI changes were introduced between
0.2.10and0.2.11that affect the demo code.You can verify quickly with the following script:
#!/bin/bash # Check if the new versions exist on PyPI and list release info for pkg in llama-stack-client llama-stack ; do echo "---- $pkg ----" curl -s "https://pypi.org/pypi/${pkg}/json" | jq -r '.releases["0.2.11"][0].upload_time_iso_8601' || \ echo "Version 0.2.11 not found on PyPI!" done
|
@anyuzoey I'll probably hold this for a few days. I was using the issue to test the github MCP server |
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.
@anyuzoey did we confirm if the new version works for all level 0-6 notebooks?
|
It works last week. |
address #272
Summary by CodeRabbit