Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump go version to 1.22.2 in v0.57.x line #923

Merged
merged 2 commits into from
Apr 16, 2024
Merged

Conversation

rcmadhankumar
Copy link
Contributor

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:
  • Follows the developer guidelines
  • Relevant tests are added or updated
  • Relevant docs in this repo added or updated
  • Relevant carvel.dev docs added or updated in a separate PR and there's
    a link to that PR
  • Code is at least as readable and maintainable as it was before this
    change

Additional documentation e.g., Proposal, usage docs, etc.:


Signed-off-by: rcmadhankumar <rcmadhankumar@gmail.com>
@rcmadhankumar
Copy link
Contributor Author

/cherry-pick v0.59.x

@rcmadhankumar
Copy link
Contributor Author

/cherry-pick v0.60.x

@rcmadhankumar rcmadhankumar force-pushed the bump-go1.22.2-57.x branch 4 times, most recently from 4ab5115 to 2c775c6 Compare April 16, 2024 09:11
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 <8457124+praveenrewar@users.noreply.github.com>
Signed-off-by: rcmadhankumar <rcmadhankumar@gmail.com>
@rcmadhankumar rcmadhankumar merged commit 8f9c750 into v0.57.x Apr 16, 2024
5 checks passed
@praveenrewar praveenrewar deleted the bump-go1.22.2-57.x branch April 16, 2024 09:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

None yet

2 participants