LCORE-380: Lock Llama-stack to version 0.2.14

[tisnik]

Description

LCORE-380: Lock Llama-stack to version 0.2.14

Type of change

• Refactor
• New feature
• Bug fix
• CVE fix
• Optimization
• Documentation Update
• Configuration Update
• Bump-up service version
• Bump-up dependent library
• Bump-up library or tool used for development (does not change the final image)
• CI configuration change
• Konflux configuration change
• Unit tests improvement
• Integration tests improvement
• End to end tests improvement

Related Tickets & Documents

• Related Issue #LCORE-380

Summary by CodeRabbit

• Chores
  • Updated the version requirement for a core dependency to ensure compatibility and stability.

[coderabbitai]

Walkthrough

The dependency for "llama-stack" in the project's configuration file was updated from a minimum version requirement (>=0.2.13) to an exact version requirement (==0.2.14). No other dependencies or settings were altered.

Changes

File	Change Summary
pyproject.toml	Updated "llama-stack" dependency to "==0.2.14"

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• LCORE-379: fixed run.yaml to be compatible with Llama Stack 0.2.14 #265: Updates configuration to ensure compatibility with llama-stack version 0.2.14, directly related to the version change in this PR.

Poem

A hop, a skip, a version bump,
The stack now stands on firmer clump.
From "at least" to "just this one,"
The update’s small, the work is done.
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e534d93 and f6e8058.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• pyproject.toml (1 hunks)

🔇 Additional comments (1)

pyproject.toml (1)

13-13: Confirm availability of llama-stack==0.2.14 on PyPI before merging

The original jq check fails because of operator-precedence: it tries to call length on a boolean. Please replace it with:

#!/usr/bin/env bash
set -euo pipefail
url="https://pypi.org/pypi/llama-stack/json"

if ! curl -fsSL "$url" \
     | jq -e '.releases["0.2.14"] | length > 0' \
     > /dev/null; then
  echo "llama-stack 0.2.14 not found on PyPI!" >&2
  exit 1
fi

echo "llama-stack 0.2.14 is available."

Or verify manually via:

pip index versions llama-stack

and confirm that 0.2.14 appears in the list.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need 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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[manstis]

@TamiTakamiya @ldjebran FYI.

@tisnik Thanks for this.

lightspeed-providers will need the same.

https://github.com/lightspeed-core/lightspeed-providers/blob/main/pyproject.toml#L10

[manstis]

@tisnik FYI lightspeed-core/lightspeed-providers#19