Skip to content

Update go version to 1.26.4 in dockerfile#614

Merged
kubermatic-bot merged 1 commit into
kubermatic:mainfrom
rajaSahil:update-go-dockerfile
Jun 15, 2026
Merged

Update go version to 1.26.4 in dockerfile#614
kubermatic-bot merged 1 commit into
kubermatic:mainfrom
rajaSahil:update-go-dockerfile

Conversation

@rajaSahil

Copy link
Copy Markdown
Contributor

What this PR does / why we need it:

  • Update go version to 1.26.4 in dockerfile

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:

Update Go version to 1.26.4 for building image.

Documentation:

NONE

@kubermatic-bot kubermatic-bot added docs/none Denotes a PR that doesn't need documentation (changes). release-note Denotes a PR that will be considered when it comes time to generate release notes. 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. labels Jun 15, 2026
@rajaSahil

Copy link
Copy Markdown
Contributor Author

/assign

@kubermatic-bot kubermatic-bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jun 15, 2026
@rajaSahil

Copy link
Copy Markdown
Contributor Author

/cc @kron4eg

@kubermatic-bot kubermatic-bot requested a review from kron4eg June 15, 2026 08:46
@rajaSahil

Copy link
Copy Markdown
Contributor Author

/hold

@kubermatic-bot kubermatic-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 15, 2026

@kron4eg kron4eg left a comment

Copy link
Copy Markdown
Member

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 15, 2026
Signed-off-by: rajaSahil <sahilraja242@gmail.com>
@kubermatic-bot

Copy link
Copy Markdown
Contributor

LGTM label has been added.

DetailsGit tree hash: 5fa81a4d623e96400b4a3c95be54b271910d3150

@kubermatic-bot

Copy link
Copy Markdown
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 Jun 15, 2026
@rajaSahil rajaSahil force-pushed the update-go-dockerfile branch from 3d6b0e0 to 08e201d Compare June 15, 2026 08:53
@kubermatic-bot kubermatic-bot removed the lgtm Indicates that a PR is ready to be merged. label Jun 15, 2026
@kubermatic-bot kubermatic-bot requested a review from kron4eg June 15, 2026 08:53
@rajaSahil

Copy link
Copy Markdown
Contributor Author

/unhold

@kubermatic-bot kubermatic-bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 15, 2026
@kubermatic-bot kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label Jun 15, 2026
@kubermatic-bot

Copy link
Copy Markdown
Contributor

LGTM label has been added.

DetailsGit tree hash: 48de9d2fb9441171be312149499f81ac3d545945

@kubermatic-bot kubermatic-bot merged commit c45ba3d into kubermatic:main Jun 15, 2026
11 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/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants