Bump v0.5.2

[garrett4wade]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @garrett4wade, 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 systematically updates all version references across the AReaL project to v0.5.2. This includes the internal application version, the recommended Docker image in the installation guide, and the Docker image used within the SkyPilot examples. The primary goal is to ensure consistency and direct users to the latest runtime environment and documentation.

Highlights

• Version Bump: The core application version has been updated from 0.5.1 to 0.5.2 in areal/version.py.
• Documentation Update: The installation documentation (docs/tutorial/installation.md) has been updated to reference the new ghcr.io/inclusionai/areal-runtime:v0.5.2 Docker image for both table entries and command-line examples.
• SkyPilot Examples Update: All SkyPilot examples (examples/skypilot/README.md, examples/skypilot/ray_cluster.sky.yaml, examples/skypilot/single_node.sky.yaml) have been updated to use the new ghcr.io/inclusionai/areal-runtime:v0.5.2 Docker image.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Ignored Files

• Ignored by pattern: .github/workflows/** (2)
  • .github/workflows/tag-release-image.yml
  • .github/workflows/test-areal.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 correctly bumps the project version from v0.5.1 to v0.5.2 across the codebase, including the main version file, documentation, and example configurations. The changes are consistent and reflect the new version. However, I've noticed that the version string is hardcoded in multiple locations. This practice can make future version updates tedious and error-prone. To improve maintainability, I recommend exploring ways to centralize the version string. For instance, documentation could use placeholders (e.g., v{{ version }}) that are substituted during a build process, and configuration files could potentially use environment variables for the image tag. This would streamline future releases.

[gemini-code-assist]

While this update is correct, hardcoding the version string in multiple places across documentation and example files makes the project harder to maintain. Each version bump requires manually finding and replacing all occurrences, which is error-prone. As suggested in the general feedback, centralizing this version string would be a significant improvement for future releases.

[gemini-code-assist]

The version string is also hardcoded here. For YAML examples like this, consider using environment variables if the execution environment (like SkyPilot) supports it. This would allow setting the version in one place for all examples.