LCORE-1064: updated version in sources

[tisnik]

Description

LCORE-1064: updated version in sources

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

Tools used to create PR

Identify any AI code assistants used in this PR (for transparency and review context)

• Assisted-by: N/A
• Generated by: N/A

Related Tickets & Documents

• Related Issue #LCORE-1064

Summary by CodeRabbit

• Chores
  • Version updated to 0.3.1

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Version bump from 0.3.0 to 0.3.1 across project files, including the version constant, OpenAPI specification, release badge, and corresponding end-to-end test expectations.

Changes

Cohort / File(s)	Summary
Version definition src/version.py	Updated __version__ constant from "0.3.0" to "0.3.1"
Documentation and specification docs/openapi.json, README.md	Updated OpenAPI spec version and README release badge link from 0.3.0 to 0.3.1; added final newline to README
End-to-end tests tests/e2e/features/info.feature	Updated info endpoint test assertions to expect version 0.3.1 for Lightspeed Core Service and llama-stack

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

This is a straightforward version bump with consistent, repetitive changes across multiple files. All modifications are simple string replacements with no logic changes or functional impact.

Possibly related PRs

• LCORE-803: Bump-up LCORE to 0.3.0 #653: Both PRs perform the same code-level change pattern—bumping the project/service version (updating src/version.py, docs/openapi.json, README badge, and corresponding test expectations).
• LCORE-459: Bump-up to version 0.1.3 #345: Both PRs bump the project version in src/version.py, updating the OpenAPI docs and README badges with related tests/docs.
• LCORE-491: E2E tests for Info, Models and Metrics endpoints #546: Both PRs modify the end-to-end info feature test expectations (tests/e2e/features/info.feature) for the service/info endpoint version response.

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 clearly summarizes the main change: a version bump from 0.3.0 to 0.3.1 across multiple source files (README.md, docs/openapi.json, src/version.py, and tests/e2e/features/info.feature).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

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

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 809a2df and cebf35c.

📒 Files selected for processing (4)

• README.md (2 hunks)
• docs/openapi.json (1 hunks)
• src/version.py (1 hunks)
• tests/e2e/features/info.feature (1 hunks)

🧰 Additional context used

📓 Path-based instructions (2)

tests/e2e/features/**/*.feature

📄 CodeRabbit inference engine (CLAUDE.md)

Use behave (BDD) framework with Gherkin feature files for end-to-end tests

Files:

• tests/e2e/features/info.feature

src/**/*.py

📄 CodeRabbit inference engine (CLAUDE.md)

src/**/*.py: Use absolute imports for internal modules in LCS project (e.g., from auth import get_auth_dependency)
All modules must start with descriptive docstrings explaining their purpose
Use logger = logging.getLogger(__name__) pattern for module logging
All functions must include complete type annotations for parameters and return types, using modern syntax (str | int) and Optional[Type] or Type | None
All functions must have docstrings with brief descriptions following Google Python docstring conventions
Function names must use snake_case with descriptive, action-oriented names (get_, validate_, check_)
Avoid in-place parameter modification anti-patterns; return new data structures instead of modifying input parameters
Use async def for I/O operations and external API calls
All classes must include descriptive docstrings explaining their purpose following Google Python docstring conventions
Class names must use PascalCase with descriptive names and standard suffixes: Configuration for config classes, Error/Exception for exceptions, Resolver for strategy patterns, Interface for abstract base classes
Abstract classes must use ABC with @abstractmethod decorators
Include complete type annotations for all class attributes in Python classes
Use import logging and module logger pattern with standard log levels: debug, info, warning, error

Files:

• src/version.py

🧠 Learnings (1)

📚 Learning: 2025-08-18T10:56:55.349Z

Learnt from: matysek
Repo: lightspeed-core/lightspeed-stack PR: 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:

• README.md

⏰ 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). (6)

• GitHub Check: build-pr
• GitHub Check: Konflux kflux-prd-rh02 / lightspeed-stack-on-pull-request
• GitHub Check: E2E: server mode / azure
• GitHub Check: E2E: library mode / ci
• GitHub Check: E2E: library mode / azure
• GitHub Check: E2E: server mode / ci

🔇 Additional comments (5)

docs/openapi.json (1)

16-16: Version bump is correct and scoped.

No schema deltas; just metadata. Verify repo-wide references (constants, tests, badges, charts) are aligned to 0.3.1. Optionally update example payloads that hardcode service_version (currently show 1.0.0) to avoid confusion in docs.

Check for stale 0.3.0 references and ensure all version declarations across the codebase are synchronized to 0.3.1.

src/version.py (1)

12-12: LGTM! Version bump applied correctly.

The version constant has been properly updated from 0.3.0 to 0.3.1, following semantic versioning for a patch release.

tests/e2e/features/info.feature (1)

18-19: LGTM! Test assertions updated correctly.

The version expectations in the e2e tests have been properly updated to 0.3.1 for both Lightspeed Core Service and llama-stack, maintaining consistency with the version bump.

README.md (2)

9-9: LGTM! Release badge updated correctly.

The GitHub release badge has been properly updated to reference version 0.3.1, ensuring the badge links to the correct release tag.

---

1026-1026: LGTM! Trailing newline added.

Adding a final newline at the end of the file follows text file best practices and improves POSIX compliance.

---

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

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