v1.6.0

[BakerNet]

Related PR(s)

Related Issue(s)

Summary / Background

[pooyaw]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[gemini-code-assist]

Summary of Changes

Hello @BakerNet, 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 primarily focuses on updating version numbers across the project. It updates the reference to the codeowners-plus GitHub Action in the README.md and increments the internal version string of the codeowners-cli tool. These changes are preparatory steps for an upcoming release, likely version 1.6.0, ensuring that documentation and internal tooling reflect the latest versioning.

Highlights

• GitHub Action Version Update: The README.md file has been updated to reference the codeowners-plus GitHub Action at version v1.6.0, upgrading from v1.5.0.
• CLI Tool Version Bump: The internal version string for the codeowners-cli tool in tools/cli/main.go has been incremented from v1.5.1.dev to v1.6.1.dev.

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

[github-actions]

Codeowners approval required for this PR:

• @zbedforrest

[gemini-code-assist]

Code Review

This pull request appears to be a post-release version bump for v1.6.0. The changes update the version in the README.md to point to the new v1.6.0 release and update the CLI tool's version for the next development cycle. I've identified a minor issue with the format of the new development version string. For better clarity in the future, consider making the PR title and description more descriptive, for example, 'Post-release: Bump version to v1.6.1.dev'.

[gemini-code-assist]

The new development version string v1.6.1.dev appears to be malformed. It should likely be v1.6.1.dev. This seems to be caused by a bug in the post-release.sh script, which incorrectly parses the version tag by including the 'v' prefix as part of the major version number. While fixing the script is outside the scope of this PR's changes, correcting the version string here is recommended. You should also consider fixing the script to prevent this from happening in future releases.

Suggested change

	Version: "v1.6.1.dev",
	Version: "v1.6.1.dev",