Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bump go to 1.23.7 #5105

Merged
merged 1 commit into from
Mar 26, 2025
Merged

Conversation

zhangzujian
Copy link
Member

Pull Request

What type of this PR

Examples of user facing changes:

  • Features
  • Bug fixes
  • Docs
  • Tests

Which issue(s) this PR fixes

Fixes #(issue-number)

Signed-off-by: zhangzujian <zhangzujian.7@gmail.com>
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.

Hello @zhangzujian, 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!

Summary of Changes

This pull request updates the Go version to 1.23.7 and related dependencies. The changes include modifications to the Dockerfile.base, download-go-deps.sh, go.mod, and go.sum files to reflect the new Go version and corresponding dependency updates. The primary goal is to upgrade the Go runtime and its associated libraries to the latest stable releases.

Highlights

  • Go Version Upgrade: The Go version has been bumped from 1.22.12 to 1.23.7 in Dockerfile.base and go.mod.
  • Kubectl Version Update: The Kubectl version has been updated from v1.30.10 to v1.30.11 in Dockerfile.base and download-go-deps.sh.
  • Dependency Updates: The go.mod and go.sum files have been updated to reflect the new Go version and its dependencies, including golang.org/x/* libraries and k8s.io/* libraries.

Changelog

Click here to see the changelog
  • dist/images/Dockerfile.base
    • Updated GO_VERSION from 1.22.12 to 1.23.7.
    • Updated KUBECTL_VERSION from v1.30.10 to v1.30.11.
  • dist/images/go-deps/download-go-deps.sh
    • Updated KUBECTL_VERSION from v1.30.10 to v1.30.11.
  • go.mod
    • Updated go version from 1.22.12 to 1.23.7.
    • Updated golang.org/x/exp from v0.0.0-20250128182459-e0ece0dbea4c to v0.0.0-20250305212735-054e65f0b394.
    • Updated golang.org/x/mod from v0.23.0 to v0.24.0.
    • Updated golang.org/x/sys from v0.30.0 to v0.31.0.
    • Updated golang.org/x/time from v0.10.0 to v0.11.0.
    • Updated k8s.io/api from v0.30.10 to v0.30.11.
    • Updated k8s.io/apimachinery from v0.30.10 to v0.30.11.
    • Updated k8s.io/kubernetes from v1.30.10 to v1.30.11.
    • Updated golang.org/x/net from v0.35.0 to v0.37.0
    • Updated golang.org/x/oauth2 from v0.26.0 to v0.28.0
    • Updated golang.org/x/sync from v0.11.0 to v0.12.0
    • Updated golang.org/x/term from v0.29.0 to v0.30.0
    • Updated golang.org/x/text from v0.22.0 to v0.23.0
    • Updated golang.org/x/tools from v0.30.0 to v0.31.0
    • Updated k8s.io/apiextensions-apiserver from v0.30.10 to v0.30.11
    • Updated k8s.io/apiserver from v0.30.10 to v0.30.11
    • Updated k8s.io/component-base from v0.30.10 to v0.30.11
    • Updated k8s.io/kube-proxy from v0.30.10 to v0.30.11
    • Updated k8s.io/kube-scheduler from v0.30.10 to v0.30.11
    • Updated k8s.io/kubectl from v0.30.10 to v0.30.11
    • Updated k8s.io/kubelet from v0.30.10 to v0.30.11
    • Updated k8s.io/legacy-cloud-providers from v0.30.10 to v0.30.11
    • Updated k8s.io/metrics from v0.30.10 to v0.30.11
    • Updated k8s.io/mount-utils from v0.30.10 to v0.30.11
    • Updated k8s.io/pod-security-admission from v0.30.10 to v0.30.11
    • Updated k8s.io/sample-apiserver from v0.30.10 to v0.30.11
  • go.sum
    • Updated checksums for golang.org/x/exp, golang.org/x/mod, golang.org/x/net, golang.org/x/oauth2, golang.org/x/sync, golang.org/x/sys, golang.org/x/term, golang.org/x/text, golang.org/x/tools, k8s.io/api, k8s.io/apiextensions-apiserver, k8s.io/apimachinery, k8s.io/apiserver, k8s.io/client-go, k8s.io/component-base, and k8s.io/kubernetes.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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.


Trivia time!

What is the official mascot of the Go programming language?

Click here for the answer
The official mascot of the Go programming language is a gopher.

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

The pull request updates the Go version and related dependencies. The changes seem straightforward and necessary for keeping the project up-to-date. However, I have a few observations regarding the Kubernetes dependencies and the trivy version.

Summary of Findings

  • Kubernetes dependency updates: The pull request updates Kubernetes dependencies. It's important to ensure that these updates are compatible with the project's codebase and that any necessary code changes are made to accommodate the new versions.
  • Trivy version update: The pull request updates the Trivy version. It's important to verify that the new Trivy version doesn't introduce any breaking changes or require any updates to the project's security scanning process.

Merge Readiness

The pull request appears to be a routine update of dependencies. However, due to the potential impact of Kubernetes and Trivy version updates, I recommend careful testing and verification before merging. I am unable to directly approve this pull request, and other reviewers should verify and approve this code before merging.

Comment on lines +48 to 50
k8s.io/api v0.30.11
k8s.io/apimachinery v0.30.11
k8s.io/client-go v1.5.2

Choose a reason for hiding this comment

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

high

It's good to see the Kubernetes dependencies being updated. However, it's crucial to ensure that the project's code is compatible with these new versions. Were any code changes required to accommodate these updates?

Comment on lines +190 to +192
k8s.io/api => k8s.io/api v0.30.11
k8s.io/apiextensions-apiserver => k8s.io/apiextensions-apiserver v0.30.11
k8s.io/apimachinery => k8s.io/apimachinery v0.30.11

Choose a reason for hiding this comment

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

high

It's good to see the Kubernetes dependencies being updated. However, it's crucial to ensure that the project's code is compatible with these new versions. Were any code changes required to accommodate these updates?

@@ -88,7 +88,7 @@ FROM ghcr.io/aquasecurity/trivy:latest AS trivy

ARG ARCH
ENV CNI_PLUGINS_VERSION="v1.5.1"
ENV KUBECTL_VERSION="v1.30.10"
ENV KUBECTL_VERSION="v1.30.11"

Choose a reason for hiding this comment

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

medium

Consider adding a comment explaining why this specific kubectl version is being used. This can help with future maintenance and understanding the reasoning behind the choice.

@@ -4,7 +4,7 @@ set -e

ARCH=${ARCH:-amd64}
CNI_PLUGINS_VERSION=${CNI_PLUGINS_VERSION:-v1.5.1}
KUBECTL_VERSION=${KUBECTL_VERSION:-v1.30.10}
KUBECTL_VERSION=${KUBECTL_VERSION:-v1.30.11}

Choose a reason for hiding this comment

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

medium

Similar to the Dockerfile, adding a comment explaining the reasoning behind this kubectl version would be beneficial.

@zhangzujian zhangzujian marked this pull request as ready for review March 26, 2025 03:54
@dosubot dosubot bot added the size:M This PR changes 30-99 lines, ignoring generated files. label Mar 26, 2025
@zhangzujian zhangzujian merged commit fe45fa8 into kubeovn:release-1.12 Mar 26, 2025
54 checks passed
@dosubot dosubot bot added the go Pull requests that update Go code label Mar 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
go Pull requests that update Go code security size:M This PR changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant