Bump go version to 1.21.9 in v0.59.x line #924
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
rcmadhankumar
force-pushed
the
bump-go1.22.2-59.x
branch
from
528b852
to
fab8a4b
Compare
rcmadhankumar
changed the title
praveenrewar
approved these changes
Apr 15, 2024
rcmadhankumar
force-pushed
the
bump-go1.22.2-59.x
branch
from
b6f0fd7
to
0306aee
Compare
Signed-off-by: rcmadhankumar <[email protected]>
Use artifact registry url for gb-frontend instead of gcr as images in gcr are not tagged anymore Use registry.k8s.io instead of k8s.gcr.io Bump k8s version in github workflow to 1.21 from 1.16 Signed-off-by: Praveen Rewar <[email protected]>
rcmadhankumar
force-pushed
the
bump-go1.22.2-59.x
branch
from
0306aee
to
8e3a289
Compare
praveenrewar
approved these changes
Apr 16, 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.
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?
Additional Notes for your reviewer:
Review Checklist:
a link to that PR
change
Additional documentation e.g., Proposal, usage docs, etc.: