-
Notifications
You must be signed in to change notification settings - Fork 543
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
mimir-build-image: Upgrade Go version to 1.23.0-bookworm #9070
Conversation
Building new version of mimir-build-image. After image is built and pushed to Docker Hub, a new commit will automatically be added to this PR with new image version |
Not ready to merge yet: Awaiting image to be built and bot commit per instructions https://github.com/grafana/mimir/blob/main/docs/internal/how-to-update-the-build-image.md?plain=1 |
Not building new version of mimir-build-image. This PR modifies |
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.
I think you have to upgrade to the latest version of golangci-lint also. That's probably why the lint CI job failed.
Building new version of mimir-build-image. After image is built and pushed to Docker Hub, a new commit will automatically be added to this PR with new image version |
Not building new version of mimir-build-image. This PR modifies |
Thanks @aknuds1 😄 The remaining lint errors seem to be new/legitimate ones caught by the upgraded linter - i'll post another commit fixing these up tomorrow. |
e9ef469
to
cc76be0
Compare
Building new version of mimir-build-image. After image is built and pushed to Docker Hub, a new commit will automatically be added to this PR with new image version |
Building new version of mimir-build-image. After image is built and pushed to Docker Hub, a new commit will automatically be added to this PR with new image version |
Building new version of mimir-build-image. After image is built and pushed to Docker Hub, a new commit will automatically be added to this PR with new image version |
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.
Please see suggestions for cleanup.
Building new version of mimir-build-image. After image is built and pushed to Docker Hub, a new commit will automatically be added to this PR with new image version |
Co-authored-by: Arve Knudsen <arve.knudsen@gmail.com>
Building new version of mimir-build-image. After image is built and pushed to Docker Hub, a new commit will automatically be added to this PR with new image version |
Building new version of mimir-build-image. After image is built and pushed to Docker Hub, a new commit will automatically be added to this PR with new image version |
Building new version of mimir-build-image. After image is built and pushed to Docker Hub, a new commit will automatically be added to this PR with new image version |
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.
Left a nit, I think linting will still fail for a couple of cases.
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.
Sorry, my suggestion got lost in the previous review.
Co-authored-by: Arve Knudsen <arve.knudsen@gmail.com>
Indeed, I do wish the linter would report all the errors at once on the CI rather than reporting them in batches. |
It's the easiest to lint locally. |
Building new version of mimir-build-image. After image is built and pushed to Docker Hub, a new commit will automatically be added to this PR with new image version |
Yeah, having to fall back to that it seems. I was misled by the last round (having only one error reported) into thinking I am done 🙈 |
Building new version of mimir-build-image. After image is built and pushed to Docker Hub, a new commit will automatically be added to this PR with new image version |
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, thanks!
Thanks for the review @aknuds1! |
Signed-off-by: Arve Knudsen <arve.knudsen@gmail.com>
86c300f
to
4bed73e
Compare
Not building new version of mimir-build-image. This PR modifies |
What this PR does
Upgrades Go version in mimir-build-image.
This required an upgrade to
golangci-lint
. In turn, the upgrade of this introduced a new linter rule for constant format strings (which in rare cases can be a security thing). Fixed all violations of this new linter rule.Which issue(s) this PR fixes or relates to
n/a
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]
.about-versioning.md
updated with experimental features.