Install goreleaser into go 1.18 image for build #4571
Merged
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.
Closes #4523
We still need to stick with goreleaser v0.179.0 because of #4542, but that doesn't inherently stop us from building with a newer Go version. This PR takes the approach of manually installing the correct version into the official Go container (instead of the other way around as in my previous attempt).
Note: I did not use alpine because it doesn't have bash, and our scripts are written for bash. This didn't actually cause problems so far, but I think this choice is more maintainable and future-proof.
I tested this as described in
releasing/cloudbuild.sh
, which should be representative since only one container is involved in this solution. But it would still be great if you could test it with cloud-build-local (which still isn't available to me). 🙏/cc @natasha41575