The "ci" workflow was previously using the "stable" and "oldstable" versions, which as of Go 1.22 introduces a slight change in how go.mod is formatted. This results in errors like
go: updates to go.mod needed; to update it:
go mod tidy
in the workflow logs.
So instead of relying on mutable version labels like "stable" and "oldstable", this commit binds the version of Go used in CI to be what is specified in the repository's go.mod file.
This will allow us the ability to gradually update Go versions without needing to change the version in more than one place, and keep CI predictable.
General:
[x] Have you removed all sensitive information, including but not limited to access keys and passwords?
[x] Have you checked to ensure there aren't other open or closed Pull Requests for the same bug/feature/question?
Pull Request Guidelines:
[ ] Does your submission pass tests?
[ ] Have you added tests?
[x] Are you addressing a single feature in this PR?
[x] Are your commits atomic, addressing one change per commit?
[x] Are you following the conventions of the language?
[x] Have you saved your large formatting changes for a different PR, so we can focus on your work?
[x] Have you explained your rationale for why this feature is needed?
The "ci" workflow was previously using the "stable" and "oldstable" versions, which as of Go 1.22 introduces a slight change in how go.mod is formatted. This results in errors like
in the workflow logs.
So instead of relying on mutable version labels like "stable" and "oldstable", this commit binds the version of Go used in CI to be what is specified in the repository's go.mod file.
This will allow us the ability to gradually update Go versions without needing to change the version in more than one place, and keep CI predictable.
General:
Pull Request Guidelines: