🌱 Bump k8s.io/release from 0.16.6-0.20240222112346-71feb57b59a4 to 0.16.9 in /hack/tools in the kubernetes group

[dependabot]

Bumps the kubernetes group in /hack/tools with 1 update: k8s.io/release.

Updates k8s.io/release from 0.16.6-0.20240222112346-71feb57b59a4 to 0.16.9

Release notes

Sourced from k8s.io/release's releases.

v0.16.9

Changes by Kind

Please note that you can also download the artifacts for this release from our Google Cloud Bucket: https://console.cloud.google.com/storage/browser/k8s-artifacts-sig-release/kubernetes/release/v0.16.9

Feature

• Schedule-builder: Added markdown help on top of each file when updating them. (#3583, @​saschagrunert) [SIG Release]

Bug or Regression

• Fixed monthly patch output for schedule-builder. (#3578, @​saschagrunert) [SIG Release]

Dependencies

Added

Nothing has changed.

Changed

Nothing has changed.

Removed

Nothing has changed.

v0.16.8

Changes by Kind

Please note that you can also download the artifacts for this release from our Google Cloud Bucket: https://console.cloud.google.com/storage/browser/k8s-artifacts-sig-release/kubernetes/release/v0.16.8

Feature

• Build Go 1.22.2 and 1.21.9 (#3549, @​cpanato) [SIG Release]
• Build k8s-ci-builder and k8s-cloud-bulider with Go 1.21.9 (#3561, @​cpanato) [SIG Release]
• Build k8s-ci-builder and k8s-cloud-bulider with Go 1.22.2 (#3555, @​cpanato) [SIG Release]
• Bump distroless iptables to use go1.22.2 and go1.21.9 (#3554, @​cpanato) [SIG Release]
• Mark GitHub release as latest if no newer releases were found (#3559, @​embik) [SIG Release]
• Schedule-builder: do not add release name for upcoming releases because it can be inferred by the target date. (#3570, @​saschagrunert) [SIG Release]

Bug or Regression

• Fixed crash in schedule-builder if next field is not set in schedule.yaml. (#3551, @​saschagrunert) [SIG Release]

Dependencies

Added

Nothing has changed.

Changed

• github.com/goark/go-cvss: v1.6.7 → v1.6.6
• golang.org/x/crypto: v0.21.0 → v0.22.0

... (truncated)

Commits

• 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]

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/test-infra repository.

[sbueringer]

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: aec5f2c7550c76372422cf16a9ce0a2ad9153725

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbueringer

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:

• OWNERS [sbueringer]

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