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

ci: upgrade to Go 1.19.1 #9812

Merged
merged 3 commits into from
Sep 13, 2022
Merged

ci: upgrade to Go 1.19.1 #9812

merged 3 commits into from
Sep 13, 2022

Conversation

milas
Copy link
Contributor

@milas milas commented Sep 6, 2022

What I did
Go released 1.18.6 + 1.19.1 today which fix a couple CVEs. (golang.org/x/net also has a related fix.)

This jumps from 1.18.5 -> 1.19.1 since it was on the to-do list regardless :)

Related issue
https://groups.google.com/g/golang-announce/c/x49AQzIVX-s

(not mandatory) A picture of a cute animal, if possible in relation with what you did
Photo of a rusty-spotted cat moving stealthily along a log

@milas milas requested a review from a team September 6, 2022 21:45
@milas milas self-assigned this Sep 6, 2022
Go released 1.18.6 + 1.19.1 today which fix a couple
CVEs. (`golang.org/x/net` also has a related fix.)

This jumps from 1.18.5 -> 1.19.1 since it was on the
to-do list regardless :)

Signed-off-by: Milas Bowman <[email protected]>
@@ -19,7 +19,6 @@ on:
default: "false"

env:
GO_VERSION: "1.18.5" # for non sandboxed e2e tests
Copy link
Member

Choose a reason for hiding this comment

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

Note that the release pipeline is still on 1.18; does the CI matrix also test against that version?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The release pipeline in docker/docker-ce-packaging, right? (IIRC we settled on it calls make build from the Makefile in this repo, which does a "local" go build inside of its container but not using buildx bake for the actual Compose build)

How do we generally handle that for other projects packaged by it? Something like this?

  • Upgrade project CI to default to Go n+1
  • Continue running project CI against Go n & n+1
  • Once all projects on Go n+1, change packaging to use Go n+1
  • Drop Go n from project CI

cc @glours if you have opinions

@thaJeztah
Copy link
Member

You'll have to update golangci-lint to v1.49 probably; note that there's some linters being deprecated (and/or replaced); docker/cli#3768

> [lint 1/1] RUN --mount=type=bind,target=.     --mount=type=cache,target=/root/.cache     --mount=from=golangci-lint,source=/usr/bin/golangci-lint,target=/usr/bin/golangci-lint     golangci-lint run --build-tags "e2e,kube" ./...:
#21 9.836 panic: load embedded ruleguard rules: rules/rules.go:13: can't load fmt
#21 9.836 
#21 9.836 goroutine 1 [running]:
#21 9.836 github.com/go-critic/go-critic/checkers.init.22()
#21 9.836 	github.com/go-critic/[email protected]/checkers/embedded_rules.go:47 +0x4b4

Need a compatible version for 1.19

Signed-off-by: Milas Bowman <[email protected]>
@@ -143,7 +142,8 @@ jobs:
name: Set up Go
uses: actions/setup-go@v3
with:
go-version: ${{ env.GO_VERSION }}
go-version-file: 'go.mod'
Copy link
Collaborator

Choose a reason for hiding this comment

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

Reading minds! I was about to make this change!

@glours glours merged commit 1ed37ef into docker:v2 Sep 13, 2022
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.

4 participants