Skip to content

Merge https://github.com/openshift/oadp-must-gather:oadp-dev (5ce8bb8) into oadp-dev#81

Open
oadp-rebasebot-app[bot] wants to merge 1 commit intoopenshift:oadp-devfrom
oadp-rebasebot:rebase-bot-oadp-dev
Open

Merge https://github.com/openshift/oadp-must-gather:oadp-dev (5ce8bb8) into oadp-dev#81
oadp-rebasebot-app[bot] wants to merge 1 commit intoopenshift:oadp-devfrom
oadp-rebasebot:rebase-bot-oadp-dev

Conversation

@oadp-rebasebot-app
Copy link

@oadp-rebasebot-app oadp-rebasebot-app bot commented Mar 10, 2026

Summary by CodeRabbit

  • Chores
    • Upgraded Go toolchain to version 1.25.0
    • Updated core dependencies for improved compatibility with newer Kubernetes versions
    • Refreshed indirect dependencies across the ecosystem to align with current standards

@coderabbitai
Copy link

coderabbitai bot commented Mar 10, 2026

Walkthrough

Go toolchain upgraded from version 1.23.x to 1.25.0. Direct and indirect dependencies updated across Kubernetes client libraries, Azure tooling, Prometheus modules, and ecosystem packages to align with newer API surfaces and compatibility requirements.

Changes

Cohort / File(s) Summary
Dependency Updates
go.mod
Go toolchain upgraded to 1.25.0; direct dependencies updated including kubernetes-csi/external-snapshotter (v8.0.0→v8.2.0), migtools/oadp-non-admin, openshift/oadp-operator, Kubernetes API machinery (v0.33.3), controller-runtime (v0.21.0); indirect dependencies refreshed for Kubernetes ecosystem (k8s.io/\*), Prometheus, Azure, protobuf, and other ecosystem modules.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~22 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Title check ⚠️ Warning The title is a generic merge commit message that does not describe the actual semantic changes made to the codebase (Go version upgrade to 1.25.0, Kubernetes dependency updates, etc.). Use a descriptive title that reflects the main changes, such as 'Upgrade Go to 1.25.0 and update Kubernetes/Velero dependencies' to clearly communicate the changeset's purpose.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Stable And Deterministic Test Names ✅ Passed The repository contains no Ginkgo test files or test suite code; the PR only updates Go module dependencies.
Test Structure And Quality ✅ Passed Pull request is exclusively a go.mod dependency update with no modifications to test files. Repository contains no Ginkgo test files and PR makes only semantic/dependency changes.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.


Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci bot requested review from mpryc and weshayutin March 10, 2026 09:53
@openshift-ci openshift-ci bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Mar 10, 2026
@openshift-ci
Copy link

openshift-ci bot commented Mar 10, 2026

Hi @oadp-rebasebot-app[bot]. Thanks for your PR.

I'm waiting for a openshift 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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@go.mod`:
- Line 69: The go.mod entry for module "github.com/gorilla/websocket" currently
pins an unreleased pseudo-version (v1.5.4-0.20250319132907-e064f32e3674); either
change that require line to the latest stable tag "v1.5.3" or, if you truly need
that specific unreleased commit, replace the pseudo-version with the same value
but add a clear comment explaining why it’s required and include a link to the
upstream PR/issue tracking the v1.5.4 release (reference the module name
"github.com/gorilla/websocket" and the pseudo-version string when editing).

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: e19d494a-d8a7-4a25-ba58-568a5e292231

📥 Commits

Reviewing files that changed from the base of the PR and between 5ce8bb8 and 4e220f4.

⛔ Files ignored due to path filters (1)
  • go.sum is excluded by !**/*.sum
📒 Files selected for processing (1)
  • go.mod

github.com/google/shlex v0.0.0-20191202100458-e7afc7fbc510 // indirect
github.com/google/uuid v1.6.0 // indirect
github.com/gorilla/websocket v1.5.0 // indirect
github.com/gorilla/websocket v1.5.4-0.20250319132907-e064f32e3674 // indirect
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

What is the latest stable tagged release of gorilla/websocket and are there any known issues with version 1.5.3 or 1.5.4?

💡 Result:

  • Latest stable tagged release: v1.5.3 (tagged Jun 14, 2024). [1][2]
  • Is there a stable v1.5.4? No—there’s no v1.5.4 tag/release in the upstream repo; there’s an open request to “Release 1.5.4 with https proxy support”. [3] (Some projects reference an unreleased pseudo-version like v1.5.4-0.20250319132907-e064f32e3674.) [4]

Known reported issues around v1.5.3 / “v1.5.4”

  • v1.5.3 release notes vs reality: An open bug report says v1.5.3 release notes claim hideTempErr was removed, but it still appears (due to a revert), so users upgrading to avoid hideTempErr panics may not get that benefit. [5]
  • Examples/docs: The chat example is reported broken unless CheckOrigin is implemented/adjusted. [6]
  • Toolchain compatibility/testing: A reported issue shows unit tests failing with Go 1.24 (TestPreparedMessage). [7]

Sources:
[1] GitHub tags list (shows v1.5.3 as latest tag, dated Jun 14, 2024) (github.com)
[2] pkg.go.dev (shows module version v1.5.3, published Jun 14, 2024) (pkg.go.dev)
[3] GitHub issue requesting “Release 1.5.4 with https proxy support” (github.com)
[4] GitLab omnibus component list referencing pseudo-version v1.5.4-0... (gitlab-org.gitlab.io)
[5] GitHub issue: v1.5.3 release notes claim hideTempErr removed but it isn’t (github.com)
[6] GitHub issue: chat example does not work (CheckOrigin) (github.com)
[7] GitHub issue: unit test fails with Go 1.24 (github.com)

Citations:


Replace pseudo-version with stable release or document justification.

The dependency uses an unreleased pseudo-version v1.5.4-0.20250319132907-e064f32e3674. The latest stable tagged release is v1.5.3 (June 14, 2024); v1.5.4 has not been officially released. Using unreleased commits in production dependencies introduces maintenance and stability risks. Either downgrade to v1.5.3 or, if this specific unreleased version is required for a critical fix or feature, add a comment documenting the reason and link to the upstream PR/issue tracking the eventual v1.5.4 release.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@go.mod` at line 69, The go.mod entry for module
"github.com/gorilla/websocket" currently pins an unreleased pseudo-version
(v1.5.4-0.20250319132907-e064f32e3674); either change that require line to the
latest stable tag "v1.5.3" or, if you truly need that specific unreleased
commit, replace the pseudo-version with the same value but add a clear comment
explaining why it’s required and include a link to the upstream PR/issue
tracking the v1.5.4 release (reference the module name
"github.com/gorilla/websocket" and the pseudo-version string when editing).

@mpryc
Copy link
Contributor

mpryc commented Mar 10, 2026

/ok-to-test

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Mar 10, 2026
@mpryc
Copy link
Contributor

mpryc commented Mar 10, 2026

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 10, 2026
@openshift-ci
Copy link

openshift-ci bot commented Mar 10, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mpryc, oadp-rebasebot-app[bot]

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 10, 2026
@openshift-ci
Copy link

openshift-ci bot commented Mar 10, 2026

@oadp-rebasebot-app[bot]: all tests passed!

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.

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. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants