chore: bump version to 0.5.9

[DylanSoftware]

Summary

• Bumps __version__ from 0.5.8 to 0.5.9 to trigger the publish GitHub Action on merge.

Test plan

• Verify the publish workflow triggers on merge to main

[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 performs a routine version update, incrementing the project's __version__ to 0.5.9. The primary purpose of this change is to activate the automated publishing workflow via GitHub Actions, ensuring that the latest development state is properly released.

Highlights

• Version Bump: Updated the project's internal version from 0.5.8 to 0.5.9.
• Automated Release Trigger: This version increment is specifically intended to trigger the configured GitHub Action for publishing the package upon merging.

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

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.

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 updates the package version to 0.5.9. The change itself is straightforward. I have added a comment suggesting the automation of the versioning process to enhance maintainability and reduce the likelihood of manual errors in future releases.

[gemini-code-assist]

Manually bumping the version in this file is a process prone to human error and can be automated. For a more robust release workflow, I recommend adopting a tool like semantic-release. It can automatically determine the next version from your commit messages, generate a changelog, and handle the package publishing. This would eliminate the need for manual version bump pull requests.