Skip to content

NO-ISSUE: Synchronize From Upstream Repositories #676

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 3 commits into from
Jan 29, 2024
Merged

NO-ISSUE: Synchronize From Upstream Repositories #676

merged 3 commits into from
Jan 29, 2024

Conversation

openshift-bot
Copy link
Contributor

@openshift-bot openshift-bot commented Jan 27, 2024 •
edited
Loading

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

Date Commit Author Message
2024-01-27 17:16:41 operator-framework/api@0eaaa1f Jacob Floyd Add field Subscription.Spec.Config.Annotations (#312)
2024-01-26 13:20:15 operator-framework/operator-registry@010e308 dependabot[bot] build(deps): bump github.com/onsi/gomega from 1.30.0 to 1.31.1 (#1215)
2024-01-23 15:23:09 operator-framework/operator-lifecycle-manager@1bb6009 dependabot[bot] build(deps): bump github.com/docker/docker (#3080)

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

@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 27, 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 27, 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-26 13:20:15 operator-framework/operator-registry@010e308 dependabot[bot] build(deps): bump github.com/onsi/gomega from 1.30.0 to 1.31.1 (#1215)
2024-01-23 15:23:09 operator-framework/operator-lifecycle-manager@1bb6009 dependabot[bot] build(deps): bump github.com/docker/docker (#3080)

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 27, 2024 00:04
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jan 27, 2024

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

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-26 13:20:15 operator-framework/operator-registry@010e308 dependabot[bot] build(deps): bump github.com/onsi/gomega from 1.30.0 to 1.31.1 (#1215)
2024-01-23 15:23:09 operator-framework/operator-lifecycle-manager@1bb6009 dependabot[bot] build(deps): bump github.com/docker/docker (#3080)

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 27, 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 27, 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 f814ea9 and 2 for PR HEAD b4bfc77 in total

cognifloyd and others added 3 commits January 28, 2024 00:02
@cognifloyd @joelanford
Add field Subscription.Spec.Config.Annotations (openshift#312)
7d121c7 
* Add field Subscription.Spec.Config.DeploymentAnnotations

* Use deploymentAnnotations over deployment_annotations

Co-authored-by: Joe Lanford <[email protected]>

* Clarify DeploymentAnnotations doc string and regen files

* Rename SubscriptionConfig.DeploymentAnnotations to SubscriptionConfig.Annotations

---------

Co-authored-by: Joe Lanford <[email protected]>
Upstream-repository: api
Upstream-commit: 0eaaa1f89530e27a87afba8bc3de66fe16bc038d
@dependabot
build(deps): bump github.com/onsi/gomega from 1.30.0 to 1.31.1 (#1215)
52d4f66 
Bumps [github.com/onsi/gomega](https://github.com/onsi/gomega) from 1.30.0 to 1.31.1.
- [Release notes](https://github.com/onsi/gomega/releases)
- [Changelog](https://github.com/onsi/gomega/blob/master/CHANGELOG.md)
- [Commits](onsi/gomega@v1.30.0...v1.31.1)

Upstream-repository: operator-registry
Upstream-commit: 010e308cbfae1b38287e7993ce8ec28e5064aa1e

---
updated-dependencies:
- dependency-name: github.com/onsi/gomega
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@dependabot
build(deps): bump github.com/docker/docker (#3080)
641f0f4 
Bumps [github.com/docker/docker](https://github.com/docker/docker) from 23.0.3+incompatible to 24.0.7+incompatible.
- [Release notes](https://github.com/docker/docker/releases)
- [Commits](moby/moby@v23.0.3...v24.0.7)

Upstream-repository: operator-lifecycle-manager
Upstream-commit: 1bb6009089171393c94c944257ec7b4d06834551

---
updated-dependencies:
- dependency-name: github.com/docker/docker
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jan 28, 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-27 17:16:41 operator-framework/api@0eaaa1f Jacob Floyd Add field Subscription.Spec.Config.Annotations (#312)
2024-01-26 13:20:15 operator-framework/operator-registry@010e308 dependabot[bot] build(deps): bump github.com/onsi/gomega from 1.30.0 to 1.31.1 (#1215)
2024-01-23 15:23:09 operator-framework/operator-lifecycle-manager@1bb6009 dependabot[bot] build(deps): bump github.com/docker/docker (#3080)

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

openshift-ci bot commented Jan 28, 2024

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 Jan 29, 2024
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD f814ea9 and 2 for PR HEAD 641f0f4 in total

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jan 29, 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 5790477 into openshift:master Jan 29, 2024
@openshift-bot
Copy link
Contributor Author

[ART PR BUILD NOTIFIER]

This PR has been included in build operator-lifecycle-manager-container-v4.16.0-202401290212.p0.g5790477.assembly.stream 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
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.
3 participants
@openshift-bot @openshift-ci-robot @cognifloyd