Use Go 1.22 in workflows #2060
Merged
Use Go 1.22 in workflows #2060
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
mbg
force-pushed
the
mbg/go/1.22
branch
2 times, most recently
from
98770be
to
f1d661c
Compare
henrymercer
approved these changes
Feb 22, 2024
This was referenced Feb 23, 2024
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.
This PR updates the workflows to use Go 1.22. I have also used this opportunity to disable the automatic caching that the
setup-goAction performs to ensure that this doesn't interfere with our testing since the Go autobuilder should install dependencies for a given project and we don't accidentally want a warm cache to mislead us into thinking that the autobuilder does this successfully when the dependencies actually come from the cache.Merge / deployment checklist