Use go.mod file for Go version in workflows #119
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates all GitHub Actions workflows to use the Go version specified in the
go.mod
file instead of maintaining a separateGO_VERSION
environment variable.Changes
All workflow files now use
go-version-file: 'go.mod'
for theactions/setup-go@v6
action:Previously, workflows used a
GO_VERSION
environment variable:The
GO_VERSION
environment variable has been removed from all workflow files, makinggo.mod
the single source of truth for the Go toolchain version.Benefits
go.mod
)go.mod
go.mod
, not every workflow filego.mod
Affected Workflows
.github/workflows/main.yml
(8 setup-go steps).github/workflows/pr.yml
(8 setup-go steps).github/workflows/release.yml
(1 setup-go step).github/workflows/scan.yml
(1 setup-go step).github/workflows/vulncheck.yml
(1 setup-go step)All workflows have been verified to build and test successfully using Go 1.25.2 as specified in
go.mod
.Original prompt
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.