Skip to content

NO-ISSUE: Synchronize From Upstream Repositories#783

Merged
openshift-merge-bot[bot] merged 5 commits intoopenshift:masterfrom
openshift-bot:synchronize-upstream
Jun 17, 2024
Merged

NO-ISSUE: Synchronize From Upstream Repositories#783
openshift-merge-bot[bot] merged 5 commits intoopenshift:masterfrom
openshift-bot:synchronize-upstream

Conversation

@openshift-bot
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
2024-06-13 18:09:24 operator-framework/operator-lifecycle-manager@59606f2 Joe Lanford bump of/api to v0.26.0 (#3317)
2024-05-28 09:31:47 operator-framework/api@9698d12 dependabot[bot] Bump github.com/sirupsen/logrus from 1.9.2 to 1.9.3
2024-05-28 09:32:07 operator-framework/api@d6920a4 dependabot[bot] Bump sigs.k8s.io/controller-runtime from 0.18.2 to 0.18.3
2024-06-11 08:06:09 operator-framework/api@e684a59 dependabot[bot] Bump sigs.k8s.io/controller-runtime from 0.18.3 to 0.18.4
2024-06-13 14:13:18 operator-framework/api@5d2d3fb Joe Lanford remove default value of catsrc.spec.grpcPodConfig.securityContextConfig (#342)

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

joelanford and others added 5 commits June 14, 2024 00:02
Signed-off-by: Joe Lanford <joe.lanford@gmail.com>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: 59606f2864ea94bfe8780e075392e0daa27fb9df
Bumps [github.com/sirupsen/logrus](https://github.com/sirupsen/logrus) from 1.9.2 to 1.9.3.
- [Release notes](https://github.com/sirupsen/logrus/releases)
- [Changelog](https://github.com/sirupsen/logrus/blob/master/CHANGELOG.md)
- [Commits](sirupsen/logrus@v1.9.2...v1.9.3)

Upstream-repository: api
Upstream-commit: 9698d12a5f3e27980773fe3e5c0cc3e8e596a6d7

---
updated-dependencies:
- dependency-name: github.com/sirupsen/logrus
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps [sigs.k8s.io/controller-runtime](https://github.com/kubernetes-sigs/controller-runtime) from 0.18.2 to 0.18.3.
- [Release notes](https://github.com/kubernetes-sigs/controller-runtime/releases)
- [Changelog](https://github.com/kubernetes-sigs/controller-runtime/blob/main/RELEASE.md)
- [Commits](kubernetes-sigs/controller-runtime@v0.18.2...v0.18.3)

Upstream-repository: api
Upstream-commit: d6920a4c8df5b2a6f9f96792c50cdb2c3e43674d

---
updated-dependencies:
- dependency-name: sigs.k8s.io/controller-runtime
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps [sigs.k8s.io/controller-runtime](https://github.com/kubernetes-sigs/controller-runtime) from 0.18.3 to 0.18.4.
- [Release notes](https://github.com/kubernetes-sigs/controller-runtime/releases)
- [Changelog](https://github.com/kubernetes-sigs/controller-runtime/blob/main/RELEASE.md)
- [Commits](kubernetes-sigs/controller-runtime@v0.18.3...v0.18.4)

Upstream-repository: api
Upstream-commit: e684a5915a470e217294aede72cad2c5daa830e7

---
updated-dependencies:
- dependency-name: sigs.k8s.io/controller-runtime
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
…ig (openshift#342)

Signed-off-by: Joe Lanford <joe.lanford@gmail.com>
Upstream-repository: api
Upstream-commit: 5d2d3fbe061b7b4a942747877efa58958fa9889e
@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 Jun 14, 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 Jun 14, 2024
@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
2024-06-13 18:09:24 operator-framework/operator-lifecycle-manager@59606f2 Joe Lanford bump of/api to v0.26.0 (#3317)
2024-05-28 09:31:47 operator-framework/api@9698d12 dependabot[bot] Bump github.com/sirupsen/logrus from 1.9.2 to 1.9.3
2024-05-28 09:32:07 operator-framework/api@d6920a4 dependabot[bot] Bump sigs.k8s.io/controller-runtime from 0.18.2 to 0.18.3
2024-06-11 08:06:09 operator-framework/api@e684a59 dependabot[bot] Bump sigs.k8s.io/controller-runtime from 0.18.3 to 0.18.4
2024-06-13 14:13:18 operator-framework/api@5d2d3fb Joe Lanford remove default value of catsrc.spec.grpcPodConfig.securityContextConfig (#342)

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
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 14, 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

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 Jun 14, 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

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

@openshift-ci-robot
Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD c921a18 and 2 for PR HEAD 4219fb9 in total

@jianzhangbjz
Copy link
Copy Markdown
Contributor

Test pass, see: https://issues.redhat.com/browse/OCPBUGS-29729
/lgtm
/label qe-approved

@openshift-ci openshift-ci Bot added the qe-approved Signifies that QE has signed off on this PR label Jun 14, 2024
@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
2024-06-13 18:09:24 operator-framework/operator-lifecycle-manager@59606f2 Joe Lanford bump of/api to v0.26.0 (#3317)
2024-05-28 09:31:47 operator-framework/api@9698d12 dependabot[bot] Bump github.com/sirupsen/logrus from 1.9.2 to 1.9.3
2024-05-28 09:32:07 operator-framework/api@d6920a4 dependabot[bot] Bump sigs.k8s.io/controller-runtime from 0.18.2 to 0.18.3
2024-06-11 08:06:09 operator-framework/api@e684a59 dependabot[bot] Bump sigs.k8s.io/controller-runtime from 0.18.3 to 0.18.4
2024-06-13 14:13:18 operator-framework/api@5d2d3fb Joe Lanford remove default value of catsrc.spec.grpcPodConfig.securityContextConfig (#342)

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.

@perdasilva
Copy link
Copy Markdown
Contributor

/retest

4 similar comments
@perdasilva
Copy link
Copy Markdown
Contributor

/retest

@perdasilva
Copy link
Copy Markdown
Contributor

/retest

@perdasilva
Copy link
Copy Markdown
Contributor

/retest

@perdasilva
Copy link
Copy Markdown
Contributor

/retest

@jianzhangbjz
Copy link
Copy Markdown
Contributor

/test e2e-gcp-olm

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 17, 2024

@openshift-bot: all tests passed!

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-merge-bot openshift-merge-bot Bot merged commit dc02939 into openshift:master Jun 17, 2024
@openshift-bot
Copy link
Copy Markdown
Contributor Author

[ART PR BUILD NOTIFIER]

This PR has been included in build operator-lifecycle-manager-container-v4.17.0-202406171003.p0.gdc02939.assembly.stream.el9 for distgit operator-lifecycle-manager.
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

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. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants