Skip to content

Use go.mod as source of Go version number for workflows #132

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

Merged
merged 1 commit into from
Mar 15, 2025

Conversation

per1234
Copy link
Contributor

@per1234 per1234 commented Mar 15, 2025

Go is used in the development and maintenance of the project. A standardized version of Go is used for all operations.

This version is defined in the go directive of the go.mod metadata file.

Go is installed in the GitHub Actions runner environments using the actions/setup-go action, which also must be configured to install the correct version of Go. Previously the version number for use by the actions/setup-go action was defined in each workflow. This meant that we had multiple copies of the Go version information, all of which had to be kept in sync.

Fortunately, support for using go.mod as the source of version information for the actions/setup-go action was recently added:

https://github.com/actions/setup-go/tree/main#getting-go-version-from-the-gomod-file

This means it is now possible for all workflows to get the Go version from a single source.

Go is used in the development and maintenance of the project. A standardized version of Go is used for all operations.

This version is defined in the `go` directive of the go.mod metadata file.

Go is installed in the GitHub Actions runner environments using the "actions/setup-go" action, which also must be
configured to install the correct version of Go. Previously the version number for use by the "actions/setup-go" action
was defined in each workflow. This meant that we had multiple copies of the Go version information, all of which had to
be kept in sync.

Fortunately, support for using `go.mod` as the source of version information for the "actions/setup-go" action was
recently added. This means it is now possible for all workflows to get the Go version from a single source.
@per1234 per1234 added type: enhancement Proposed improvement topic: infrastructure Related to project infrastructure labels Mar 15, 2025
@per1234 per1234 self-assigned this Mar 15, 2025
@per1234 per1234 merged commit b65c61b into arduino:master Mar 15, 2025
20 checks passed
@per1234 per1234 deleted the go_mod-version-source branch March 15, 2025 20:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: infrastructure Related to project infrastructure type: enhancement Proposed improvement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant