Skip to content

NO-ISSUE: Synchronize From Upstream Repositories#1336

Open
openshift-bot wants to merge 1 commit into
openshift:mainfrom
openshift-bot:synchronize-upstream
Open

NO-ISSUE: Synchronize From Upstream Repositories#1336
openshift-bot wants to merge 1 commit into
openshift:mainfrom
openshift-bot:synchronize-upstream

Conversation

@openshift-bot

@openshift-bot openshift-bot commented Jul 1, 2026

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-06-30 07:27:23 operator-framework/operator-lifecycle-manager@d0f9ae3 dependabot[bot] 🌱 Bump github.com/onsi/gomega from 1.42.0 to 1.42.1 (#3861)

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.

/assign @openshift/openshift-team-operator-runtime

Summary by CodeRabbit

  • Chores
    • Updated a testing-related Go dependency to a newer patch version in the project and staging configuration.

@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 Jul 1, 2026
@coderabbitai

coderabbitai Bot commented Jul 1, 2026

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 36346c8b-7fac-4c85-8cdb-9871b0ba792a

📥 Commits

Reviewing files that changed from the base of the PR and between 4793a79 and 45ee27b.

⛔ Files ignored due to path filters (3)
  • go.sum is excluded by !**/*.sum
  • staging/operator-lifecycle-manager/go.sum is excluded by !**/*.sum
  • vendor/modules.txt is excluded by !**/vendor/**, !vendor/**
📒 Files selected for processing (2)
  • go.mod
  • staging/operator-lifecycle-manager/go.mod
✅ Files skipped from review due to trivial changes (2)
  • staging/operator-lifecycle-manager/go.mod
  • go.mod

Walkthrough

This change updates the indirect dependency github.com/onsi/gomega from v1.42.0 to v1.42.1 in both go.mod files. No source code or exported entity changes are included.

Changes

Dependency version update

Layer / File(s) Summary
Gomega version bump
go.mod, staging/operator-lifecycle-manager/go.mod
Updates the required github.com/onsi/gomega module version from v1.42.0 to v1.42.1 in both module manifests.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

Suggested reviewers: rashmigottipati

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title matches the sync-from-upstream dependency update and clearly reflects the main change.
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.
Stable And Deterministic Test Names ✅ Passed Only dependency metadata changed (go.mod/go.sum/vendor); no Ginkgo test titles were added or modified.
Test Structure And Quality ✅ Passed Only go.mod files changed to bump gomega; no Ginkgo test code or test logic was modified, so this checklist is N/A.
Microshift Test Compatibility ✅ Passed The only new e2e spec uses BuildConfig/ImageStream, but BeforeEach calls exutil.SkipMicroshift(oc), which skips on MicroShift via IsMicroshiftCluster.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The only new Ginkgo e2e spec is OLMv0 custom schema; it has no node-count, HA, drain, anti-affinity, or rescheduling assumptions.
Topology-Aware Scheduling Compatibility ✅ Passed PR only updates dependency sync/RBAC and package-server TLS profile logic; no new affinity, topology spread, node selectors, or replica constraints were introduced.
Ote Binary Stdout Contract ✅ Passed Only dependency files changed (go.mod/go.sum/vendor); no main/init/TestMain/suite-setup code was modified, so no stdout contract violation was introduced.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The PR only bumps gomega in go.mod files; no Ginkgo e2e tests or network-dependent test code were added.
No-Weak-Crypto ✅ Passed Only gomega version bumps in go.mod files; no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB, custom crypto, or secret comparisons found.
Container-Privileges ✅ Passed PR only updates go.mod files; no container/K8s manifests were changed, so none of the flagged privilege settings were introduced.
No-Sensitive-Data-In-Logs ✅ Passed Added logs only report TLS profile values and errors; no passwords, tokens, PII, hostnames, or customer data were logged.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@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-06-30 07:27:23 operator-framework/operator-lifecycle-manager@d0f9ae3 dependabot[bot] 🌱 Bump github.com/onsi/gomega from 1.42.0 to 1.42.1 (#3861)

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.

/assign @openshift/openshift-team-operator-runtime

Summary by CodeRabbit

  • Chores
  • Updated an internal test dependency to a newer patch version for improved stability and consistency.

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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 1, 2026
@openshift-ci openshift-ci Bot requested review from joelanford and tmshort July 1, 2026 00:07
@tmshort

tmshort commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

/retest

@tmshort

tmshort commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

/assign

@tmshort

tmshort commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

/retest e2e-aws-upgrade-ovn-signle-node

@tmshort

tmshort commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

/test e2e-aws-upgrade-ovn-single-node

@tmshort

tmshort commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

/verified by tmshort

It's just a dependency update. CI should be sufficient

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jul 1, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@tmshort: This PR has been marked as verified by tmshort.

Details

In response to this:

/verified by tmshort

It's just a dependency update

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-merge-bot

Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD a0451ac and 2 for PR HEAD 4793a79 in total

@tmshort

tmshort commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

/test e2e-aws-upgrade-ovn-single-node

Bumps [github.com/onsi/gomega](https://github.com/onsi/gomega) from 1.42.0 to 1.42.1.
- [Release notes](https://github.com/onsi/gomega/releases)
- [Changelog](https://github.com/onsi/gomega/blob/master/CHANGELOG.md)
- [Commits](onsi/gomega@v1.42.0...v1.42.1)

---
updated-dependencies:
- dependency-name: github.com/onsi/gomega
  dependency-version: 1.42.1
  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: d0f9ae35b6680e8d77f9355d29d4e4340853931d
@openshift-bot openshift-bot force-pushed the synchronize-upstream branch from 4793a79 to 45ee27b Compare July 2, 2026 00:04
@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-06-30 07:27:23 operator-framework/operator-lifecycle-manager@d0f9ae3 dependabot[bot] 🌱 Bump github.com/onsi/gomega from 1.42.0 to 1.42.1 (#3861)

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.

/assign @openshift/openshift-team-operator-runtime

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-robot openshift-ci-robot removed the verified Signifies that the PR passed pre-merge verification criteria label Jul 2, 2026
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Jul 2, 2026
@openshift-ci

openshift-ci Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

[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

@tmshort

tmshort commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

/lgtm

@tmshort

tmshort commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

/retest

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 2, 2026
@openshift-ci

openshift-ci Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

@openshift-bot: 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/okd-scos-images 45ee27b link true /test okd-scos-images
ci/prow/e2e-gcp-ovn 45ee27b link true /test e2e-gcp-ovn

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants