Update link checker config and fix some broken links

[dveeden]

First-time contributors' checklist

• I've signed the Contributor License Agreement, which is required for the repository owners to accept my contribution.

What is changed, added or deleted? (Required)

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

• master (the latest development version)
• v9.0 (TiDB 9.0 versions)
• v8.5 (TiDB 8.5 versions)
• v8.1 (TiDB 8.1 versions)
• v7.5 (TiDB 7.5 versions)
• v7.1 (TiDB 7.1 versions)
• v6.5 (TiDB 6.5 versions)
• v6.1 (TiDB 6.1 versions)
• v5.4 (TiDB 5.4 versions)

What is the related PR or file link(s)?

• This PR is translated from:
• Other reference link(s):

Do your changes match any of the following descriptions?

• Delete files
• Change aliases
• Need modification after applied to another branch
• Might cause conflicts after applied to another branch

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

[dveeden]

This doesn't fix all issues

dvaneeden@dve-carbon:~/dev/pingcap/docs$ lychee --cache --max-cache-age 1d --root-dir . --exclude https://docs.pingcap.com/tidb/  --exclude https://docs.pingcap.com/tidb-data-migration/ --exclude vx.y --exclude tidb-operator-version  --exclude github-id --exclude-path './releases/' --exclude-path '^tidb-cloud/releases/' . | grep -E '\[404\]'
17476/17476 ━━━━━━━━━━━━━━━━━━━━ Finished extracting links                                                                                                                                                                                              [404] https://docs.pingcap.com/tidbcloud/secure-connections-to-starter-clusters/ | Error (cached)
[404] https://docs.pingcap.com/tidb-in-kubernetes/stable/restore-from-aws-s3-by-snapshot | Error (cached)
[404] https://docs.airbyte.com/operator-guides/transformation-and-normalization/transformations-with-dbt | Error (cached)
[404] https://docs.pingcap.com/developer/vector-search-full-text-search-python | Error (cached)
[404] https://docs.pingcap.com/developer/vector-search-full-text-search-sql | Error (cached)

[dveeden]

https://github.com/pingcap/docs/actions/workflows/link.yaml shows many failures.

I guess nobody looks at this and the issue generation isn't working?

[dveeden]

[dveeden]

Updating the create-issue-from-file action should fix this as since v5.0.1 it should truncate the input if it is too long.

[qiancai]

I found two workflow regressions that are worth fixing before merge:

1. The scheduled link.yaml job now fails in the lychee step before Create Issue From File can run, so broken links will no longer open the issue this workflow is designed to create.
2. The same workflow now excludes releases/ and tidb-cloud/releases/ entirely, which removes periodic broken-link coverage from a large set of public release-note pages.

I also spot-checked the updated external documentation URLs in the Markdown files, and the new targets themselves resolve correctly.

[qiancai]

Rest LGTM

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2026-03-20 09:44:24.190316958 +0000 UTC m=+522991.277974485: ✖️🔁 reset by qiancai.
• 2026-03-20 09:47:00.724173436 +0000 UTC m=+523147.811830973: ☑️ agreed by qiancai.
• 2026-03-20 10:54:34.536150394 +0000 UTC m=+527201.623807931: ☑️ agreed by hfxsd.

[hfxsd]

/approve

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hfxsd

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [hfxsd]

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