Skip to content

Conversation

red-hat-konflux-kflux-prd-rh03[bot]
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
github.com/openshift/osde2e-common require digest 2d6094e -> 7806b74

Warning

Some dependencies could not be looked up. Check the warning logs for more information.


Configuration

📅 Schedule: Branch creation - "after 5am on sunday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

To execute skipped test pipelines write comment /ok-to-test.

This PR has been generated by MintMaker (powered by Renovate Bot).

Signed-off-by: red-hat-konflux-kflux-prd-rh03 <206760901+red-hat-konflux-kflux-prd-rh03[bot]@users.noreply.github.com>
Copy link
Contributor Author

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 34 additional dependencies were updated

Details:

Package Change
github.com/onsi/ginkgo/v2 v2.17.1 -> v2.23.4
github.com/onsi/gomega v1.32.0 -> v1.38.0
github.com/prometheus/client_golang v1.16.0 -> v1.23.0
k8s.io/api v0.30.1 -> v0.31.3
k8s.io/apimachinery v0.30.1 -> v0.31.3
k8s.io/client-go v0.30.1 -> v0.31.3
k8s.io/code-generator v0.30.0 -> v0.31.0
sigs.k8s.io/controller-runtime v0.18.0 -> v0.19.0
github.com/cespare/xxhash/v2 v2.2.0 -> v2.3.0
github.com/davecgh/go-spew v1.1.1 -> v1.1.2-0.20180830191138-d8f796af33cc
github.com/go-logr/logr v1.4.1 -> v1.4.3
github.com/go-openapi/swag v0.22.3 -> v0.22.4
github.com/google/go-cmp v0.6.0 -> v0.7.0
github.com/google/pprof v0.0.0-20210720184732-4bb14d4b1be1 -> v0.0.0-20250403155104-27863c87afa6
github.com/google/uuid v1.3.0 -> v1.6.0
github.com/moby/spdystream v0.2.0 -> v0.4.0
github.com/prometheus/client_model v0.4.0 -> v0.6.2
github.com/prometheus/common v0.44.0 -> v0.65.0
github.com/prometheus/procfs v0.12.0 -> v0.16.1
golang.org/x/exp v0.0.0-20220722155223-a9213eeb770e -> v0.0.0-20230515195305-f3d0a9c9a5cc
golang.org/x/mod v0.17.0 -> v0.25.0
golang.org/x/net v0.38.0 -> v0.41.0
golang.org/x/oauth2 v0.27.0 -> v0.30.0
golang.org/x/sync v0.12.0 -> v0.15.0
golang.org/x/sys v0.31.0 -> v0.33.0
golang.org/x/term v0.30.0 -> v0.32.0
golang.org/x/text v0.23.0 -> v0.26.0
golang.org/x/tools v0.21.1-0.20240508182429-e35e4ccd0d2d -> v0.33.0
google.golang.org/protobuf v1.33.0 -> v1.36.6
k8s.io/apiextensions-apiserver v0.30.0 -> v0.31.0
k8s.io/klog/v2 v2.120.1 -> v2.130.1
k8s.io/utils v0.0.0-20230726121419-3b25d923346b -> v0.0.0-20240711033017-18e509b52bc8
sigs.k8s.io/e2e-framework v0.3.0 -> v0.5.0
sigs.k8s.io/yaml v1.3.0 -> v1.4.0

@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 Aug 10, 2025
Copy link
Contributor

openshift-ci bot commented Aug 10, 2025

Hi @red-hat-konflux-kflux-prd-rh03[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.

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.

@samanthajayasinghe
Copy link
Contributor

/test all

@codecov-commenter
Copy link

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 46.35%. Comparing base (9baf918) to head (a7c376a).
⚠️ Report is 4 commits behind head on master.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #216   +/-   ##
=======================================
  Coverage   46.35%   46.35%           
=======================================
  Files          10       10           
  Lines         755      755           
=======================================
  Hits          350      350           
  Misses        395      395           
  Partials       10       10           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@samanthajayasinghe
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 19, 2025
@samanthajayasinghe
Copy link
Contributor

/approve

Copy link
Contributor

openshift-ci bot commented Aug 19, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: red-hat-konflux-kflux-prd-rh03[bot], samanthajayasinghe

The full list of commands accepted by this bot can be found here.

The pull request process is described here

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 Aug 19, 2025
Copy link
Contributor

openshift-ci bot commented Aug 19, 2025

@red-hat-konflux-kflux-prd-rh03: 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/coverage a7c376a link unknown /test coverage
ci/prow/lint a7c376a link unknown /test lint
ci/prow/test a7c376a link unknown /test test
ci/prow/e2e-binary-build-success a7c376a link unknown /test e2e-binary-build-success
ci/prow/images a7c376a link unknown /test images
ci/prow/validate a7c376a link unknown /test validate

Full PR test history. Your PR dashboard.

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.

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD e182361 and 2 for PR HEAD a7c376a in total

@openshift-merge-robot
Copy link
Contributor

PR needs rebase.

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-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 19, 2025
@samanthajayasinghe
Copy link
Contributor

Closing this PR since we can't rebase the PR

@samanthajayasinghe
Copy link
Contributor

/close

@openshift-ci openshift-ci bot closed this Aug 20, 2025
Copy link
Contributor

openshift-ci bot commented Aug 20, 2025

@samanthajayasinghe: Closed this PR.

In response to this:

/close

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.

@samanthajayasinghe
Copy link
Contributor

/label rebase

Copy link
Contributor

openshift-ci bot commented Aug 20, 2025

@samanthajayasinghe: The label(s) /label rebase cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, ux-approved, no-qe, downstream-change-needed, rebase/manual, cluster-config-api-changed, run-integration-tests, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, jira/valid-bug, ok-to-test, stability-fix-approved, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

/label rebase

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.

@samanthajayasinghe
Copy link
Contributor

/label rebase/manual

@openshift-ci openshift-ci bot added the rebase/manual Indicates the PR should not be rebased by the rebasebot. label Aug 20, 2025
@smarthall
Copy link
Contributor

/label rebase

Copy link
Contributor

openshift-ci bot commented Aug 28, 2025

@smarthall: The label(s) /label rebase cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, ux-approved, no-qe, downstream-change-needed, rebase/manual, cluster-config-api-changed, run-integration-tests, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, jira/valid-bug, ok-to-test, stability-fix-approved, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

/label rebase

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.

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. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. rebase/manual Indicates the PR should not be rebased by the rebasebot.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants