Go version is inconsistent in GitHub workflows

[brooke-hamilton]

Steps to reproduce

We have several GitHub workflows that install Go using the setup-go action. They use a variable named GOVER that is set at the top of each workflow, and later to set the go-version property of the setup-go action. The GOVER variable has values that are different from the Go version set in the go.mod file at the root of the repo.

Here is an example: GOVER is set to 1.22.2. In go.mod, the go version is set to 1.23.0.

Observed behavior

No response

Desired behavior

In all affected workflows:

• Set the go-version-file with the go.mod file from the root of the repo.
• Remove statements that set the go-version property.
• Remove the GOVER variable. (NOTE: the GOVER variable is used in multiple actions called from the workflows.)

See the documentation for the go-version-file property here.

Consider updating the Go version in go.mod to the most recent version.

Workaround

No response

rad Version

Edge

Operating system

No response

Additional context

No response

Would you like to support us?

• Yes, I would like to support you

AB#14258

[radius-triage-bot]

👋 @brooke-hamilton Thanks for filing this bug report.

A project maintainer will review this report and get back to you soon. If you'd like immediate help troubleshooting, please visit our Discord server.

For more information on our triage process please visit our triage overview