openshift / file-integrity-operator

Operator providing OpenShift cluster node file integrity checking
Apache License 2.0
31 stars 27 forks source link

Bump the kubernetes group with 3 updates #460

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps the kubernetes group with 3 updates: k8s.io/api, k8s.io/apiextensions-apiserver and sigs.k8s.io/controller-runtime.

Updates k8s.io/api from 0.28.2 to 0.28.3

Commits


Updates k8s.io/apiextensions-apiserver from 0.28.2 to 0.28.3

Commits


Updates sigs.k8s.io/controller-runtime from 0.16.2 to 0.16.3

Release notes

Sourced from sigs.k8s.io/controller-runtime's releases.

v0.16.3

What's Changed

Full Changelog: https://github.com/kubernetes-sigs/controller-runtime/compare/v0.16.2...v0.16.3

Commits
  • 5f8d96b Merge pull request #2552 from varshaprasad96/bump/k8s-1.28.3
  • 5572514 [fix]: Bump k8s to 1.28.3
  • 7c1e2d9 Merge pull request #2541 from joelanford/0.16-golang-x-net
  • 5201923 :bug: bump golang.org/x/net to v0.17.0
  • 8b5b1a2 Merge pull request #2539 from k8s-infra-cherrypick-robot/cherry-pick-2528-to-...
  • b9c691d sparkles: Cache: Allow defining options that apply to all namespaces that the...
  • 8361246 Merge pull request #2523 from troy0820/troy0820/cherry-pick-to-release-0.16
  • f7b7450 🐛 Handle unstructured status update with fake client (#2495)
  • 2d6b699 [release-0.16] 🐛 Correctly identify if patch call was made on status (#2515)
  • da31104 Merge pull request #2516 from k8s-infra-cherrypick-robot/cherry-pick-2507-to-...
  • Additional commits viewable in compare view


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
openshift-ci[bot] commented 1 year ago

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
openshift-ci[bot] commented 1 year ago

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot] Once this PR has been reviewed and has the lgtm label, please assign xiaojiey for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files: - **[OWNERS](https://github.com/openshift/file-integrity-operator/blob/master/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
openshift-ci[bot] commented 1 year ago

@dependabot[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/unit eafc3a36e6740c305e8b6f9efc7f833bb5fc9543 link true /test unit
ci/prow/e2e-bundle-aws-upgrade eafc3a36e6740c305e8b6f9efc7f833bb5fc9543 link true /test e2e-bundle-aws-upgrade
ci/prow/e2e-aws eafc3a36e6740c305e8b6f9efc7f833bb5fc9543 link true /test e2e-aws
ci/prow/e2e-bundle-aws eafc3a36e6740c305e8b6f9efc7f833bb5fc9543 link true /test e2e-bundle-aws
ci/prow/verify eafc3a36e6740c305e8b6f9efc7f833bb5fc9543 link true /test verify

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
dependabot[bot] commented 1 year ago

Looks like these dependencies are updatable in another way, so this is no longer needed.