Skip to content

Bump grpc - #8314

Merged
kubermatic-bot merged 1 commit into
kubermatic:mainfrom
buraksekili:deps/security-20260918-main
Sep 21, 2026
Merged

kubermatic-bot merged 1 commit into
kubermatic:mainfrom
buraksekili:deps/security-20260918-main

Conversation

@buraksekili

@buraksekili buraksekili commented Sep 18, 2026 •

Copy link
Copy Markdown
Contributor

What this PR does / why we need it:

Updates gRPC to a newer release. No major upgrades: k8s.io pins and the Go directive are unchanged.

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
NONE

Signed-off-by: Burak Sekili <32663655+buraksekili@users.noreply.github.com>
@kubermatic-bot kubermatic-bot added the kind/chore Updating grunt tasks etc; no production code changes. label Sep 18, 2026
@kubermatic-bot

Copy link
Copy Markdown
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@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-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. do-not-merge/test-issue-needed Indicates that a PR should not merge because it's missing one of the test issue labels. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Sep 18, 2026
@buraksekili
buraksekili marked this pull request as ready for review September 21, 2026 12:49
@kubermatic-bot kubermatic-bot added test-issue/none Denotes a PR that doesn't need a test issue (changes). and removed do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. do-not-merge/test-issue-needed Indicates that a PR should not merge because it's missing one of the test issue labels. labels Sep 21, 2026

@ahmadhamzh ahmadhamzh left a comment

Copy link
Copy Markdown
Contributor

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 Sep 21, 2026
@kubermatic-bot

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ahmadhamzh

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

Copy link
Copy Markdown
Contributor

LGTM label has been added.

DetailsGit tree hash: a6a566fc8278bf83b1300c041d8740b15cdd818d

@kubermatic-bot kubermatic-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 21, 2026
@kubermatic-bot
kubermatic-bot merged commit 41b8e2a into kubermatic:main Sep 21, 2026
8 checks passed
@kubermatic-bot kubermatic-bot added this to the KKP 2.31 milestone Sep 21, 2026
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-none Denotes a PR that doesn't merit a release note. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. test-issue/none Denotes a PR that doesn't need a test issue (changes).

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants