Fix docker tags

[nithishr]

• Tag images as latest only in the case of stable releases

[gemini-code-assist]

Summary of Changes

Hello @nithishr, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the project's release candidate version from "0.5.2rc4" to "0.5.2rc5" across key configuration files. This version increment is crucial for correctly managing Docker image tags, ensuring that only stable releases are designated with the "latest" tag, thereby preventing pre-release versions from being inadvertently promoted as the primary stable image.

Highlights

• Version Increment: The project version has been updated from "0.5.2rc4" to "0.5.2rc5" across multiple configuration files, including pyproject.toml, server.json, and uv.lock.
• Docker Tag Alignment: This version bump is a preparatory step to ensure that Docker images for release candidates are not mistakenly tagged as "latest", reserving the "latest" tag exclusively for stable releases.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/docker.yml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request bumps the version from 0.5.2rc4 to 0.5.2rc5 across pyproject.toml, server.json, and uv.lock. The changes are consistent and correctly prepare for a new release candidate. The changes appear to follow the documented release process, which is great for consistency. While the changes themselves are correct, the pull request title and description are slightly disconnected from the content, as they refer to Docker tagging logic which isn't part of this PR's changes. For better long-term maintainability and a clearer Git history, I'd suggest aligning the PR title more closely with the action taken (e.g., 'chore: Bump version to 0.5.2rc5'). Overall, the changes are correct and ready to be merged.