OCPBUGS-76460,OCPBUGS-74928: Synchronize From Upstream Repositories by openshift-bot · Pull Request #1244 · openshift/operator-framework-olm

openshift-bot · 2026-02-27T14:01:54Z

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

Date	Commit	Author	Message
2026-02-25 15:07:15	operator-framework/operator-lifecycle-manager@abb8e1f	WSandboxedOCCodeBot	fix: upgrade Go to 1.25.7 to resolve CVE-2025-68121 (#3776)
2026-02-25 20:20:47	operator-framework/operator-lifecycle-manager@9fe62d8	dependabot[bot]	Bump goreleaser/goreleaser-action from 6 to 7 (#3775)
2026-02-26 09:01:08	operator-framework/operator-lifecycle-manager@521a89f	Todd Short	Update operator-framework/api to v0.40.0 (#3777)
2026-03-02 18:09:46	operator-framework/operator-lifecycle-manager@f6925fd	Jordan Keister	bumping o-f components (#3779)
2026-02-04 16:44:17	operator-framework/operator-registry@9fa4d9b	Per Goncalves da Silva	Add pedjak to OWNERS (#1902)
2026-02-05 14:13:38	operator-framework/operator-registry@a40ca89	dependabot[bot]	Bump google.golang.org/grpc/cmd/protoc-gen-go-grpc from 1.6.0 to 1.6.1 (#1903)
2026-02-06 08:23:35	operator-framework/operator-registry@9a6641c	dependabot[bot]	Bump go.podman.io/common from 0.66.1 to 0.67.0 (#1907)
2026-02-06 08:26:19	operator-framework/operator-registry@568b220	dependabot[bot]	Bump github.com/grpc-ecosystem/grpc-health-probe from 0.4.44 to 0.4.45 (#1908)
2026-02-10 15:36:00	operator-framework/operator-registry@2634c9a	dependabot[bot]	Bump the golang-x-deps group across 1 directory with 3 updates (#1911)
2026-02-11 15:13:39	operator-framework/operator-registry@691fb0f	dependabot[bot]	Bump github.com/mattn/go-sqlite3 from 1.14.33 to 1.14.34 (#1913)
2026-02-11 15:16:40	operator-framework/operator-registry@9eb4b5f	dependabot[bot]	Bump the k8s-dependencies group with 4 updates (#1912)
2026-02-13 11:23:19	operator-framework/operator-registry@01a4def	dependabot[bot]	Bump google.golang.org/grpc from 1.78.0 to 1.79.0 (#1915)
2026-02-18 05:47:49	operator-framework/operator-registry@7bdb135	dependabot[bot]	Bump google.golang.org/grpc from 1.79.0 to 1.79.1 (#1916)
2026-02-23 10:16:31	operator-framework/operator-registry@81aee76	Jordan Keister	adding olm.bundle image/relatedImages pullspec format validation (#1905)
2026-02-23 10:22:06	operator-framework/operator-registry@f410a39	Jordan Keister	handle cases where spec.version.release is a number instead of string (#1909)
2026-02-27 02:41:48	operator-framework/operator-registry@1731fc8	Todd Short	Update to go 1.25.7 (#1918)
2026-02-27 04:32:13	operator-framework/operator-registry@ce760e1	dependabot[bot]	Bump github.com/operator-framework/api from 0.39.0 to 0.40.0 (#1917)
2026-02-27 04:35:00	operator-framework/operator-registry@8811033	dependabot[bot]	Bump actions/download-artifact from 7 to 8 (#1919)
2026-02-27 04:37:35	operator-framework/operator-registry@7474e67	dependabot[bot]	Bump actions/upload-artifact from 6 to 7 (#1920)
2026-02-27 21:31:43	operator-framework/operator-registry@4bf3823	Jordan Keister	bumping api to capture go bumps across the whole o-f set (#1921)
2026-02-17 15:49:09	operator-framework/api@1b5c3ea	dependabot[bot]	Bump the k8s-dependencies group with 4 updates (#478)
2026-02-18 15:15:40	operator-framework/api@63554ab	Jordan Keister	add bundle relatedimage image pullspec validation (#475)
2026-02-24 15:39:18	operator-framework/api@7641ce3	Todd Short	Add OpenAPIModelName() generation for v1alpha1 and lib/version types (#477)
2026-02-25 16:22:49	operator-framework/api@afd36f6	Camila Macedo	Upgrade from go 1.25.3 to 1.25.7 (#474)

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

openshift-ci-robot · 2026-02-27T14:01:57Z

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

Details

In response to this:

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 · 2026-02-27T14:01:58Z

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

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 · 2026-02-27T14:02:23Z

[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:

DOWNSTREAM_OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

openshift-ci · 2026-02-27T14:02:24Z

[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:

DOWNSTREAM_OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

jianzhangbjz · 2026-02-28T01:15:44Z

/retitle OCPBUGS-76460: Synchronize From Upstream Repositories

openshift-ci-robot · 2026-02-28T01:15:52Z

@openshift-bot: This pull request references Jira Issue OCPBUGS-76460, which is valid.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.22.0) matches configured target version for branch (4.22.0)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @huangmingxia

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

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 · 2026-02-28T01:16:25Z

Hi @huangmingxia , could you help pre-merge verify it? Thanks!
/assign @huangmingxia

openshift-ci-robot · 2026-03-01T00:04:55Z

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

Details

In response to this:

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.

huangmingxia · 2026-03-02T08:25:09Z

Pre-merge testing on the Hive side passed. The Hive operator was successfully installed via both non-OLM and OLM on OCP 4.22.

Hi @jianzhangbjz Should I add the verified label to this PR?

tmshort · 2026-03-02T20:42:07Z

/retitle OCPBUGS-74928: Synchronize From Upstream Repositories

openshift-ci-robot · 2026-03-02T20:42:22Z

@openshift-bot: This pull request references Jira Issue OCPBUGS-74928, which is invalid:

expected the bug to target the "4.22.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

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.

tmshort · 2026-03-02T20:47:34Z

/jira refresh

openshift-ci-robot · 2026-03-02T20:47:40Z

@tmshort: This pull request references Jira Issue OCPBUGS-74928, which is valid.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.22.0) matches configured target version for branch (4.22.0)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (bandrade@redhat.com), skipping review request.

Details

In response to this:

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 · 2026-03-03T00:53:34Z

Hi @jianzhangbjz Should I add the verified label to this PR?

Thanks for your verification! Since a new fix(OCPBUGS-74928) was added to this PR, waiting for @bandrade 's verification.
/assign @bandrade

jianzhangbjz · 2026-03-03T01:17:08Z

/retest-required

tmshort · 2026-03-03T14:52:57Z

/retest

tmshort · 2026-03-03T14:53:54Z

/lgtm

grokspawn · 2026-03-03T15:35:20Z

/retest

tmshort · 2026-03-03T21:16:47Z

/retest

openshift-ci-robot · 2026-03-04T00:09:48Z

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

Details

In response to this:

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 · 2026-03-04T00:38:43Z

/retitle OCPBUGS-76460,OCPBUGS-74928: Synchronize From Upstream Repositories

openshift-ci-robot · 2026-03-04T00:38:53Z

@openshift-bot: This pull request references Jira Issue OCPBUGS-76460, which is valid.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.22.0) matches configured target version for branch (4.22.0)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @huangmingxia

This pull request references Jira Issue OCPBUGS-74928, which is valid.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.22.0) matches configured target version for branch (4.22.0)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (bandrade@redhat.com), skipping review request.

Details

In response to this:

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.

tmshort · 2026-03-04T14:49:04Z

/retest

bandrade · 2026-03-04T19:07:49Z

/label qe-approved
/verified by @bandrade

openshift-ci-robot · 2026-03-04T19:08:01Z

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

Details

In response to this:

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 · 2026-03-04T19:08:06Z

@openshift-bot: This pull request references Jira Issue OCPBUGS-76460, which is valid.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.22.0) matches configured target version for branch (4.22.0)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @huangmingxia

This pull request references Jira Issue OCPBUGS-74928, which is valid.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.22.0) matches configured target version for branch (4.22.0)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (bandrade@redhat.com), skipping review request.

Details

In response to this:

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 · 2026-03-04T19:12:18Z

@openshift-bot: Jira Issue OCPBUGS-76460: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-76460 has been moved to the MODIFIED state.

Jira Issue Verification Checks: Jira Issue OCPBUGS-74928
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-74928 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

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-robot · 2026-03-05T12:54:28Z

Fix included in accepted release 4.22.0-0.nightly-2026-03-05-070435

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 Feb 27, 2026

openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 27, 2026

oceanc80 mentioned this pull request Feb 27, 2026

chore(deps): upgrade go to 1.25.7 to address CVE-2025-68121 #1242

Closed

openshift-ci bot changed the title ~~NO-ISSUE: Synchronize From Upstream Repositories~~ OCPBUGS-76460: Synchronize From Upstream Repositories Feb 28, 2026

openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Feb 28, 2026

openshift-ci bot requested a review from huangmingxia February 28, 2026 01:15

openshift-ci bot assigned huangmingxia Feb 28, 2026

openshift-bot changed the title ~~OCPBUGS-76460: Synchronize From Upstream Repositories~~ NO-ISSUE: Synchronize From Upstream Repositories Mar 1, 2026

openshift-ci-robot removed jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Mar 1, 2026

openshift-ci bot changed the title ~~NO-ISSUE: Synchronize From Upstream Repositories~~ OCPBUGS-74928: Synchronize From Upstream Repositories Mar 2, 2026

openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Mar 2, 2026

openshift-ci-robot mentioned this pull request Mar 2, 2026

OCPBUGS-74928: Synchronize From Upstream Repositories openshift/operator-framework-operator-controller#648

Merged

openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Mar 2, 2026

openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Mar 3, 2026

openshift-ci bot assigned bandrade Mar 3, 2026

openshift-ci bot assigned tmshort Mar 3, 2026

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 3, 2026

openshift-bot changed the title ~~OCPBUGS-76460,OCPBUGS-74928: Synchronize From Upstream Repositories~~ NO-ISSUE: Synchronize From Upstream Repositories Mar 4, 2026

openshift-ci-robot removed jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Mar 4, 2026

openshift-ci bot changed the title ~~NO-ISSUE: Synchronize From Upstream Repositories~~ OCPBUGS-76460,OCPBUGS-74928: Synchronize From Upstream Repositories Mar 4, 2026

openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Mar 4, 2026

openshift-ci-robot mentioned this pull request Mar 4, 2026

OCPBUGS-76460, OCPBUGS-75921, MON-4513: Synchronize From Upstream Repositories #1237

Merged

openshift-ci-robot mentioned this pull request Mar 4, 2026

OCPBUGS-74928: Bump github.com/operator-framework/api from 0.39.0 to 0.41.0 operator-framework/operator-marketplace#728

Merged

openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Mar 4, 2026

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 4, 2026

openshift-merge-bot bot merged commit b51083f into openshift:main Mar 4, 2026
15 of 16 checks passed

Conversation

openshift-bot commented Feb 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Feb 27, 2026

Uh oh!

openshift-ci bot commented Feb 27, 2026

Uh oh!

openshift-ci bot commented Feb 27, 2026

Uh oh!

openshift-ci bot commented Feb 27, 2026

Uh oh!

jianzhangbjz commented Feb 28, 2026

Uh oh!

openshift-ci-robot commented Feb 28, 2026

Uh oh!

jianzhangbjz commented Feb 28, 2026

Uh oh!

openshift-ci-robot commented Mar 1, 2026

Uh oh!

huangmingxia commented Mar 2, 2026

Uh oh!

tmshort commented Mar 2, 2026

Uh oh!

openshift-ci-robot commented Mar 2, 2026

Uh oh!

tmshort commented Mar 2, 2026

Uh oh!

openshift-ci-robot commented Mar 2, 2026

Uh oh!

jianzhangbjz commented Mar 3, 2026

Uh oh!

jianzhangbjz commented Mar 3, 2026

Uh oh!

tmshort commented Mar 3, 2026

Uh oh!

tmshort commented Mar 3, 2026

Uh oh!

grokspawn commented Mar 3, 2026

Uh oh!

tmshort commented Mar 3, 2026

Uh oh!

openshift-ci-robot commented Mar 4, 2026

Uh oh!

jianzhangbjz commented Mar 4, 2026

Uh oh!

openshift-ci-robot commented Mar 4, 2026

Uh oh!

tmshort commented Mar 4, 2026

Uh oh!

bandrade commented Mar 4, 2026

Uh oh!

openshift-ci-robot commented Mar 4, 2026

Uh oh!

openshift-ci-robot commented Mar 4, 2026

Uh oh!

Uh oh!

openshift-ci-robot commented Mar 4, 2026

Uh oh!

openshift-merge-robot commented Mar 5, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

11 participants

openshift-bot commented Feb 27, 2026 •

edited

Loading