-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
chore(deps): update go to 1.22 #13258
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: william.vanhevelingen <william.vanhevelingen@acquia.com>
@@ -339,7 +339,7 @@ endif | |||
$(GOPATH)/bin/swagger: | |||
# update this in Nix when upgrading it here | |||
ifneq ($(USE_NIX), true) | |||
go install github.com/go-swagger/go-swagger/cmd/swagger@v0.28.0 | |||
go install github.com/go-swagger/go-swagger/cmd/swagger@v0.31.0 |
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.
@agilgur5 the swagger update has changed/deleted some files which seems unexpected.
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 haven't analyzed the Swagger update etc yet (not sure yet), but the go.mod
and Dockerfile
+ Dockerfile.windows
need updating for a new Go version as well
Signed-off-by: william.vanhevelingen <william.vanhevelingen@acquia.com>
@agilgur5 if the swagger changes are okay then this is good to merge. |
Fixes: #13188
Motivation
This change updates golang to 1.22
Modifications
ci
/release
workflows were updated to use 1.22go-swagger
was updated to address a panicmake pre-commit -B
is responsible the majority the changesVerification
E2E tests should be enough