Skip to content

NO-ISSUE: Synchronize From Upstream Repositories #67

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 10 commits into from
Feb 1, 2024
Merged

NO-ISSUE: Synchronize From Upstream Repositories #67

merged 10 commits into from
Feb 1, 2024

Conversation

openshift-bot
Copy link

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

Date Commit Author Message
2024-01-23 00:00:41 operator-framework/@96a14c4 dtfranz UPSTREAM: : Add OpenShift specific files
2024-01-23 00:00:41 operator-framework/@1465f56 Alexander Greene UPSTREAM: : Drop commitchecker
2024-01-23 00:00:41 operator-framework/@b5dc027 AOS Automation Release Team UPSTREAM: : Updating ose-olm-operator-controller-container image to be consistent with ART Reconciling with https://github.com/openshift/ocp-build-data/tree/4022cd290f00a44d667dda03f2d78d84a488c7ed/images/ose-olm-operator-controller.yml

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-runtime
/cc @openshift/openshift-team-operator-ecosystem

varshaprasad96 and others added 10 commits January 23, 2024 15:50
@varshaprasad96
✨ Bump rukpak to 0.17.0 (#583)
ef06f40 
This commit makes the following changes:
1. Bump Rukpak to use version 0.17.0
2. Modify the BundleDeployment spec accordingly
   to not specify a bundle template.
3. Introduce `watchNamespaces` field in the spec
   that accepts a list of namespaces to watch.
4. Fix unit and e2e tests accordingly.

Signed-off-by: Varsha Prasad Narsing <varshaprasad96@gmail.com>
Merge branch 'main' into synchronize
fd4d4c6
@dtfranz
UPSTREAM: <carry>: Add OpenShift specific files
c32d5d1 
Signed-off-by: dtfranz <dfranz@redhat.com>
@awgreene
UPSTREAM: <carry>: Drop commitchecker
145248d 
Signed-off-by: Alexander Greene <greene.al1991@gmail.com>
UPSTREAM: <carry>: Updating ose-olm-operator-controller-container ima…
70122fa 
…ge to be consistent with ART

Reconciling with https://github.com/openshift/ocp-build-data/tree/4022cd290f00a44d667dda03f2d78d84a488c7ed/images/ose-olm-operator-controller.yml
UPSTREAM: <drop>: go mod vendor
366ab20
UPSTREAM: <drop>: generate manifests
f88647a
UPSTREAM: <drop>: remove upstream GitHub configuration
d7a1929
UPSTREAM: <drop>: configure the commit-checker
a4936db
UPSTREAM: <drop>: rewrite go mod
8115c89
@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 23, 2024
@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 23, 2024
@openshift-ci-robot
Copy link

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

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
2024-01-23 00:00:41 operator-framework/@96a14c4 dtfranz UPSTREAM: : Add OpenShift specific files
2024-01-23 00:00:41 operator-framework/@1465f56 Alexander Greene UPSTREAM: : Drop commitchecker
2024-01-23 00:00:41 operator-framework/@b5dc027 AOS Automation Release Team UPSTREAM: : Updating ose-olm-operator-controller-container image to be consistent with ART Reconciling with https://github.com/openshift/ocp-build-data/tree/4022cd290f00a44d667dda03f2d78d84a488c7ed/images/ose-olm-operator-controller.yml

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-runtime
/cc @openshift/openshift-team-operator-ecosystem

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 openshift-ci bot requested a review from a team January 23, 2024 19:13
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jan 23, 2024

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

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

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
2024-01-23 00:00:41 operator-framework/@96a14c4 dtfranz UPSTREAM: : Add OpenShift specific files
2024-01-23 00:00:41 operator-framework/@1465f56 Alexander Greene UPSTREAM: : Drop commitchecker
2024-01-23 00:00:41 operator-framework/@b5dc027 AOS Automation Release Team UPSTREAM: : Updating ose-olm-operator-controller-container image to be consistent with ART Reconciling with https://github.com/openshift/ocp-build-data/tree/4022cd290f00a44d667dda03f2d78d84a488c7ed/images/ose-olm-operator-controller.yml

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-runtime
/cc @openshift/openshift-team-operator-ecosystem

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/test-infra repository.

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jan 23, 2024

[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

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 OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jan 23, 2024

[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

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

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD f33e998 and 2 for PR HEAD 8115c89 in total

@kevinrizza
Copy link
Member

/retest

1 similar comment
@kevinrizza
Copy link
Member

/retest

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Feb 1, 2024

@openshift-bot: all tests passed!

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit bc77333 into openshift:main Feb 1, 2024
@openshift-bot
Copy link
Author

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-olm-operator-controller-container-v4.16.0-202402020041.p0.gbc77333.assembly.stream for distgit ose-olm-operator-controller.
All builds following this will include this PR.

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. 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.
6 participants
@openshift-bot @openshift-ci-robot @kevinrizza @varshaprasad96 @dtfranz @awgreene