As we reevaluate how to best support and maintain Staging Ref in the future, we encourage development teams using this environment to highlight their use cases in the following issue: https://gitlab.com/gitlab-com/gl-infra/software-delivery/framework/software-delivery-framework-issue-tracker/-/issues/36.

Skip to content
Snippets Groups Projects
Unverified Commit beb40839 authored by Ash McKenzie's avatar Ash McKenzie
Browse files

Use go 1.21 in CI

parent e2e31b4a
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
Showing
with 1 addition and 6 deletions
.gitlab-ci.yml
+ 1
− 6
View file @ beb40839
@@ -16,12 +16,7 @@ variables:
TRANSFER_METER_FREQUENCY: "1s"
DOCKER_VERSION: "20.10.15"
BUNDLE_FROZEN: "true"
# Due to https://go.dev/doc/toolchain, we need to keep our base image at Go 1.20
# until GitLab 16.11 is out which will mean we can drop support for Go 1.20
# and make 1.21 our minimum. Using Go 1.21 here now results in the go.mod
# being updated to include the 'toolchain go<version>' directive, which
# causes CI failures.
GO_VERSION: "golang-1.20"
GO_VERSION: "golang-1.21"
GOPATH: $CI_PROJECT_DIR/.GOPATH
DEBIAN_VERSION: "bookworm"
RUBY_VERSION: "ruby-3.2"
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment

As we reevaluate how to best support and maintain Staging Ref in the future, we encourage development teams using this environment to highlight their use cases in the following issue: https://gitlab.com/gitlab-com/gl-infra/software-delivery/framework/software-delivery-framework-issue-tracker/-/issues/36.