chore: use oldstable and stable alias a Go version #80
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ldez
force-pushed
the
feat/go-version-alias
branch
from
2df7a85 to
90fa6ed
Compare
|
Thanks for the PR, but I stick to specific major versions on purpose, much like go.mod, because I need to be in control of when I add or remove support for a Go version - and so whether CI is testing that version or not. |
|
So can I create a PR to update the CI to go1.21/go1.22 instead of go1.20/go1.21? |
|
No need, I'll do that - I will need to do a bunch of other things too, like update dependencies and check that the tool works on Go tip today for 1.23. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
It allows the CI to automatically follow the "2 latest minor versions of Go" rule.
https://github.com/actions/setup-go?tab=readme-ov-file#using-stableoldstable-aliases