Merge V1.76.0 into Develop

[aslam-quad]

Merge V1.76.0 into Develop

[gemini-code-assist]

Summary of Changes

Hello @aslam-quad, 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 synchronizes the develop branch by merging in the V1.76.0 release. The primary change involves updating version identifiers across the codebase, specifically incrementing the application's reported version and updating the module_name metadata for all Terraform modules to reflect the new v1.76.0 tag.

Highlights

• Application Version Update: The main application version in cmd/root.go has been updated from v1.75.1 to v1.76.0.
• Terraform Module Version Bumps: All Terraform modules across both community/modules and modules directories have had their provider_meta module_name updated from v1.75.1 to v1.76.0.

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

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 version number from v1.75.1 to v1.76.0 across the codebase. The changes are consistent and look good.

However, I've added a couple of medium-severity comments regarding the manual process of updating these version strings. Having to manually update the version in dozens of files is error-prone and not very maintainable. I've suggested exploring automation for this process, such as using build flags for the Go binary and scripting for the Terraform module files. Adopting such automation would make the release process more robust and less tedious.