Bump version to 0.1.1

[tisnik]

Description

Bump version to 0.1.1

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

Summary by CodeRabbit

• Chores
  • Updated version number to 0.1.1 across documentation and application.
  • Refreshed badges and API documentation to reflect the new version.

[coderabbitai]

Walkthrough

The changes increment the project version from 0.1.0 to 0.1.1 across three files: the README badge, the OpenAPI documentation, and the version definition in the source code. No other logic, content, or API specifications were modified.

Changes

Cohort / File(s)	Change Summary
README Badge Update README.md	Updated the GitHub release badge link from version 0.1.0 to 0.1.1.
OpenAPI Version Bump docs/openapi.json	Changed the API version in the info section from "0.1.0" to "0.1.1".
Source Version Update src/version.py	Updated the __version__ variable from "0.1.0" to "0.1.1".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• LCORE-434: Added version tag #303: Both PRs involve changes to version badges in the README, making them related through documentation versioning.

Poem

A hop, a skip, a version jump—
From zero-one-oh to one-one’s thump!
The docs, the code, the badge agree,
All in sync, as they should be.
With every bump, we leap ahead—
A rabbit’s joy: “Release!” it said.
🐇✨

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

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

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

README.md (1)

385-386: Update Test PyPI link to new version
The link still references 0.1.0.

-* https://test.pypi.org/project/lightspeed-stack/0.1.0/
+* https://test.pypi.org/project/lightspeed-stack/0.1.1/

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 701183c and 2ad251c.

📒 Files selected for processing (3)

• README.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-1771: Ensure that the global security field has rules defined

(CKV_OPENAPI_4)

---

[HIGH] 1-1771: 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)

• GitHub Check: e2e_tests

🔇 Additional comments (3)

src/version.py (1)

12-12: Version bump looks correct and consistent
__version__ now reflects 0.1.1. No further action required.

README.md (1)

9-9: Badge URL correctly updated
The badge now points at the 0.1.1 tag.

docs/openapi.json (1)

10-10: API version string increment acknowledged
info.version updated to 0.1.1 – aligns with code & docs.