Skip to content

chore: bump Go from 1.26.5 to 1.27.4 - #770

Open
update-go-version[bot] wants to merge 1 commit into
masterfrom
go-update-1.27.4
Open

update-go-version[bot] wants to merge 1 commit into
masterfrom
go-update-1.27.4

Conversation

@update-go-version

Copy link
Copy Markdown

Go version update: 1.26.5 → 1.27.4

Release notes

Changed files

  • go.mod

This PR was automatically created by the go-update-action.

@openshift-ci

openshift-ci Bot commented Nov 11, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: update-go-version[bot]
Once this PR has been reviewed and has the lgtm label, please assign matousjobanek for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@coderabbitai

coderabbitai Bot commented Nov 11, 2026

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 59bcb8af-59eb-416e-bc8e-4224815d4817

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review

@openshift-ci

openshift-ci Bot commented Nov 11, 2026

Copy link
Copy Markdown

Hi @update-go-version[bot]. Thanks for your PR.

I'm waiting for a codeready-toolchain member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants