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

test: using stable/oldstable aliases #282

Merged
merged 2 commits into from
Nov 21, 2023
Merged

Conversation

zucchinidev
Copy link
Contributor

If stable is provided, action will get the latest stable version from the go-versions repository manifest.

If oldstable is provided, when current release is 1.19.x, action will resolve version as 1.18.x, where x is the latest patch release.

We also want to maintain 1.20 version, so we test it.

#186180915

If stable is provided, action will get the latest stable version from
the go-versions repository manifest.

If oldstable is provided, when current release is 1.19.x, action will
resolve version as 1.18.x, where x is the latest patch release.

We also want to maintain 1.20 version, so we test it.

[#186180915](https://www.pivotaltracker.com/story/show/186180915)
Copy link
Member

@blgm blgm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great. This keeps the repo up to date with new Go versions automatically.

At the moment oldstable == 1.20 so we have a duplication, but that's deliberate as oldstable will change in time. We keep 1.20 because that's the version of the Go directive in the go.mod and it's sensible to check that this version always works. We may update it in the future, but want that to be considered rather than automatic.

@blgm blgm merged commit be90826 into main Nov 21, 2023
4 checks passed
@blgm blgm deleted the test_stable_old_1.20_version branch November 21, 2023 17:28
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