LCORE-803: Bump-up LCORE to 0.3.0

[tisnik]

Description

LCORE-803: Bump-up LCORE to 0.3.0

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

Related Tickets & Documents

• Related Issue #LCORE-803

Summary by CodeRabbit

• Chores
  • Bumped application and API version to 0.3.0.
• Documentation
  • Updated README badge to reflect version 0.3.0.
  • OpenAPI specification now reports version 0.3.0.
• Tests
  • Updated end-to-end tests to expect version 0.3.0.

No functional or behavioral changes; this release aligns versioning across the app, documentation, and tests.

[coderabbitai]

Walkthrough

Project version references updated from 0.2.0 to 0.3.0 across README, OpenAPI spec, source version constant, and an e2e test expectation. An EOF newline was added to docs/openapi.json. No logic or public API changes.

Changes

Cohort / File(s)	Summary
Version metadata bump README.md, src/version.py	Updated displayed/version constants from 0.2.0 to 0.3.0.
OpenAPI spec version update docs/openapi.json	Bumped info.version to 0.3.0; added trailing newline.
E2E test expectation tests/e2e/features/info.feature	Adjusted expected version from 0.2.0 to 0.3.0.

Sequence Diagram(s)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• LCORE-544: Bump-up to version 0.2.0 #435 — Prior version bump touching the same files (0.1.3→0.2.0).
• LCORE-448: Bump-up to version 0.1.2 #326 — Similar update of version strings in version.py, OpenAPI, and README.
• LCORE-459: Bump-up to version 0.1.3 #345 — Another coordinated version bump across version.py, OpenAPI info, and README.

Poem

A rabbit taps the version drum—0.3.0, hooray!
Tags hop forward, docs in line, neat as bales of hay.
Specs now squeak a fresher tune, tests nod “looks right to me.”
With paws of merge, I stamp and grin—
Release carrots for all to see! 🥕✨

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 succinctly identifies the Jira ticket and accurately describes the primary change, which is updating the LCORE service version to 0.3.0, making it clear to reviewers what the pull request accomplishes.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ 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: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 23948fd and e05c7d1.

📒 Files selected for processing (4)

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

🧰 Additional context used

📓 Path-based instructions (3)

src/**/*.py

📄 CodeRabbit inference engine (CLAUDE.md)

Use absolute imports for internal modules (e.g., from auth import get_auth_dependency)

Files:

• src/version.py

**/*.py

📄 CodeRabbit inference engine (CLAUDE.md)

**/*.py: All modules start with descriptive module-level docstrings explaining purpose
Use logger = logging.getLogger(name) for module logging after import logging
Define type aliases at module level for clarity
All functions require docstrings with brief descriptions
Provide complete type annotations for all function parameters and return types
Use typing_extensions.Self in model validators where appropriate
Use modern union syntax (str | int) and Optional[T] or T | None consistently
Function names use snake_case with descriptive, action-oriented prefixes (get_, validate_, check_)
Avoid in-place parameter modification; return new data structures instead of mutating arguments
Use appropriate logging levels: debug, info, warning, error with clear messages
All classes require descriptive docstrings explaining purpose
Class names use PascalCase with conventional suffixes (Configuration, Error/Exception, Resolver, Interface)
Abstract base classes should use abc.ABC and @AbstractMethod for interfaces
Provide complete type annotations for all class attributes
Follow Google Python docstring style for modules, classes, and functions, including Args, Returns, Raises, Attributes sections as needed

Files:

• src/version.py

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

📄 CodeRabbit inference engine (CLAUDE.md)

Write E2E tests as Gherkin feature files for behave

Files:

• tests/e2e/features/info.feature

🪛 Checkov (3.2.334)

docs/openapi.json

[high] 1-3810: Ensure that the global security field has rules defined

(CKV_OPENAPI_4)

---

[high] 1-3810: 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 (ci)

🔇 Additional comments (5)

README.md (1)

9-9: LGTM! Version reference updated consistently.

The badge link correctly references the new 0.3.0 release tag, aligning with the version updates in src/version.py, docs/openapi.json, and the E2E test expectations.

src/version.py (1)

12-12: LGTM! Canonical version updated.

The __version__ constant is correctly updated to "0.3.0". This serves as the single source of truth for the project version, as referenced by pyproject.toml and reflected in the OpenAPI spec and test expectations.

docs/openapi.json (2)

16-16: LGTM! OpenAPI spec version updated.

The API specification version is correctly updated to "0.3.0", maintaining consistency with the service version defined in src/version.py.

---

3810-3810: LGTM! EOF newline added.

Adding a trailing newline follows POSIX standards for text files and is a good practice.

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

20-20: LGTM! Test expectation updated.

The E2E test correctly expects version "0.3.0" in the info endpoint response, maintaining test coverage after the version bump.

---

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.}