Skip to content

NO-ISSUE: Synchronize From Upstream Repositories#1192

Merged
openshift-merge-bot[bot] merged 4 commits intoopenshift:mainfrom
openshift-bot:synchronize-upstream
Jan 14, 2026
Merged

NO-ISSUE: Synchronize From Upstream Repositories#1192
openshift-merge-bot[bot] merged 4 commits intoopenshift:mainfrom
openshift-bot:synchronize-upstream

Conversation

@openshift-bot
Copy link
Copy Markdown
Contributor

The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:

Date Commit Author Message
2026-01-13 07:41:36 operator-framework/operator-lifecycle-manager@a3cc0c4 dependabot[bot] 🌱 Bump github.com/prometheus/common from 0.67.4 to 0.67.5 (#3731)
2026-01-13 07:44:20 operator-framework/operator-lifecycle-manager@0efadc5 dependabot[bot] 🌱 Bump github.com/onsi/ginkgo/v2 from 2.27.3 to 2.27.5 (#3735)
2026-01-13 12:28:04 operator-framework/operator-lifecycle-manager@b8a965c dependabot[bot] 🌱 Bump golang.org/x/net from 0.48.0 to 0.49.0 (#3734)
2026-01-13 12:30:57 operator-framework/operator-lifecycle-manager@7890bdc dependabot[bot] 🌱 Bump github.com/onsi/gomega from 1.38.3 to 1.39.0 (#3736)

This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.

/cc @openshift/openshift-team-operator-framework

dependabot Bot added 4 commits January 14, 2026 00:03
Bumps [github.com/prometheus/common](https://github.com/prometheus/common) from 0.67.4 to 0.67.5.
- [Release notes](https://github.com/prometheus/common/releases)
- [Changelog](https://github.com/prometheus/common/blob/main/CHANGELOG.md)
- [Commits](prometheus/common@v0.67.4...v0.67.5)

---
updated-dependencies:
- dependency-name: github.com/prometheus/common
  dependency-version: 0.67.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: a3cc0c45696f09981c5954cb212dcf9ea7579ed4
Bumps [github.com/onsi/ginkgo/v2](https://github.com/onsi/ginkgo) from 2.27.3 to 2.27.5.
- [Release notes](https://github.com/onsi/ginkgo/releases)
- [Changelog](https://github.com/onsi/ginkgo/blob/master/CHANGELOG.md)
- [Commits](onsi/ginkgo@v2.27.3...v2.27.5)

---
updated-dependencies:
- dependency-name: github.com/onsi/ginkgo/v2
  dependency-version: 2.27.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: 0efadc5e36b4882f9c9ad36393cfda7e4bb8afc1
Bumps [golang.org/x/net](https://github.com/golang/net) from 0.48.0 to 0.49.0.
- [Commits](golang/net@v0.48.0...v0.49.0)

---
updated-dependencies:
- dependency-name: golang.org/x/net
  dependency-version: 0.49.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: b8a965c37ae13ad064de567b1999a5b4b24c0474
Bumps [github.com/onsi/gomega](https://github.com/onsi/gomega) from 1.38.3 to 1.39.0.
- [Release notes](https://github.com/onsi/gomega/releases)
- [Changelog](https://github.com/onsi/gomega/blob/master/CHANGELOG.md)
- [Commits](onsi/gomega@v1.38.3...v1.39.0)

---
updated-dependencies:
- dependency-name: github.com/onsi/gomega
  dependency-version: 1.39.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: 7890bdca55cc8fa1ce3cfb8997df8c6b81725752
@openshift-bot openshift-bot added 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. labels Jan 14, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 14, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@openshift-bot: This pull request explicitly references no jira issue.

Details

In response to this:

The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:

Date Commit Author Message
2026-01-13 07:41:36 operator-framework/operator-lifecycle-manager@a3cc0c4 dependabot[bot] 🌱 Bump github.com/prometheus/common from 0.67.4 to 0.67.5 (#3731)
2026-01-13 07:44:20 operator-framework/operator-lifecycle-manager@0efadc5 dependabot[bot] 🌱 Bump github.com/onsi/ginkgo/v2 from 2.27.3 to 2.27.5 (#3735)
2026-01-13 12:28:04 operator-framework/operator-lifecycle-manager@b8a965c dependabot[bot] 🌱 Bump golang.org/x/net from 0.48.0 to 0.49.0 (#3734)
2026-01-13 12:30:57 operator-framework/operator-lifecycle-manager@7890bdc dependabot[bot] 🌱 Bump github.com/onsi/gomega from 1.38.3 to 1.39.0 (#3736)

This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.

/cc @openshift/openshift-team-operator-framework

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 Jan 14, 2026

@openshift-bot: GitHub didn't allow me to request PR reviews from the following users: openshift/openshift-team-operator-framework.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:

Date Commit Author Message
2026-01-13 07:41:36 operator-framework/operator-lifecycle-manager@a3cc0c4 dependabot[bot] 🌱 Bump github.com/prometheus/common from 0.67.4 to 0.67.5 (#3731)
2026-01-13 07:44:20 operator-framework/operator-lifecycle-manager@0efadc5 dependabot[bot] 🌱 Bump github.com/onsi/ginkgo/v2 from 2.27.3 to 2.27.5 (#3735)
2026-01-13 12:28:04 operator-framework/operator-lifecycle-manager@b8a965c dependabot[bot] 🌱 Bump golang.org/x/net from 0.48.0 to 0.49.0 (#3734)
2026-01-13 12:30:57 operator-framework/operator-lifecycle-manager@7890bdc dependabot[bot] 🌱 Bump github.com/onsi/gomega from 1.38.3 to 1.39.0 (#3736)

This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.

/cc @openshift/openshift-team-operator-framework

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
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jan 14, 2026

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: openshift-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

1 similar comment
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jan 14, 2026

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: openshift-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

@jianzhangbjz
Copy link
Copy Markdown
Contributor

/retest

@jianzhangbjz
Copy link
Copy Markdown
Contributor

/verified by pass

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jan 14, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@jianzhangbjz: This PR has been marked as verified by pass.

Details

In response to this:

/verified by pass

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.

@jianzhangbjz
Copy link
Copy Markdown
Contributor

It failed at

curl: (56) OpenSSL SSL_read: Connection reset by peer, errno 104
gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
...
  * could not run steps: step ci-image failed: error occurred handling build ci-image-amd64: the build ci-image-amd64 failed after 4m1s with reason DockerBuildFailed: Dockerfile build strategy has failed. 

@jianzhangbjz
Copy link
Copy Markdown
Contributor

/retest-required

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jan 14, 2026

@openshift-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.

@openshift-merge-bot openshift-merge-bot Bot merged commit f54c3eb into openshift:main Jan 14, 2026
15 checks passed
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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants