Skip to content

Bump controller-runtime to 0.23.1#1996

Merged
kubermatic-bot merged 2 commits intokubermatic:mainfrom
archups:bump-controller-runtime-0.23.1
Feb 17, 2026
Merged

Bump controller-runtime to 0.23.1#1996
kubermatic-bot merged 2 commits intokubermatic:mainfrom
archups:bump-controller-runtime-0.23.1

Conversation

@archups
Copy link
Contributor

@archups archups commented Feb 13, 2026

What this PR does / why we need it:
This PR is to bump Go dependencies controller-runtime to 0.23.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:

Bump controller-runtime to 0.23.1

Documentation:

NONE

Additional information: #1997 to track the GolangCI lint staticcheck issue.

Signed-off-by: Archana Sawant <archupsawant@gmail.com>
@archups archups self-assigned this Feb 13, 2026
@kubermatic-bot kubermatic-bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. release-note Denotes a PR that will be considered when it comes time to generate release notes. docs/none Denotes a PR that doesn't need documentation (changes). 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. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Feb 13, 2026
@archups archups force-pushed the bump-controller-runtime-0.23.1 branch from a0ed276 to 62e24a0 Compare February 13, 2026 20:10
Signed-off-by: Archana Sawant <archupsawant@gmail.com>
@archups archups changed the title WIP: Bump controller-runtime to 0.23.1 Bump controller-runtime to 0.23.1 Feb 13, 2026
@kubermatic-bot kubermatic-bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 13, 2026
Copy link
Member

@kron4eg kron4eg 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 Feb 17, 2026
@kubermatic-bot
Copy link
Contributor

LGTM label has been added.

DetailsGit tree hash: c69c7732f8a703eb8208c7eb48bba708663ab954

@kubermatic-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kron4eg

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

The pull request process is described here

Details 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 Feb 17, 2026
@kubermatic-bot kubermatic-bot merged commit 6323ea7 into kubermatic:main Feb 17, 2026
13 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. 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 Denotes a PR that will be considered when it comes time to generate release notes. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. 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

Comments