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

@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

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 | ✅ 14 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Test Structure And Quality ⚠️ Warning The new Ginkgo spec in tests-extension/test/qe/specs/olmv0_custom_schema.go bundles several scenarios into one It and many Expect calls still lack diagnostic messages. Split the custom-schema checks into smaller Its per scenario and add failure messages to setup/core expectations; keep the existing cleanup and timeouts.
✅ Passed checks (14 passed)
Check name Status Explanation
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 PR only bumps gomega and updates sums/modules metadata; no Ginkgo test titles or test code changed.
Microshift Test Compatibility ✅ Passed No Ginkgo e2e tests were added or changed; the PR only bumps gomega in go.mod/go.sum and vendor metadata.
Single Node Openshift (Sno) Test Compatibility ✅ Passed Only go.mod/go.sum/vendor metadata changed; no new Ginkgo e2e tests or topology-sensitive test code was added.
Topology-Aware Scheduling Compatibility ✅ Passed Only gomega dependency metadata changed in go.mod/go.sum/vendor files; no deployment, controller, or scheduling logic was modified.
Ote Binary Stdout Contract ✅ Passed Only dependency metadata changed (go.mod/go.sum/vendor/modules.txt); no Go source or process-level stdout-writing code was modified.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed No Ginkgo e2e tests were added or modified; only go.mod/go.sum and vendor module metadata updated the gomega version.
No-Weak-Crypto ✅ Passed Only dependency metadata changed; no source code or crypto API usage was added in the touched files.
Container-Privileges ✅ Passed PR only updates go.mod/go.sum and vendor/modules.txt; no K8s/container manifests changed and no privileged settings appear in the diff.
No-Sensitive-Data-In-Logs ✅ Passed Only dependency metadata/checksum updates in go.mod/go.sum/vendor/modules.txt; no logging code or sensitive data exposure changed.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title matches the main change: syncing repositories from upstream, including the dependency update.
✨ 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

@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
@perdasilva

Copy link
Copy Markdown
Contributor

/retest

1 similar comment
@tmshort

tmshort commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

/retest

@tmshort

tmshort commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

/verified by tmshort

It's just a bump of a test dependency; if CI passes, it's good.

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jul 2, 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 bump of a test dependency; if CI passes, it's good.

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 834f3e0 and 2 for PR HEAD 45ee27b in total

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 45ee27b to da1e3b9 Compare July 3, 2026 00:03
@openshift-ci-robot openshift-ci-robot removed the verified Signifies that the PR passed pre-merge verification criteria label Jul 3, 2026
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Jul 3, 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-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.

@perdasilva

Copy link
Copy Markdown
Contributor

/retest

@perdasilva

Copy link
Copy Markdown
Contributor

/lgtm

@perdasilva

Copy link
Copy Markdown
Contributor

/verified by ci

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 3, 2026
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jul 3, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@perdasilva: This PR has been marked as verified by ci.

Details

In response to this:

/verified by ci

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 834f3e0 and 2 for PR HEAD da1e3b9 in total

@openshift-ci

openshift-ci Bot commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

@openshift-bot: The following test 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 da1e3b9 link true /test okd-scos-images

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

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.

4 participants