Skip to content

NO-ISSUE: Synchronize From Upstream Repositories#988

Merged
openshift-merge-bot[bot] merged 6 commits intoopenshift:mainfrom
openshift-bot:synchronize-upstream
Apr 22, 2025
Merged

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

Conversation

@openshift-bot
Copy link
Copy Markdown
Contributor

@openshift-bot openshift-bot commented Mar 22, 2025 •
edited
Loading

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

Date Commit Author Message
2025-03-21 12:50:04 operator-framework/operator-lifecycle-manager@8e39ae2 dependabot[bot] 🌱 Bump the k8s-dependencies group with 8 updates (#3541)
2025-03-21 12:50:08 operator-framework/operator-lifecycle-manager@6056602 dependabot[bot] 🌱 Bump golang.org/x/time from 0.10.0 to 0.11.0 (#3540)
2025-03-25 19:09:00 operator-framework/operator-lifecycle-manager@0a6499f Mikalai Radchuk Add tests for package migration/renaming (#3547)
2025-03-26 10:03:50 operator-framework/operator-lifecycle-manager@4de2797 dependabot[bot] 🌱 Bump sigs.k8s.io/controller-runtime (#3544)
2025-03-29 14:41:26 operator-framework/operator-lifecycle-manager@98b975a dependabot[bot] 🌱 Bump github.com/onsi/ginkgo/v2 from 2.23.0 to 2.23.3 (#3545)
2025-04-04 07:18:34 operator-framework/operator-lifecycle-manager@dfd0b2b Anik CVE-2025-27144: pin go-jose/v4@v4.0.5 (#3550)

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-bot openshift-bot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Mar 22, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 22, 2025
@openshift-bot openshift-bot added the lgtm Indicates that a PR is ready to be merged. label Mar 22, 2025
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Mar 22, 2025

@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
2025-03-21 12:50:04 operator-framework/operator-lifecycle-manager@8e39ae2 dependabot[bot] 🌱 Bump the k8s-dependencies group with 8 updates (#3541)
2025-03-21 12:50:08 operator-framework/operator-lifecycle-manager@6056602 dependabot[bot] 🌱 Bump golang.org/x/time from 0.10.0 to 0.11.0 (#3540)

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 Mar 22, 2025

@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
2025-03-21 12:50:04 operator-framework/operator-lifecycle-manager@8e39ae2 dependabot[bot] 🌱 Bump the k8s-dependencies group with 8 updates (#3541)
2025-03-21 12:50:08 operator-framework/operator-lifecycle-manager@6056602 dependabot[bot] 🌱 Bump golang.org/x/time from 0.10.0 to 0.11.0 (#3540)

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 Mar 22, 2025

[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 Mar 22, 2025

[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

@perdasilva
Copy link
Copy Markdown
Contributor

perdasilva commented Mar 23, 2025

/retest

@jianzhangbjz
Copy link
Copy Markdown
Contributor

jianzhangbjz commented Mar 24, 2025

/unhold

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 24, 2025
@openshift-bot openshift-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 25, 2025
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 26, 2025
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 26, 2025

New changes are detected. LGTM label has been removed.

@jianzhangbjz
Copy link
Copy Markdown
Contributor

jianzhangbjz commented Mar 26, 2025

/unhold

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 26, 2025
@openshift-bot openshift-bot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged. labels Mar 27, 2025
@jianzhangbjz
Copy link
Copy Markdown
Contributor

jianzhangbjz commented Mar 27, 2025

/unhold

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 27, 2025
@openshift-bot openshift-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 28, 2025
@jianzhangbjz
Copy link
Copy Markdown
Contributor

jianzhangbjz commented Mar 28, 2025

/unhold

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 28, 2025
@openshift-bot openshift-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 29, 2025
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 30, 2025
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 30, 2025

New changes are detected. LGTM label has been removed.

@openshift-bot openshift-bot added the lgtm Indicates that a PR is ready to be merged. label Mar 31, 2025
@openshift-ci-robot openshift-ci-robot removed the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Apr 9, 2025
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Apr 9, 2025

@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
2025-03-21 12:50:04 operator-framework/operator-lifecycle-manager@8e39ae2 dependabot[bot] 🌱 Bump the k8s-dependencies group with 8 updates (#3541)
2025-03-21 12:50:08 operator-framework/operator-lifecycle-manager@6056602 dependabot[bot] 🌱 Bump golang.org/x/time from 0.10.0 to 0.11.0 (#3540)
2025-03-25 19:09:00 operator-framework/operator-lifecycle-manager@0a6499f Mikalai Radchuk Add tests for package migration/renaming (#3547)
2025-03-26 10:03:50 operator-framework/operator-lifecycle-manager@4de2797 dependabot[bot] 🌱 Bump sigs.k8s.io/controller-runtime (#3544)
2025-03-29 14:41:26 operator-framework/operator-lifecycle-manager@98b975a dependabot[bot] 🌱 Bump github.com/onsi/ginkgo/v2 from 2.23.0 to 2.23.3 (#3545)
2025-04-04 07:18:34 operator-framework/operator-lifecycle-manager@dfd0b2b Anik CVE-2025-27144: pin go-jose/v4@v4.0.5 (#3550)

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.

@jianzhangbjz
Copy link
Copy Markdown
Contributor

jianzhangbjz commented Apr 9, 2025

/unhold

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 9, 2025
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Apr 9, 2025

/retest-required

Remaining retests: 0 against base HEAD 84b340e and 2 for PR HEAD d3160ca in total

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

openshift-ci-robot commented Apr 9, 2025

/retest-required

Remaining retests: 0 against base HEAD 84b340e and 2 for PR HEAD d3160ca in total

@openshift-bot openshift-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 10, 2025
@jianzhangbjz
Copy link
Copy Markdown
Contributor

jianzhangbjz commented Apr 10, 2025

/unhold

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 10, 2025
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Apr 10, 2025

/retest-required

Remaining retests: 0 against base HEAD 84b340e and 2 for PR HEAD d3160ca in total

2 similar comments
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Apr 10, 2025

/retest-required

Remaining retests: 0 against base HEAD 84b340e and 2 for PR HEAD d3160ca in total

@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Apr 10, 2025

/retest-required

Remaining retests: 0 against base HEAD 84b340e and 2 for PR HEAD d3160ca in total

@openshift-bot openshift-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 11, 2025
@jianzhangbjz
Copy link
Copy Markdown
Contributor

jianzhangbjz commented Apr 11, 2025

/unhold

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 11, 2025
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Apr 11, 2025

/retest-required

Remaining retests: 0 against base HEAD 84b340e and 2 for PR HEAD d3160ca in total

@openshift-bot openshift-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 12, 2025
@jianzhangbjz
Copy link
Copy Markdown
Contributor

jianzhangbjz commented Apr 14, 2025

/unhold

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 14, 2025
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Apr 14, 2025

/retest-required

Remaining retests: 0 against base HEAD 84b340e and 2 for PR HEAD d3160ca in total

@anik120
Copy link
Copy Markdown
Contributor

anik120 commented Apr 14, 2025

/retest-required

@openshift-bot openshift-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 15, 2025
@jianzhangbjz
Copy link
Copy Markdown
Contributor

jianzhangbjz commented Apr 15, 2025

/unhold

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 15, 2025
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Apr 15, 2025

/retest-required

Remaining retests: 0 against base HEAD 84b340e and 2 for PR HEAD d3160ca in total

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

openshift-ci-robot commented Apr 15, 2025

/retest-required

Remaining retests: 0 against base HEAD 84b340e and 2 for PR HEAD d3160ca in total

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 15, 2025

@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-e2e-aws-ovn d3160ca link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-gcp-olm d3160ca link true /test e2e-gcp-olm

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-bot openshift-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 16, 2025
@tmshort tmshort mentioned this pull request Apr 21, 2025
Merged
@openshift-merge-bot openshift-merge-bot Bot merged commit d3160ca into openshift:main Apr 22, 2025
12 of 15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. 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

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

7 participants

@openshift-bot @openshift-ci-robot @perdasilva @jianzhangbjz @m1kola @tmshort @anik120