LCORE-1652: Add release candidates versions

[tisnik]

Description

LCORE-1652: Add release candidates versions

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
• Benchmarks improvement

Tools used to create PR

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

Related Tickets & Documents

• Related Issue #LCORE-1652

Summary by CodeRabbit

• Documentation
  • Updated supported versions documentation to include two prerelease versions (0.6.0rc1 and 0.6.0rc2), displaying their respective support statuses and planned lifecycle information. The versions table was also reformatted to improve readability and alignment.

[coderabbitai]

Warning

Rate limit exceeded

@tisnik has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 46 minutes and 50 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: c3218879-0f6c-4a0d-b1d4-c6dbe7cc2fe9

📥 Commits

Reviewing files that changed from the base of the PR and between 2021898 and 3406120.

📒 Files selected for processing (1)

• docs/versions_supported.md

Walkthrough

The supported versions documentation is updated to include two prerelease version entries: 0.6.0rc1 and 0.6.0rc2. Each entry includes status designations and placeholder values for lifecycle dates.

Changes

Supported Versions Documentation

Layer / File(s)	Summary
Supported versions table expansion docs/versions_supported.md	Prerelease version rows for 0.6.0rc1 and 0.6.0rc2 are added to the supported versions table with "Current" and "Future" status values and "to be decided" placeholders for release and end-of-life dates. Table formatting is also adjusted.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the main change: adding release candidate versions (0.6.0rc1 and 0.6.0rc2) to the supported versions documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

✨ Simplify code

• Create PR with simplified code

---

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

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/versions_supported.md`:
- Around line 8-10: The status values for the versions are inconsistent: update
the status column for the rows with identifiers "0.6.0", "0.6.0rc1", and
"0.6.0rc2" so they reflect a consistent lifecycle model (either mark the
released final "0.6.0" as "Current" and both "0.6.0rc1" and "0.6.0rc2" as
"Past/Archived"/"Deprecated", or if RCs are still active mark "0.6.0" as
"Future" and set the RC rows to "Current"/"Active"); change the status strings
in the table accordingly to match your chosen model.
- Around line 9-10: The release candidate dates are ordered incorrectly: ensure
that "0.6.0rc1" and "0.6.0rc2" are scheduled before the final "0.6.0" date by
updating their date values in the table (e.g., move 0.6.0rc1 to an earlier date
than the final, set 0.6.0rc2 between rc1 and the final release), so the sequence
is rc1 → rc2 → 0.6.0; update the date strings for the rows containing
"0.6.0rc1", "0.6.0rc2", and "0.6.0" accordingly.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 5643af63-cfb8-4a3f-b76d-a700a1ec8fb6

📥 Commits

Reviewing files that changed from the base of the PR and between 9b2e821 and 2021898.

📒 Files selected for processing (1)

• docs/versions_supported.md

📜 Review details

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

• GitHub Check: build-pr
• GitHub Check: unit_tests (3.12)
• GitHub Check: unit_tests (3.13)
• GitHub Check: pydocstyle
• GitHub Check: radon
• GitHub Check: list_outdated_dependencies
• GitHub Check: Pylinter
• GitHub Check: spectral
• GitHub Check: integration_tests (3.12)
• GitHub Check: E2E: server mode / ci / group 3
• GitHub Check: E2E: server mode / ci / group 1
• GitHub Check: E2E: server mode / ci / group 2
• GitHub Check: E2E: library mode / ci / group 3
• GitHub Check: E2E Tests for Lightspeed Evaluation job
• GitHub Check: E2E: library mode / ci / group 2
• GitHub Check: E2E: library mode / ci / group 1
• GitHub Check: Konflux kflux-prd-rh02 / lightspeed-stack-on-pull-request