feat: bump go to v1.20.10 #578
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
FrankYang0529
force-pushed
the
HARV-SEC-38
branch
2 times, most recently
from
95c1068 to
02940cc
Compare
|
Should we change this line https://github.com/harvester/harvester-installer/blob/master/Dockerfile.dapper#L21 for |
FrankYang0529
force-pushed
the
HARV-SEC-38
branch
from
02940cc to
a491c43
Compare
Signed-off-by: PoAn Yang <[email protected]>
Signed-off-by: PoAn Yang <[email protected]>
FrankYang0529
force-pushed
the
HARV-SEC-38
branch
from
a491c43 to
21597b2
Compare
FrankYang0529
force-pushed
the
HARV-SEC-38
branch
from
57c0d4b to
9111ce0
Compare
Signed-off-by: PoAn Yang <[email protected]>
FrankYang0529
force-pushed
the
HARV-SEC-38
branch
from
9111ce0 to
7eff34b
Compare
|
@Mergifyio backport v1.2 |
✅ Backports have been created
|
|
@Mergifyio backport v1.1 |
✅ Backports have been created
|
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.
Problem:
We used go 1.18, which is EOL in 2023/02.
Solution:
Bump golang to v1.20.10.
Related Issue:
https://github.com/harvester/security/issues/38