LCORE-459: Bump-up to version 0.1.3 #345
Conversation
WalkthroughThis change updates the version number from "0.1.2" to "0.1.3" across several files, including documentation, the OpenAPI specification, and the source code's version constant. No other content, functionality, or logic was altered. Changes
Sequence Diagram(s)No sequence diagram generated, as all changes are simple version string updates with no control flow modifications. Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Poem
Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. 📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (4)
✅ Files skipped from review due to trivial changes (2)
🚧 Files skipped from review as they are similar to previous changes (1)
🧰 Additional context used🪛 Checkov (3.2.334)docs/openapi.json[HIGH] 1-1795: Ensure that the global security field has rules defined (CKV_OPENAPI_4) [HIGH] 1-1795: 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). (1)
🔇 Additional comments (1)
✨ 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 comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![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
🔭 Outside diff range comments (1)
docs/openapi.json (1)
1-1795: Add global security definitions to OpenAPI spec
The spec currently defines 401/403 responses but no top-levelsecurityorsecuritySchemes, which breaks tooling and may be a compliance gap.
- docs/openapi.json: insert a top-level
securityarray immediately after the"info"block- docs/openapi.json: add a
securitySchemesobject under"components"@@ "info": { ... }, + "security": [ + { "bearerAuth": [] } + ], @@ "components": { + "securitySchemes": { + "bearerAuth": { + "type": "http", + "scheme": "bearer", + "bearerFormat": "JWT" + } + }, "schemas": { ...Please confirm with your security/API owners which auth scheme to use (e.g., API key vs. JWT) and update accordingly.
🧹 Nitpick comments (1)
docs/getting_started.md (1)
1746-1749: Manual version strings are error-prone – consider templatingHard-coding
0.1.3here means the file must be edited for every future patch. Long-term, inject the value during the docs build (e.g.,{{ __version__ }}via Jinja or mkdocs-macros).
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (4)
README.md(1 hunks)docs/getting_started.md(1 hunks)docs/openapi.json(2 hunks)src/version.py(1 hunks)
🧰 Additional context used
🪛 Checkov (3.2.334)
docs/openapi.json
[HIGH] 1-1795: Ensure that the global security field has rules defined
(CKV_OPENAPI_4)
[HIGH] 1-1795: Ensure that security operations is not empty.
(CKV_OPENAPI_5)
🔇 Additional comments (2)
src/version.py (1)
12-12: Version constant correctly bumped, but make sure packaging metadata is rebuiltThe change is spot-on. After merging, remember to re-generate distribution artifacts (e.g.,
make distribution-archives) so that PyPI/containers pick up0.1.3, and cut the corresponding Git tag/release.docs/openapi.json (1)
10-10: Version string bumped successfully
info.versionis updated to0.1.3, matching the declared PR intent.
| [](https://www.python.org/) | ||
| [](https://www.python.org/) | ||
| [](https://github.com/lightspeed-core/lightspeed-stack/releases/tag/0.1.2) | ||
| [](https://github.com/lightspeed-core/lightspeed-stack/releases/tag/0.1.3) |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Link now targets 0.1.3 — verify no other stale badges
The badge points to the new tag and looks fine. To be safe, scan the repo for any remaining 0.1.2 literals.
🏁 Script executed:
#!/bin/bash
# Find any forgotten hard-coded references to the old version.
rg -n '"?0\.1\.2"?' || trueLength of output: 1678
Replace leftover 0.1.2 references in docs/getting_started.md
Scan results uncovered hard-coded mentions of the old version in your getting-started guide. Please update these to 0.1.3:
- docs/getting_started.md: line 690
~ lightspeed-stack==0.1.2 - docs/getting_started.md: line 1025
To retrieve stable version0.1.2, use the following command: - docs/getting_started.md: line 1028
podman pull quay.io/lightspeed-core/lightspeed-stack:0.1.2 - docs/getting_started.md: line 1032
Trying to pull quay.io/lightspeed-core/lightspeed-stack:0.1.2...
The uv.lock entries pinning dependencies at “0.1.2” are autogenerated—no manual edits needed (you can regenerate the lock file if you want those updated).
🤖 Prompt for AI Agents
In docs/getting_started.md at lines 690, 1025, 1028, and 1032, update all
hard-coded references of version "0.1.2" to "0.1.3" to ensure the documentation
reflects the current stable version. No changes are needed for uv.lock as it is
autogenerated.
tisnik
force-pushed
the
lcore-459-bump-up-to-version-0.1.3
branch
from
c293dba to
362aee6
Compare
1 participant
Description
LCORE-459: Bump-up to version 0.1.3
Type of change
Related Tickets & Documents
Summary by CodeRabbit
Documentation
Chores