Skip to content

Conversation

@cloud-java-bot
Copy link
Collaborator

To be merged after the release is complete.

@cloud-java-bot cloud-java-bot added the PR: Merge After Release This PR should only be merged after the release stated in description. label Nov 18, 2025
@github-actions github-actions bot mentioned this pull request Nov 18, 2025
5 tasks
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @cloud-java-bot, I'm Gemini Code Assist1! 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-core project. Following the v0.28.1 release, the snapshot version has been advanced to 0.28.2-SNAPSHOT to prepare for subsequent development cycles.

Highlights

  • Version Update: The project version in jib-core/gradle.properties has been incremented from 0.28.1-SNAPSHOT to 0.28.2-SNAPSHOT.
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.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request performs a post-release version bump for the jib-core module from 0.28.1-SNAPSHOT to 0.28.2-SNAPSHOT, following the v0.28.1 release. While the version change is appropriate for the next development cycle, the manual process could be improved. I have provided a suggestion to automate this step using the existing Gradle release plugin, which would enhance the robustness and consistency of the release workflow.

@@ -1 +1 @@
version = 0.28.1-SNAPSHOT
version = 0.28.2-SNAPSHOT
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This manual version bump appears to be a post-release task. The net.researchgate.release plugin, which is already configured in jib-core/build.gradle, can automate this process. Relying on manual version updates is error-prone. I recommend leveraging the release plugin to handle versioning automatically. This would typically involve a command like gradle release which would create a release commit/tag and a subsequent commit for the next development version, leading to a more robust and consistent release process.

@diegomarquezp diegomarquezp enabled auto-merge (squash) November 18, 2025 21:24
@diegomarquezp diegomarquezp merged commit 1cd849a into master Nov 19, 2025
8 of 10 checks passed
@diegomarquezp diegomarquezp deleted the core-release-v0.28.1 branch November 19, 2025 01:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

PR: Merge After Release This PR should only be merged after the release stated in description.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants