Skip to content

Conversation

@tisnik
Copy link
Contributor

@tisnik tisnik commented Oct 1, 2025

Description

LCORE-650: Support Llama Stack version 0.2.21

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-650

Summary by CodeRabbit

  • Chores
    • Updated dependencies to llama-stack 0.2.21 and llama-stack-client 0.2.21.
    • Increased the maximal supported Llama Stack version to 0.2.21 to align with the latest stack.
    • Ensures compatibility with the latest Llama Stack release.
    • No functional behavior changes expected for end-users; only version and compatibility updates.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Oct 1, 2025

Walkthrough

Bumps llama-stack and llama-stack-client from 0.2.20 to 0.2.21 in pyproject.toml, updates MAXIMAL_SUPPORTED_LLAMA_STACK_VERSION in src/constants.py to "0.2.21", and updates the e2e test expectation for the info endpoint to reflect version 0.2.21. No other behavioral changes.

Changes

Cohort / File(s) Summary
Dependency bump
pyproject.toml
Update dependencies: llama-stack 0.2.20 → 0.2.21 and llama-stack-client 0.2.20 → 0.2.21.
Version constant
src/constants.py
Update MAXIMAL_SUPPORTED_LLAMA_STACK_VERSION: "0.2.20" → "0.2.21".
Tests
tests/e2e/features/info.feature
Update expected llama-stack version in the info endpoint test from 0.2.20 → 0.2.21.

Sequence Diagram(s)

(omitted — changes are version bumps and test expectation updates; control flow unchanged)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested reviewers

  • umago

Poem

A rabbit scurries, version in paw,
Nudge from .20 to .21 — hurrah! 🐇
Two stacks aligned, a test revised,
Constants ticked, the build apprised.
I wiggle my nose and hop away. ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed The title succinctly conveys the primary purpose of the PR, namely adding support for Llama Stack version 0.2.21, and includes the relevant issue key for traceability. It is concise, specific to the main change, and avoids extraneous details.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

📜 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 ca0a94d and 3c72b88.

📒 Files selected for processing (1)
  • tests/e2e/features/info.feature (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
tests/e2e/features/**/*.feature

📄 CodeRabbit inference engine (CLAUDE.md)

Write E2E tests as Gherkin feature files for behave

Files:

  • tests/e2e/features/info.feature
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: e2e_tests
  • GitHub Check: build-pr
🔇 Additional comments (1)
tests/e2e/features/info.feature (1)

21-21: LGTM! Test expectation correctly updated.

The version expectation has been properly updated to match the bumped llama-stack version 0.2.21.


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

Comment @coderabbitai help to get the list of available commands and usage tips.

@tisnik tisnik merged commit fd96246 into lightspeed-core:main Oct 1, 2025
18 of 19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant