Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
[![License](https://img.shields.io/badge/license-Apache-blue)](https://github.com/lightspeed-core/lightspeed-stack/blob/main/LICENSE)
[![made-with-python](https://img.shields.io/badge/Made%20with-Python-1f425f.svg)](https://www.python.org/)
[![Required Python version](https://img.shields.io/python/required-version-toml?tomlFilePath=https%3A%2F%2Fraw.githubusercontent.com%2Flightspeed-core%2Flightspeed-stack%2Frefs%2Fheads%2Fmain%2Fpyproject.toml)](https://www.python.org/)
[![Tag](https://img.shields.io/github/v/tag/lightspeed-core/lightspeed-stack)](https://github.com/lightspeed-core/lightspeed-stack/releases/tag/0.1.3)
[![Tag](https://img.shields.io/github/v/tag/lightspeed-core/lightspeed-stack)](https://github.com/lightspeed-core/lightspeed-stack/releases/tag/0.2.0)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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:

-[![Tag](https://img.shields.io/github/v/tag/lightspeed-core/lightspeed-stack)](https://github.com/lightspeed-core/lightspeed-stack/releases/tag/0.2.0)
+[![Tag](https://img.shields.io/github/v/tag/lightspeed-core/lightspeed-stack)](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
fi

Length 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:

[![Tag](https://img.shields.io/github/v/tag/lightspeed-core/lightspeed-stack)](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:

-[![Tag](https://img.shields.io/github/v/tag/lightspeed-core/lightspeed-stack)](https://github.com/lightspeed-core/lightspeed-stack/releases/tag/0.2.0)
+[![Tag](https://img.shields.io/github/v/tag/lightspeed-core/lightspeed-stack)](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).


Lightspeed Core Stack (LCS) is an AI-powered assistant that provides answers to product questions using backend LLM services, agents, and RAG databases.

Expand Down
8 changes: 4 additions & 4 deletions docs/deployment_guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -614,14 +614,14 @@ Writing manifest to image destination
4468f475931a54ad1e5c26270ff4c3e55ec31444c1b0bf8fb77a576db7ab33f1
```

To retrieve stable version `0.1.3`, use the following command:
To retrieve stable version `0.2.0`, use the following command:

```bash
podman pull quay.io/lightspeed-core/lightspeed-stack:0.1.3
podman pull quay.io/lightspeed-core/lightspeed-stack:0.2.0
```

```text
Trying to pull quay.io/lightspeed-core/lightspeed-stack:0.1.3...
Trying to pull quay.io/lightspeed-core/lightspeed-stack:0.2.0...
Getting image source signatures
Copying blob 7c9e86f872c9 done |
Copying blob 455d71b0a12b skipped: already exists
Expand Down Expand Up @@ -1323,7 +1323,7 @@ The response should look like:
```json
{
"name": "Lightspeed Core Service (LCS)",
"version": "0.1.3"
"version": "0.2.0"
}
```

Expand Down
2 changes: 1 addition & 1 deletion docs/getting_started.md
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@ It is possible to run Lightspeed Core Stack service with Llama Stack "embedded"
+ greenlet==3.2.3
+ grpcio==1.74.0
+ httpx-sse==0.4.1
~ lightspeed-stack==0.1.3 (from file:///tmp/ramdisk/lightspeed-stack)
~ lightspeed-stack==0.2.0 (from file:///tmp/ramdisk/lightspeed-stack)
+ litellm==1.74.9.post1
+ lxml==6.0.0
+ mcp==1.12.2
Expand Down
4 changes: 2 additions & 2 deletions docs/openapi.json
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@
"name": "Apache 2.0",
"url": "https://www.apache.org/licenses/LICENSE-2.0.html"
},
"version": "0.1.3"
"version": "0.2.0"
},
"servers": [
{
Expand Down Expand Up @@ -2237,4 +2237,4 @@
}
}
}
}
}
2 changes: 1 addition & 1 deletion src/version.py
Original file line number Diff line number Diff line change
Expand Up @@ -9,4 +9,4 @@
# [tool.pdm.version]
# source = "file"
# path = "src/version.py"
__version__ = "0.1.3"
__version__ = "0.2.0"