Skip to content

NO-JIRA: chore(deps): weekly dependabot consolidation#8578

Open
hypershift-jira-solve-ci[bot] wants to merge 3 commits into
openshift:mainfrom
hypershift-community:fix/weekly-dependabot-consolidation
Open

NO-JIRA: chore(deps): weekly dependabot consolidation#8578
hypershift-jira-solve-ci[bot] wants to merge 3 commits into
openshift:mainfrom
hypershift-community:fix/weekly-dependabot-consolidation

Conversation

@hypershift-jira-solve-ci
Copy link
Copy Markdown

@hypershift-jira-solve-ci hypershift-jira-solve-ci Bot commented May 22, 2026

Summary

Weekly consolidation of dependabot dependency updates.

Consolidated PRs

Commits

  1. chore(deps): update root module dependencies
  2. chore(deps): update vendored dependencies
  3. chore: update remaining generated files

Assisted-by: Claude (via Claude Code)


Note: This PR was auto-generated by the dependabot-triage periodic CI job. See the full report for token usage, cost breakdown, and detailed output.

Summary by CodeRabbit

  • Chores
    • Updated Google API dependencies to newer stable revisions for continued compatibility.
    • Pinned Python IDNA dependency to version 3.15 to address compatibility and stability.

OpenShift CI Bot added 3 commits May 22, 2026 12:23
Weekly dependabot dependency consolidation.
Vendor updates for root module dependency changes.
Additional generated file updates from dependency changes.
@openshift-merge-bot
Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 22, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@hypershift-jira-solve-ci[bot]: This pull request explicitly references no jira issue.

Details

In response to this:

Summary

Weekly consolidation of dependabot dependency updates.

Consolidated PRs

Commits

  1. chore(deps): update root module dependencies
  2. chore(deps): update vendored dependencies
  3. chore: update remaining generated files

Assisted-by: Claude (via Claude Code)

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 22, 2026

Please specify an area label

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.

@openshift-ci openshift-ci Bot requested review from Nirshal and csrwng May 22, 2026 12:32
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 22, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: hypershift-jira-solve-ci[bot]
Once this PR has been reviewed and has the lgtm label, please assign devguyio 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
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 22, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: a0c598d4-5c48-4cc4-85fc-8098dd065397

📥 Commits

Reviewing files that changed from the base of the PR and between 1796aa5 and fc2534c.

⛔ Files ignored due to path filters (5)
  • go.sum is excluded by !**/*.sum
  • vendor/google.golang.org/api/compute/v1/compute-api.json is excluded by !vendor/**, !**/vendor/**
  • vendor/google.golang.org/api/compute/v1/compute-gen.go is excluded by !vendor/**, !**/vendor/**
  • vendor/google.golang.org/api/internal/version.go is excluded by !vendor/**, !**/vendor/**
  • vendor/modules.txt is excluded by !vendor/**, !**/vendor/**
📒 Files selected for processing (2)
  • go.mod
  • hypershift-ci-python/requirements.txt
✅ Files skipped from review due to trivial changes (1)
  • hypershift-ci-python/requirements.txt

📝 Walkthrough

Walkthrough

This pull request updates three dependency pinnings across two package systems: Go module bumps in go.mod (google.golang.org/api v0.279.0 → v0.280.0 and google.golang.org/genproto/googleapis/rpc pseudo-version update) and a Python CI requirement bump (idna 3.10 → 3.15) in hypershift-ci-python/requirements.txt.

Possibly related PRs

  • openshift/hypershift#8464: Updates google.golang.org/api dependency in go.mod from an earlier version, overlapping with this PR's module requirement changes.

Suggested reviewers

  • muraee
  • sjenning

Important

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

❌ Failed checks (1 error, 1 warning)

Check name Status Explanation Resolution
Stable And Deterministic Test Names ❌ Error New Ginkgo tests use fmt.Sprintf with dynamic workload.Name in titles: control_plane_workloads_test.go (11 tests) and control_plane_infrastructure_test.go violate stable test name requirements. Replace fmt.Sprintf test names with static descriptions. Move dynamic workload.Name values into test bodies only, never test titles.
Ipv6 And Disconnected Network Test Compatibility ⚠️ Warning New Ginkgo e2e test assets reference quay.io/openshift/origin-pod:4.19.0, requiring external registry access that fails in disconnected IPv6-only environments. Use internal/mirrored images or add [Skipped:Disconnected] tag. Verify with /payload-job periodic-ci-openshift-release-master-nightly-4.22-e2e-metal-ipi-ovn-ipv6
✅ Passed checks (10 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly identifies this as a weekly dependabot consolidation PR, which matches the actual changes (Go module and Python dependency updates).
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Test Structure And Quality ✅ Passed Ginkgo tests follow quality standards: proper single responsibility, setup/cleanup patterns, appropriate timeouts with Eventually blocks, and meaningful assertion messages.
Microshift Test Compatibility ✅ Passed This PR only updates dependencies (google.golang.org/api, idna, urllib3) and does not add any new Ginkgo e2e tests. The MicroShift compatibility check is not applicable.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR contains only dependency version updates (go.mod and requirements.txt changes). No new Ginkgo e2e tests were added, making the SNO test compatibility check inapplicable.
Topology-Aware Scheduling Compatibility ✅ Passed PR only updates dependency versions in go.mod and requirements.txt with generated/vendor file updates; no deployment manifests, operator code, or scheduling constraints were modified.
Ote Binary Stdout Contract ✅ Passed PR contains only dependency version updates (go.mod, requirements.txt) with no source code changes; OTE stdout contract violations only apply to code changes in process-level functions.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@hypershift-jira-solve-ci hypershift-jira-solve-ci Bot force-pushed the fix/weekly-dependabot-consolidation branch from 1796aa5 to fc2534c Compare May 22, 2026 12:39
@codecov
Copy link
Copy Markdown

codecov Bot commented May 22, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 40.41%. Comparing base (d24af10) to head (fc2534c).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #8578   +/-   ##
=======================================
  Coverage   40.41%   40.41%           
=======================================
  Files         755      755           
  Lines       93235    93235           
=======================================
  Hits        37679    37679           
  Misses      52854    52854           
  Partials     2702     2702           
Flag Coverage Δ
cmd-support 34.44% <ø> (ø)
cpo-hostedcontrolplane 41.76% <ø> (ø)
cpo-other 40.31% <ø> (ø)
hypershift-operator 50.72% <ø> (ø)
other 31.58% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 22, 2026

@hypershift-jira-solve-ci[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

do-not-merge/needs-area jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant