Skip to content

Commit ec42d9c

Browse files
committed
tools/go.mod: Update the go version from 1.22.0 to 1.22.1
Latest release of golangci-lint uses `go 1.22.1` as part of go mod file so when our tooling try to consume this version then following is added for `tools/go.mod` because in our mod file we mention minimum required go version is `1.22.0` and as per go toolchain guideline it should run in in newer toolchain ``` go 1.22.0 toolchain go1.22.5 ``` snip from: https://go.dev/doc/toolchain ``` When the go or toolchain line is newer than the bundled toolchain, the go command runs the newer toolchain instead. For example, when using the go command bundled with Go 1.21.3 in a main module that says go 1.21.9, the go command finds and runs Go 1.21.9 instead. It first looks in the PATH for a program named go1.21.9 and otherwise downloads and caches a copy of the Go 1.21.9 toolchain. ``` - https://github.com/golangci/golangci-lint/blob/v1.61.0/go.mod#L3
1 parent 3a8f554 commit ec42d9c

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

tools/go.mod

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
module github.com/crc-org/crc/tools
22

3-
go 1.22.0
3+
go 1.22.1
44

55
require (
66
github.com/cfergeau/gomod2rpmdeps v0.0.0-20210223144124-2042c4850ca8

update-go-version.sh

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ golang_base_version=$1
1010
echo "Updating golang version to $golang_base_version"
1111

1212
go mod edit -go "${golang_base_version}.0"
13-
go mod edit -go "${golang_base_version}.0" tools/go.mod
13+
go mod edit -go "${golang_base_version}.1" tools/go.mod
1414

1515
sed -i "s,^GOVERSION = 1.[0-9]\+,GOVERSION = ${golang_base_version}," Makefile
1616
sed -i "s,^\(FROM registry.ci.openshift.org/openshift/release:rhel-8-release-golang-\)1.[0-9]\+,\1${golang_base_version}," images/*/Dockerfile

0 commit comments

Comments
 (0)