gradle release v3.5.0

[cloud-java-bot]

To be merged after the release is complete.

[gemini-code-assist]

Summary of Changes

Hello @cloud-java-bot, 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 updates the development version of the jib-gradle-plugin in its gradle.properties file. This is a standard procedure to prepare the codebase for ongoing development and future releases, setting the stage for work towards the next version after the v3.5.0 release.

Highlights

• Version Update: The jib-gradle-plugin's gradle.properties file has been updated to increment the version from "3.4.6-SNAPSHOT" to "3.5.1-SNAPSHOT". This change likely prepares the project for the next development cycle following the v3.5.0 release.

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 updates the version of the jib-gradle-plugin from 3.4.6-SNAPSHOT to 3.5.1-SNAPSHOT. While the PR title indicates a v3.5.0 release, the version change seems to skip the actual release version in the project's history. I have added a comment to the affected file to highlight this potential process issue. Additionally, for a new release, it is expected that the CHANGELOG.md is updated to document the changes, which is missing in this pull request.

[gemini-code-assist]

The PR title suggests a release of v3.5.0, but the version is being bumped directly from 3.4.6-SNAPSHOT to 3.5.1-SNAPSHOT. This approach skips the 3.5.0 version in the commit history, which can be confusing. A more standard release process would involve a commit with the version set to 3.5.0 for the release, followed by a separate commit to bump the version to 3.5.1-SNAPSHOT for future development. Could you please clarify if this direct jump is intentional?