Skip to content

NO-ISSUE: Synchronize From Upstream Repositories#778

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

NO-ISSUE: Synchronize From Upstream Repositories#778
openshift-merge-bot[bot] merged 4 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-11 06:04:16 operator-framework/operator-lifecycle-manager@09935f0 dependabot[bot] build(deps): bump golang.org/x/net from 0.25.0 to 0.26.0 (#3312)
2024-06-11 06:04:36 operator-framework/operator-lifecycle-manager@7406613 dependabot[bot] build(deps): bump sigs.k8s.io/controller-runtime from 0.18.3 to 0.18.4 (#3313)
2024-06-11 06:27:38 operator-framework/operator-lifecycle-manager@0d07970 dependabot[bot] build(deps): bump goreleaser/goreleaser-action from 5 to 6 (#3314)
2024-06-11 06:54:33 operator-framework/operator-lifecycle-manager@4fc8920 dependabot[bot] build(deps): bump github.com/go-logr/logr from 1.4.1 to 1.4.2 (#3311)

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

dependabot Bot added 4 commits June 12, 2024 00:02
Bumps [golang.org/x/net](https://github.com/golang/net) from 0.25.0 to 0.26.0.
- [Commits](golang/net@v0.25.0...v0.26.0)

Upstream-repository: operator-lifecycle-manager
Upstream-commit: 09935f00859e2a15007c4f6a9fefbfbfb0a49e71

---
updated-dependencies:
- dependency-name: golang.org/x/net
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…4 (#3313)

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: operator-lifecycle-manager
Upstream-commit: 74066131d293ee7e25989ca816975a09dc1f6d3c

---
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>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [goreleaser/goreleaser-action](https://github.com/goreleaser/goreleaser-action) from 5 to 6.
- [Release notes](https://github.com/goreleaser/goreleaser-action/releases)
- [Commits](goreleaser/goreleaser-action@v5...v6)

Upstream-repository: operator-lifecycle-manager
Upstream-commit: 0d079704e1fef98edb32c6dcb4dbf35c9f882328

---
updated-dependencies:
- dependency-name: goreleaser/goreleaser-action
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [github.com/go-logr/logr](https://github.com/go-logr/logr) from 1.4.1 to 1.4.2.
- [Release notes](https://github.com/go-logr/logr/releases)
- [Changelog](https://github.com/go-logr/logr/blob/master/CHANGELOG.md)
- [Commits](go-logr/logr@v1.4.1...v1.4.2)

Upstream-repository: operator-lifecycle-manager
Upstream-commit: 4fc8920527c1fe295611636a0a530b69ed40c90d

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

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@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 12, 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 12, 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-11 06:04:16 operator-framework/operator-lifecycle-manager@09935f0 dependabot[bot] build(deps): bump golang.org/x/net from 0.25.0 to 0.26.0 (#3312)
2024-06-11 06:04:36 operator-framework/operator-lifecycle-manager@7406613 dependabot[bot] build(deps): bump sigs.k8s.io/controller-runtime from 0.18.3 to 0.18.4 (#3313)
2024-06-11 06:27:38 operator-framework/operator-lifecycle-manager@0d07970 dependabot[bot] build(deps): bump goreleaser/goreleaser-action from 5 to 6 (#3314)
2024-06-11 06:54:33 operator-framework/operator-lifecycle-manager@4fc8920 dependabot[bot] build(deps): bump github.com/go-logr/logr from 1.4.1 to 1.4.2 (#3311)

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 12, 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 12, 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 e45e646 and 2 for PR HEAD 8210c1a in total

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 12, 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 c921a18 into openshift:master Jun 12, 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-202406121116.p0.gc921a18.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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants