Skip to content
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

chore: run CI with Go version from mod file #462

Merged
merged 1 commit into from
May 14, 2024
Merged

Conversation

ctreatma
Copy link
Contributor

@ctreatma ctreatma commented May 13, 2024

Using the go.mod to drive Go version choice in CI makes it easier to upgrade to newer versions of Go. Since this CLI is shipped as a binary and not meant to be used as a module, there's not much reason to do matrix testing on multiple versions of Go.

This was broken out of #461 because the E2E test workflow uses a pull_request_target trigger. That trigger means that the workflow always uses the workflow configuration from the main branch, so it's impossible for the E2E workflow to pass on that PR because--if we don't merge this PR first--the workflow configuration has to be updated in order to run on a different version of Go.

@ctreatma ctreatma force-pushed the go-version-from-mod branch from 80a8712 to 34b23ee Compare May 13, 2024 19:11
@ctreatma ctreatma marked this pull request as ready for review May 13, 2024 19:11
@displague displague merged commit d7d3645 into main May 14, 2024
6 checks passed
@displague displague deleted the go-version-from-mod branch May 14, 2024 20:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants