ci: use go go-1.21 during docker build #818
Merged
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
colinlyguo
approved these changes
Jun 11, 2024
omerfirmak
approved these changes
Jun 11, 2024
0xmountaintop
pushed a commit
that referenced
this pull request
Jul 30, 2024
feat: use go go-1.21 during docker build
0xmountaintop
pushed a commit
that referenced
this pull request
Jul 30, 2024
feat: use go go-1.21 during docker build
0xmountaintop
added a commit
that referenced
this pull request
Jul 30, 2024
ci: use go go-1.21 during docker build (#818) feat: use go go-1.21 during docker build Co-authored-by: Péter Garamvölgyi <peter@scroll.io>
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
1. Purpose or design rationale of this PR
Fix failing build after #816, since new ccc build assumes we use go 1.21.
2. PR title
Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:
3. Deployment tag versioning
Has the version in
params/version.gobeen updated?4. Breaking change label
Does this PR have the
breaking-changelabel?