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

[release/v2.24] Bump to Go 1.21.9 #13247

Merged
merged 1 commit into from
Apr 8, 2024

Conversation

xrstf
Copy link
Contributor

@xrstf xrstf commented Apr 5, 2024

What this PR does / why we need it:
Just bumping to the most recent Go version.

What type of PR is this?
/kind chore

Does this PR introduce a user-facing change? Then add your Release Note here:

Bump to Go 1.21.9

Documentation:

NONE

@kubermatic-bot kubermatic-bot added this to the KKP 2.24 milestone Apr 5, 2024
@kubermatic-bot kubermatic-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. kind/chore Updating grunt tasks etc; no production code changes. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Apr 5, 2024
@xrstf xrstf changed the title Bump to Go 1.21.9 [release/v2.24] Bump to Go 1.21.9 Apr 5, 2024
@xrstf
Copy link
Contributor Author

xrstf commented Apr 5, 2024

/retest

Copy link
Member

@embik embik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

@kubermatic-bot kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label Apr 8, 2024
@kubermatic-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: ebae999176fae2bb8a7000059815d4f764d36184

@kubermatic-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: embik

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubermatic-bot kubermatic-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 8, 2024
@embik embik added the cherry-pick-approved Indicates a PR has been approved by release managers. label Apr 8, 2024
@kubermatic-bot kubermatic-bot removed the do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. label Apr 8, 2024
@kubermatic-bot kubermatic-bot merged commit 9551337 into kubermatic:release/v2.24 Apr 8, 2024
23 checks passed
@xrstf xrstf deleted the go1219 branch April 10, 2024 16:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cherry-pick-approved Indicates a PR has been approved by release managers. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. kind/chore Updating grunt tasks etc; no production code changes. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants