chore: Bump umbrelladocs/action-linkspector from 1.0.0 to 1.4.0

[dependabot]

Bumps umbrelladocs/action-linkspector from 1.0.0 to 1.4.0.

Release notes

Sourced from umbrelladocs/action-linkspector's releases.

Release v1.4.0

v1.4.0: PR #48 - chore(deps): update reviewdog/reviewdog to 0.21.0

Release v1.3.7

v1.3.7: PR #47 - Update linkspector version to 0.4.7

Release v1.3.6

v1.3.6: PR #46 - Update linkspector version to 0.4.6

Release v1.3.5

v1.3.5: PR #45 - Update linkspector version to 0.4.5

Release v1.3.4

v1.3.4: PR #42 - Update linkspector version to 0.4.4

Release v1.3.3

v1.3.3: PR #41 - Update linkspector version to 0.4.3

Release v1.3.2

v1.3.2: PR #40 - Update linkspector version to 0.4.2

Release v1.3.1

v1.3.1: PR #38 - Add support for showing stats

Release v1.3.0

v1.3.0: PR #37 - Update linkspector version to 0.4.1

What's Changed

• Update linkspector version to 0.4.1 by @​github-actions in UmbrellaDocs/action-linkspector#37

Full Changelog: UmbrellaDocs/action-linkspector@v1.2...v1.3.0

Release v1.2.5

What's Changed

• fix: disable AppArmor user namespace restrictions on the runner by @​Realiserad in UmbrellaDocs/action-linkspector#34
• chore(deps): update reviewdog/reviewdog to 0.20.3 by @​github-actions in UmbrellaDocs/action-linkspector#31
• Add fail_level argument and deprecate fail_on_error by @​bitcoin-tools in UmbrellaDocs/action-linkspector#23

New Contributors

• @​Realiserad made their first contribution in UmbrellaDocs/action-linkspector#34
• @​bitcoin-tools made their first contribution in UmbrellaDocs/action-linkspector#23

Full Changelog: UmbrellaDocs/action-linkspector@v1.2.4...UmbrellaDocs:release-1.2.5

Release v1.2.4

v1.2.4: PR #27 - User namespace cloning on 24.04

Release v1.2.3

v1.2.3: PR #26 - Updated README to include a note about using runner as ubuntu 22.04

... (truncated)

Commits

• 652f85b Merge pull request #48 from UmbrellaDocs/depup/reviewdog/reviewdog
• 9db4e7e chore(deps): update reviewdog/reviewdog to 0.21.0
• 874d01c Merge pull request #47 from UmbrellaDocs/update-linkspector-version
• bfc5bc5 Update linkspector version to 0.4.7
• 3a951c1 Merge pull request #46 from UmbrellaDocs/update-linkspector-version
• 8f8a099 Update linkspector version to 0.4.6
• e2ccef5 Merge pull request #45 from UmbrellaDocs/update-linkspector-version
• 6cc23b2 Update linkspector version to 0.4.5
• a0567ce Merge pull request #42 from UmbrellaDocs/update-linkspector-version
• f5418fd Update linkspector version to 0.4.4
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[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 aramase for approval. For more information see the 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]

This issue is currently awaiting triage.

If secrets-store-sync-controller contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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]

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

I'm waiting for a github.com 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 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
pull-secrets-store-sync-controller-e2e-provider-k8s-1-32-2	7a1499e	link	true	/test pull-secrets-store-sync-controller-e2e-provider-k8s-1-32-2
pull-secrets-store-sync-controller-e2e-provider-k8s-1-31-6	7a1499e	link	true	/test pull-secrets-store-sync-controller-e2e-provider-k8s-1-31-6
pull-secrets-store-sync-controller-e2e-provider-k8s-1-29-14	7a1499e	link	true	/test pull-secrets-store-sync-controller-e2e-provider-k8s-1-29-14
pull-secrets-store-sync-controller-e2e-provider-k8s-1-30-10	7a1499e	link	true	/test pull-secrets-store-sync-controller-e2e-provider-k8s-1-30-10

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.

[k8s-triage-robot]

Unknown CLA label state. Rechecking for CLA labels.

Send feedback to sig-contributor-experience at kubernetes/community.

/check-cla
/easycla