build(deps): bump the kubernetes group across 1 directory with 6 updates

[dependabot]

Bumps the kubernetes group with 4 updates in the / directory: k8s.io/api, k8s.io/cli-runtime, sigs.k8s.io/controller-runtime and sigs.k8s.io/release-utils.

Updates k8s.io/api from 0.31.2 to 0.31.3

Commits

• b7783ab Update dependencies to v0.31.3 tag
• See full diff in compare view

Updates k8s.io/apimachinery from 0.31.2 to 0.31.3

Commits

• See full diff in compare view

Updates k8s.io/cli-runtime from 0.31.2 to 0.31.3

Commits

• 597e981 Update dependencies to v0.31.3 tag
• See full diff in compare view

Updates k8s.io/client-go from 0.31.2 to 0.31.3

Commits

• ef98edc Update dependencies to v0.31.3 tag
• See full diff in compare view

Updates sigs.k8s.io/controller-runtime from 0.19.1 to 0.19.2

Release notes

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

v0.19.2

What's Changed

• ✨ Add EnableWatchBookmarks option to cache informers by @​k8s-infra-cherrypick-robot in kubernetes-sigs/controller-runtime#3018

Full Changelog: kubernetes-sigs/controller-runtime@v0.19.1...v0.19.2

Commits

• bfd1cf9 [release-0.19] ✨ Add EnableWatchBookmarks option to cache informers (#3018)
• See full diff in compare view

Updates sigs.k8s.io/release-utils from 0.8.4 to 0.8.5

Release notes

Sourced from sigs.k8s.io/release-utils's releases.

v0.8.5

No release notes provided.

Commits

• 06acb35 Merge pull request #113 from saschagrunert/go-1.22
• 5e795d2 Switch to go 1.23
• See full diff 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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> 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 <dependency name> 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 <dependency name> 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 <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[k8s-ci-robot]

[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 ccojocar 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

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

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

I'm waiting for a kubernetes-sigs 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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-ci-robot]

@dependabot[bot]: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-security-profiles-operator-verify	264b6cb	link	true	/test pull-security-profiles-operator-verify

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.