Upgrade github.com/google/ko to v0.18.1

[ChrisGe4]

Description

Upgrade github.com/google/ko to v0.18.1 to update the indirect dependency github.com/sigstore/timestamp-authority to v2.0.3 and address CVE-2025-66564.

[gemini-code-assist]

Summary of Changes

Hello @ChrisGe4, 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 enhancing security and maintaining up-to-date dependencies. It includes a critical upgrade of the github.com/google/ko module to mitigate a known CVE, alongside a general update of the Go language version and various other direct and indirect Go modules. A significant structural change involves the removal of previously vendored cloud.google.com/go/spanner related files, streamlining the project's dependency footprint.

Highlights

• Dependency Upgrade: Upgraded the github.com/google/ko module to v0.18.1.
• Security Fix: The github.com/google/ko upgrade addresses CVE-2025-66564 by updating the indirect dependency github.com/sigstore/timestamp-authority to v2.0.3.
• Go Version Update: The Go language version used in the project and its examples has been updated from 1.19 to 1.23.0.
• Dependency Cleanup: Removed a substantial amount of vendored code related to cloud.google.com/go/spanner and its sub-modules, indicating a shift in dependency management strategy or a major refactoring.
• Other Dependency Updates: Numerous other direct and indirect Go dependencies have been updated to their latest versions, including github.com/docker/cli, github.com/google/go-containerregistry, go.opentelemetry.io/otel components, golang.org/x libraries, google.golang.org/grpc, and google.golang.org/protobuf.

🧠 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 upgrades github.com/google/ko to v0.18.1 and numerous other dependencies, which is crucial for addressing CVE-2025-66564 and maintaining the project's security and health. The update of Go versions in example modules is also a good step.

A significant change in this PR is the removal of a large number of vendored files, which suggests a move away from vendoring dependencies. This is a positive change for modernizing dependency management. However, this major change is not mentioned in the pull request description. For better maintainability and easier reviews in the future, I recommend providing a more comprehensive description that outlines all major changes, including dependency management strategy shifts and the full scope of dependency upgrades.

[gemini-code-assist]

Upgrading the Go version from 1.19 to 1.23.0 is a significant jump. This could introduce breaking changes, for instance, the change in for loop variable semantics in Go 1.22. Please ensure that the example code is compatible with Go 1.23 and that all related tests are passing.

[gemini-code-assist]

Similar to the other example module, upgrading the Go version from 1.19 to 1.23.0 is a significant jump. This could introduce breaking changes, for instance, the change in for loop variable semantics in Go 1.22. Please ensure that the example code is compatible with Go 1.23 and that all related tests are passing.