chore: bump gaurav-nelson/github-action-markdown-link-check from 1.0.15 to 1.0.16

[dependabot]

Bumps gaurav-nelson/github-action-markdown-link-check from 1.0.15 to 1.0.16.

Release notes

Sourced from gaurav-nelson/github-action-markdown-link-check's releases.

1.0.16

What's Changed

• Update to 3.11.1 by @​PatrickHeneise in gaurav-nelson/github-action-markdown-link-check#179
• Respect folder patch when modified only is used by @​gaurav-nelson in gaurav-nelson/github-action-markdown-link-check#184
• [Snyk] Security upgrade node from lts-alpine to 20-alpine3.18 by @​gaurav-nelson in gaurav-nelson/github-action-markdown-link-check#189
• Added results as output parameters by @​gaurav-nelson in gaurav-nelson/github-action-markdown-link-check#149

New Contributors

• @​PatrickHeneise made their first contribution in gaurav-nelson/github-action-markdown-link-check#179

Full Changelog: gaurav-nelson/github-action-markdown-link-check@1.0.15...1.0.16

Commits

• 1b916f2 Bump markdown-link-check and node image
• 7d83e59 Update README.md
• 25b2c43 Merge pull request #149 from gaurav-nelson/step-output
• c541b5c Added results as output parameters
• 0f074c8 maintenance-only README.md
• a996638 Update README.md
• 46e4421 Merge pull request #189 from gaurav-nelson/snyk-fix-28c2a22fe65aa69306d3041d1...
• 1c7e3fe fix: Dockerfile to reduce vulnerabilities
• 322b231 Merge pull request #184 from gaurav-nelson/fix-158
• 5525016 Respect folder patch when modified only is used
• 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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[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-secrets-store-csi-driver-image-scan	25d7756	link	false	/test pull-secrets-store-csi-driver-image-scan

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.

[aramase]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aramase, dependabot[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:

• OWNERS [aramase]

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