-
Notifications
You must be signed in to change notification settings - Fork 107
build: bump go version to 1.23.12 #1128
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @ellemouton, 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!
I've updated the project's Go version from 1.23.9
to 1.23.12
across the entire codebase. This change affects various build configurations, including Dockerfiles for different environments (production, development, builder, tools) and the Makefile
, as well as the go.mod
files for the main project and its internal modules. The primary goal is to ensure the project leverages the latest stable Go release, benefiting from recent performance improvements, bug fixes, and security enhancements.
Highlights
- Docker Build Environment Update: The Go version used for building and running the application within Docker containers has been updated from
1.23.9-alpine3.20
to1.23.12-alpine3.22
in both the mainDockerfile
anddev.Dockerfile
. - Makefile Go Version Alignment: The
Makefile
now references Go version1.23.12
for consistency across the project's build processes and GitHub Actions. - Go Module Version Updates: All
go.mod
files across the main project and its sub-modules (autopilotserverrpc
,litrpc
,perms
) have been updated to declare Go version1.23.12
as the minimum required version. - Builder and Tooling Dockerfile Updates: Specialized Dockerfiles for building (
make/builder.Dockerfile
) and tools (tools/Dockerfile
) have been updated to use thegolang:1.23.12-bookworm
base image.
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 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 or fill out our survey 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.
Footnotes
-
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. ↩
There was a problem hiding this 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 bumps the Go version from 1.23.9 to 1.23.12 across the project, including go.mod
files, Makefiles, and Dockerfiles. The changes are consistent, but I've identified a potential issue in the Dockerfiles where the Go builder image is updated to use Alpine 3.22, while the final runtime image remains on Alpine 3.20. This version mismatch could lead to runtime errors. My review includes suggestions to align the Alpine versions to ensure compatibility.
/gemini review |
There was a problem hiding this 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 correctly bumps the Go version to 1.23.12 across all relevant files, including the Makefile, various go.mod
files, and Dockerfiles. The corresponding base Docker images are also updated, which is good practice. The changes are consistent and look good. I've added one comment regarding a related check script that could be improved for future maintainability.
@@ -1,4 +1,4 @@ | |||
FROM golang:1.23.9-bookworm@sha256:26ca07ec0684ebe2154ad45a3a03710edb90b9cfc3769bead74ebcf6644dc759 | |||
FROM golang:1.23.12-bookworm@sha256:d22457a90736648a605cf54c33a7a310bb290e1ac78af2bcbc1d87821c52c4b7 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While this version update is correct, it's worth noting that this file is currently excluded from the Go version check in the scripts/check-go-version-dockerfile.sh
script. Since this file is clearly intended to be updated with the project's Go version, this exclusion appears to be outdated. To improve future maintainability and ensure this file is correctly validated in subsequent version bumps, consider removing ./tools/Dockerfile
from the exception_list
in scripts/check-go-version-dockerfile.sh
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🎉
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🎉!
Nit:
I'd suggest also updating the go version in the /tools/go.mod
file.
No description provided.