chore(deps): bump tcort/github-action-markdown-link-check from 1.1.2 to 1.1.3 in the minor-and-patch group across 1 directory

[dependabot]

Bumps the minor-and-patch group with 1 update in the / directory: tcort/github-action-markdown-link-check.

Updates tcort/github-action-markdown-link-check from 1.1.2 to 1.1.3

Changelog

Sourced from tcort/github-action-markdown-link-check's changelog.

Changes

Version 1.1.3

• update entrypoint.sh to use markdown-link-check 3.15.0
• update Dockerfile to use node:24.18.0-alpine3.24
• Add CHANGELOG.md and MAINT.md

Commits

• e047c5b chore(entrypoint): new markdown-link-check
• f324e89 chore(Dockerfile): update to node:24.18.0-alpine3.24
• See full diff in compare view

[phil-davis]

The action tcort/github-action-markdown-link-check@e047c5b37f24ab722bbef1a27b6fab7f96bc4068 is not allowed in owncloud-docker/ubuntu because all actions must be from a repository owned by owncloud-docker, created by GitHub, verified in the GitHub Marketplace, or match one of the patterns:

https://github.com/owncloud-docker/ubuntu/actions/runs/30769294362

@DeepDiver1975 not urgent, but allowing this action update needs to be sorted out.

[DeepDiver1975]

Holding: CI is failing (not a rebase conflict). The Docker CI run on this branch ends in startup_failure (head 07d1221), so the required build (22.04) / build and build (24.04) / build checks never post — the merge stays BLOCKED even though lint is green and the PR is approved. Root cause: main.yml passes secrets.DOCKERHUB_TOKEN into the reusable docker-build.yml, but DOCKERHUB_TOKEN only exists as an org Actions secret; Dependabot-triggered runs cannot read Actions secrets and no Dependabot secret is configured (repo or org). A rebase won't fix this — needs DOCKERHUB_TOKEN added as a Dependabot secret (or the secret pass-through guarded for bot PRs).