Add automated Go version update workflow

[mpryc]

Summary

Add a thin caller workflow for the centralized Go version update automation.

This workflow calls the reusable update-go-version workflow from
medik8s/.github, which:

• Updates go.mod to the target Go minor version (drops .0 suffix)
• Removes the toolchain directive (patch versions handled by CI builder)
• Runs go mod tidy + go mod vendor
• Updates .ci-operator.yaml builder image tag
• Verifies build passes
• Creates a PR with all changes

Runs weekly (Monday 8:00 UTC) and on manual dispatch. Supports dry-run mode.

Depends-On: medik8s/.github#21

Test plan

• Merge the .github PR first
• Run this workflow via workflow_dispatch with dry-run enabled
• Verify the generated PR has correct changes

[coderabbitai]

Warning

Review limit reached

@mpryc, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 57 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e92d5777-18ed-44af-a05a-df5126c8fe12

📥 Commits

Reviewing files that changed from the base of the PR and between e345299 and ab90508.

📒 Files selected for processing (1)

• .github/workflows/go-update.yaml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mpryc
Once this PR has been reviewed and has the lgtm label, please assign clobrano 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:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@mpryc: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/4.23-openshift-e2e	ab90508	link	true	/test 4.23-openshift-e2e
ci/prow/5.0-openshift-e2e	ab90508	link	true	/test 5.0-openshift-e2e

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.