Skip to content

chore(deps): update golang docker tag to v1.26#196

Open
renovate-bot wants to merge 1 commit intoGoogleCloudPlatform:mainfrom
renovate-bot:renovate/golang-1.x
Open

chore(deps): update golang docker tag to v1.26#196
renovate-bot wants to merge 1 commit intoGoogleCloudPlatform:mainfrom
renovate-bot:renovate/golang-1.x

Conversation

@renovate-bot
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
golang stage minor 1.251.26

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate-bot renovate-bot requested review from a team and janetkuo as code owners February 10, 2026 22:30
@gemini-code-assist
Copy link

Summary of Changes

Hello @renovate-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 golang Docker image version used in the pre-sync/oci-image-verification service. This ensures that the build environment for this component leverages the latest stable Go release, incorporating recent language features, performance improvements, and security patches.

Highlights

  • Dependency Update: Updated the golang Docker image tag from 1.25 to 1.26 in pre-sync/oci-image-verification/Dockerfile.
Changelog
  • pre-sync/oci-image-verification/Dockerfile
    • Updated the base golang image from version 1.25 to 1.26.
Activity
  • Pull request was automatically generated by Renovate bot to update a dependency.
  • Automerge is currently disabled, requiring manual merging.
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

@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 aims to update the Go version to 1.26 by changing the Docker base image. However, this change is incomplete. The go.mod file for this project contains go 1.25.0 and toolchain go1.25.7 directives, which pin the build to use Go toolchain version 1.25.7, regardless of the version present in the Docker image. For the update to be effective, the go.mod file must also be updated to reflect the new Go version.


# Build stage
FROM golang:1.25 as builder
FROM golang:1.26 as builder

Choose a reason for hiding this comment

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

high

While the base image is updated to golang:1.26, this change is not sufficient to update the Go version used for the build. The go.mod file in this directory specifies toolchain go1.25.7, which forces the Go toolchain to use that specific version, ignoring the one provided by the Docker image.

To complete the upgrade to Go 1.26, you must also update pre-sync/oci-image-verification/go.mod:

- go 1.25.0
- toolchain go1.25.7
+ go 1.26.0
+ toolchain go1.26.0

Without updating go.mod, this Dockerfile change has no effect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments