LCORE-544: Bump-up to version 0.2.0 #435
Conversation
WalkthroughProject version references updated from 0.1.3 to 0.2.0 across README, docs, OpenAPI metadata, and the Python version constant. Docs also refresh example outputs, including an expanded dependency list in getting_started.md. No functional code or API changes. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested reviewers
Poem
Tip 🔌 Remote MCP (Model Context Protocol) integration is now available!Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats. ✨ Finishing Touches
🧪 Generate unit tests
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. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
tisnik
force-pushed
the
bump-up-to-version-0.2.0
branch
from
e747945 to
19da578
Compare
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
docs/deployment_guide.md (2)
403-404: Fix stray backtick in cp command.The trailing backtick breaks copy/paste.
-cp examples/lightspeed-stack-lls-external.yaml lightspeed-stack.yaml` +cp examples/lightspeed-stack-lls-external.yaml lightspeed-stack.yaml
617-632: docs/deployment_guide.md: Stable image tag 0.2.0 not found on Quay — action required
The manifest check for quay.io/lightspeed-core/lightspeed-stack:0.2.0 returned HTTP 404, indicating the tag does not exist. Update the docs or the registry so that users can pull the referenced image.• File docs/deployment_guide.md, lines 617–632: the example
podman pull …:0.2.0should point to an existing tag or you must push the 0.2.0 image to quay.io.
• After fixing, re-run the manifest check or manually verify thatcurl -I https://quay.io/v2/lightspeed-core/lightspeed-stack/manifests/0.2.0returns HTTP 200.
🧹 Nitpick comments (4)
docs/openapi.json (1)
1-2239: Consider defining securitySchemes and operation/global security to satisfy CKV_OPENAPI_4/5.Static analysis flags the spec for lacking security definitions. If applicable to 0.2.0, add a bearer auth scheme and wire it to the endpoints that require auth (e.g., /v1/query, /v1/feedback, conversations). Keep “noop” deployments in mind—attach security at operation-level instead of globally if some endpoints must remain open.
Example snippet to incorporate (adapt as needed):
{ "components": { "securitySchemes": { "BearerAuth": { "type": "http", "scheme": "bearer", "bearerFormat": "JWT" } } }, "paths": { "/v1/query": { "post": { "security": [ { "BearerAuth": [] } ] } } } // Optionally, a top-level "security": [ { "BearerAuth": [] } ] if all endpoints require auth }docs/deployment_guide.md (1)
672-701: Unify Llama Stack version across docs (0.2.14 here vs 0.2.17 elsewhere).This guide pins llama-stack==0.2.14, while docs/getting_started.md uses 0.2.17. Please align to a single recommended version or a supported range that matches MINIMAL/MAXIMAL_SUPPORTED_LLAMA_STACK_VERSION in src/constants.py for 0.2.0.
Options:
- Pick one version (e.g., 0.2.17) everywhere and validate it’s within the supported range.
- Or document a range (e.g., >=A, <B) consistent with the service’s compatibility gates.
Also applies to: 148-201
docs/getting_started.md (2)
64-64: Dependency snapshot reflects lightspeed-stack 0.2.0 — OK.If you want to reduce doc churn on every bump, consider templating the version (e.g., ${LS_STACK_VERSION}) or annotating that exact versions in the sample output may differ.
27-45: Llama Stack pinned to 0.2.17 — ensure consistency with other docs.README.md and deployment_guide pin 0.2.14, while this page uses 0.2.17. Please pick one recommended version (or a supported range) across the docs and confirm it’s within the service’s supported bounds.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (5)
README.md(1 hunks)docs/deployment_guide.md(2 hunks)docs/getting_started.md(1 hunks)docs/openapi.json(2 hunks)src/version.py(1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2025-08-18T10:56:55.349Z
Learnt from: matysek
PR: lightspeed-core/lightspeed-stack#292
File: pyproject.toml:0-0
Timestamp: 2025-08-18T10:56:55.349Z
Learning: The lightspeed-stack project intentionally uses a "generic image" approach, bundling many dependencies directly in the base runtime image to work for everyone, rather than using lean base images with optional dependency groups.
Applied to files:
docs/deployment_guide.md
🪛 Checkov (3.2.334)
docs/openapi.json
[HIGH] 1-2240: Ensure that the global security field has rules defined
(CKV_OPENAPI_4)
[HIGH] 1-2240: Ensure that security operations is not empty.
(CKV_OPENAPI_5)
⏰ 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: build-pr
- GitHub Check: e2e_tests
🔇 Additional comments (4)
docs/openapi.json (2)
16-16: OpenAPI info.version bumped to 0.2.0 — aligned with the project version.Matches src/version.py and the docs. LGTM.
2240-2240: Trailing newline/EOF formatting fix acknowledged.No concerns.
src/version.py (2)
12-12: Single source of truth set to 0.2.0 — good.This aligns with the declared release version.
1-12: No outdated version references found; 0.2.0 is consistently used throughout the repo.All checks passed—there are no occurrences of “0.1.3,” and every reference to version “0.2.0” appears as expected in docs, tests, source files, and lockfiles. Feel free to resolve this comment.
| [](https://www.python.org/) | ||
| [](https://www.python.org/) | ||
| [](https://github.com/lightspeed-core/lightspeed-stack/releases/tag/0.1.3) | ||
| [](https://github.com/lightspeed-core/lightspeed-stack/releases/tag/0.2.0) |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Pin to 0.2.0 is fine; consider linking the badge to “latest” to avoid future drift, and verify the 0.2.0 tag exists.
Keeping the badge image as “latest tag” while the link points to a fixed tag means every release requires touching this line. Linking to “releases/latest” avoids that churn. Also, please ensure the 0.2.0 release/tag is already published before merging.
Apply if you prefer a stable link to the latest release page:
-[](https://github.com/lightspeed-core/lightspeed-stack/releases/tag/0.2.0)
+[](https://github.com/lightspeed-core/lightspeed-stack/releases/latest)Run to verify the tag exists:
🏁 Script executed:
#!/bin/bash
set -euo pipefail
TAG="0.2.0"
OWNER_REPO="lightspeed-core/lightspeed-stack"
resp=$(curl -sSf "https://api.github.com/repos/${OWNER_REPO}/releases/tags/${TAG}" || true)
if jq -e '.tag_name=="'"${TAG}"'"' >/dev/null <<<"$resp"; then
echo "OK: release ${TAG} exists: $(jq -r .html_url <<<"$resp")"
else
echo "ERROR: release ${TAG} not found" >&2
exit 1
fiLength of output: 348
Release tag “0.2.0” not found – please publish before merging
Our verification against the GitHub Releases API returned a 404 for tag 0.2.0, which means the badge link will be broken until the tag is actually created. Please ensure the 0.2.0 release (and corresponding tag) is published before merging this change.
• Location: README.md, line 9
• Current badge/link:
[](https://github.com/lightspeed-core/lightspeed-stack/releases/tag/0.2.0)Optional: to avoid manual updates on future releases, you can point the link at the “latest” endpoint instead:
-[](https://github.com/lightspeed-core/lightspeed-stack/releases/tag/0.2.0)
+[](https://github.com/lightspeed-core/lightspeed-stack/releases/latest)This ensures the badge always links to the newest release, preventing future churn.
🤖 Prompt for AI Agents
In README.md around line 9, the release tag referenced (0.2.0) does not exist so
the badge link will 404; either create and publish a GitHub release that creates
tag v0.2.0 (or 0.2.0 depending on your tag naming) before merging, or update the
badge link to use the releases/latest URL so it always points to the newest
release; ensure the link and badge remain consistent (if you publish 0.2.0, keep
the current link, otherwise change the link target to /releases/latest and keep
the badge URL as-is).
1 participant
Description
Bump-up to version 0.2.0
Type of change
Related Tickets & Documents
Summary by CodeRabbit
Documentation
Chores