Skip to content

Bump kkp go dependency for 2.28.0-rc.1 #7411

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

Merged
merged 1 commit into from
Jun 9, 2025

Conversation

mohamed-rafraf
Copy link
Member

What this PR does / why we need it:
This PR bumps KKP Go Dependency to prepare 2.28.0-rc.1
Which issue(s) this PR fixes:

Fixes #

What type of PR is this?

/kind chore

Special notes for your reviewer:

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

NONE

Documentation:

NONE

@kubermatic-bot kubermatic-bot added kind/chore Updating grunt tasks etc; no production code changes. release-note-none Denotes a PR that doesn't merit a release note. docs/none Denotes a PR that doesn't need documentation (changes). dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. labels Jun 9, 2025
@mohamed-rafraf
Copy link
Member Author

/assign

@kubermatic-bot kubermatic-bot added the do-not-merge/code-freeze Indicates that a PR should not merge because it has not been approved for code freeze yet. label Jun 9, 2025
@kubermatic-bot kubermatic-bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jun 9, 2025
@mohamed-rafraf
Copy link
Member Author

/milestone KKP 2.28

@kubermatic-bot kubermatic-bot added this to the KKP 2.28 milestone Jun 9, 2025
@mohamed-rafraf
Copy link
Member Author

/cc @Waseem826

@kubermatic-bot kubermatic-bot requested a review from Waseem826 June 9, 2025 07:34
@mohamed-rafraf mohamed-rafraf added the code-freeze-approved Indicates a PR has been approved by release managers during code freeze. label Jun 9, 2025
@kubermatic-bot kubermatic-bot added sig/api Denotes a PR or issue as being assigned to SIG API. and removed do-not-merge/code-freeze Indicates that a PR should not merge because it has not been approved for code freeze yet. labels Jun 9, 2025
Copy link
Contributor

@Waseem826 Waseem826 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 Jun 9, 2025
@kubermatic-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Waseem826

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
Copy link
Contributor

LGTM label has been added.

Git tree hash: 00cd83b453fae0fbd57aeef20391364aae95b12c

@kubermatic-bot kubermatic-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 9, 2025
@kubermatic-bot kubermatic-bot merged commit 84dbdd2 into kubermatic:main Jun 9, 2025
8 checks passed
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. code-freeze-approved Indicates a PR has been approved by release managers during code freeze. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. docs/none Denotes a PR that doesn't need documentation (changes). kind/chore Updating grunt tasks etc; no production code changes. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. sig/api Denotes a PR or issue as being assigned to SIG API. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants