chore(release): bump version to 2.0.2

[Ahmath-Gadji]

Summary

• pyproject.toml + uv.lock: 2.0.1 -> 2.0.2
• compose: openrag and openrag-admin-ui pins -> v2.0.2
• chart: version 0.5.2 -> 0.5.3, appVersion -> 2.0.2
• chart values: ray, openrag, adminUi image tags -> v2.0.2

Test plan

• CI passes

Summary by CodeRabbit

• Release
  • Updated the application to version 2.0.2.
  • Updated container images across supported deployment options to version 2.0.2.
  • Updated deployment metadata to reflect the new release version.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: a320ab12-a82d-42e5-969b-176b38dbc922

📥 Commits

Reviewing files that changed from the base of the PR and between b2ab6b1 and 589d7bd.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (4)

• infra/charts/openrag-stack/Chart.yaml
• infra/charts/openrag-stack/values.yaml
• infra/compose/docker-compose.yaml
• pyproject.toml

---

📝 Walkthrough

Walkthrough

The release version is updated to 2.0.2 across project and Helm metadata, while Helm and Docker Compose image references move from v2.0.1 to v2.0.2.

Changes

Release alignment

Layer / File(s)	Summary
Release metadata pyproject.toml, infra/charts/openrag-stack/Chart.yaml	Project and Helm versions are updated for the 2.0.2 release.
Deployment image tags infra/charts/openrag-stack/values.yaml, infra/compose/docker-compose.yaml	Ray, OpenRAG, and Admin UI image references are updated from v2.0.1 to v2.0.2.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• linagora/openrag#765: Updates the same release metadata and image tag locations.
• linagora/openrag#637: Updates Helm chart release metadata.
• linagora/openrag#647: Updates the same Docker Compose image references.

Suggested labels: chore

Suggested reviewers: andyne13, enjoybacon7

🚥 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 clearly and concisely summarizes the main change: bumping the release version to 2.0.2.
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.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/bump-version-2.0.2

---

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

[hedhoud]

This branch is now 20 commits behind develop, so its successful checks do not validate the code that would actually ship. Please cut or refresh the 2.0.2 release from the current develop, rerun CI, and keep the image publication order consistent with the v2.0.1 release flow.

[hedhoud]

These image tags are not available yet. Because this PR targets develop, merging it will immediately publish chart 0.5.3-dev with defaults that cannot be pulled, leaving deployments in ImagePullBackOff. Please keep the release-only pins on the release branch until v2.0.2 is published, then back-merge them as we did for v2.0.1.

[Ahmath-Gadji]

Closing this in favor of doing the version bump as part of the actual release cut, not directly on develop.

Why:

• This PR targets develop and pins v2.0.2 image tags/versions that don't exist yet — the latest published tag is still v2.0.1. Merging now would leave develop (and the 0.5.3-dev chart it drives) referencing images that can't be pulled, per @hedhoud's review.
• The branch is also 20 commits behind develop at this point.
• Looking at how v2.0.1 actually shipped, the bump belongs on the release side of the flow, not the develop side:
  • release: v2.0.1 #763 (release/2.0.1 → main) did the version bump and merged into main, where the v2.0.1 tag was then cut — build.yml's verify-tag gate only publishes GA images for tags reachable from main.
  • chore: back-merge v2.0.1 into develop #765 (backmerge/v2.0.1-into-develop → develop) brought that same bump back into develop only afterward, once the images already existed.

Correct order for 2.0.2: cut a release/2.0.2 branch, do the version bump there, PR it into main, tag v2.0.2 on main so CI publishes real images, then sync main back into develop (backmerge PR) with that same bump — mirroring #763 → #765.

Will reopen following that flow once the 2.0.2 release is actually cut.