bump v1.0.1

[garrett4wade]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello, 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 the project's internal version number and all external references to its associated Docker image to v1.0.1. This ensures that documentation, build configurations, and example deployments consistently point to the latest release of the AReaL runtime.

Highlights

• Version Bump: The project version has been updated from 1.0.0 to 1.0.1 in pyproject.toml and uv.lock.
• Docker Image Update: References to the areal-runtime Docker image have been updated from v1.0.0 to v1.0.1 across documentation and Skypilot example configurations.

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

Changelog

• docs/en/tutorial/installation.md
  • Updated the AReaL Image version in the installation table.
  • Updated the docker pull and docker run commands to use the new image version.
• examples/skypilot/README.md
  • Updated the image_id for the AReaL runtime in the Skypilot resource definitions.
• examples/skypilot/ray_cluster.sky.yaml
  • Updated the image_id for the AReaL runtime.
• examples/skypilot/single_node.sky.yaml
  • Updated the image_id for the AReaL runtime.
• pyproject.toml
  • Updated the version field to 1.0.1.
• uv.lock
  • Updated the areal package version to 1.0.1.

Ignored Files

• Ignored by pattern: .github/workflows/** (2)
  • .github/workflows/install-test.yml
  • .github/workflows/tag-release-image.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 project version from 1.0.0 to 1.0.1. The version number has been updated in the project's pyproject.toml, uv.lock, and various documentation and example files. The changes are consistent and correct for a version bump. However, I've noticed that the version number is hardcoded in multiple documentation and example files. To improve maintainability and reduce the risk of inconsistencies in future releases, I've suggested centralizing the version number, for instance by using placeholders and a substitution mechanism as part of your release process. This would make version bumps easier and less error-prone.

[gemini-code-assist]

To improve maintainability and reduce the chance of errors in future version bumps, consider using a variable for the version number. Since you are using Jupyter Book (as indicated by your project dependencies), you can define a substitution in your _config.yml file. For example:

myst_substitutions:
  areal_version: 1.0.1

Then, you can use {{ areal_version }} in your Markdown files. This would centralize the version number and ensure consistency across all documentation. For example, this line would become:
| AReaL Image | ghcr.io/inclusionai/areal-runtime:v{{ areal_version }} (includes runtime dependencies and Ray components) |
This change should be applied to all hardcoded versions in this file.

[gemini-code-assist]

Having the version number hardcoded in multiple example files makes version bumps tedious and error-prone. Consider using a placeholder for the version (e.g., AREAL_VERSION) and using a script to substitute it with the correct version from pyproject.toml as part of your release process. This would ensure all examples are always up-to-date with the release and simplifies future version bumps.

[gemini-code-assist]

Hardcoding the version number in example YAML files like this one and single_node.sky.yaml can lead to maintenance issues. To avoid manual updates and potential inconsistencies, consider using a templating approach for these configuration files. A script could replace a version placeholder (e.g., {{ areal_version }}) with the actual version from pyproject.toml during your release process.