Ayaan Gazali b6604af9a0 ci(links): stop the weekly link report flagging the Vite entry HTML (#2324) ...

* ci(links): stop the weekly link report flagging the Vite entry HTML

The Link Checker workflow opens an issue whenever lychee exits non-zero.
One of the two errors in this week's report (#2317) is not a broken link:

  [ERROR] error: (at 5:49) | Cannot resolve root-relative link
  '/favicon-black.svg?v=4': To resolve root-relative links in local
  files, provide a root dir

packages/inspector/index.html is a Vite entry document. Its two absolute
paths, /favicon-black.svg?v=4 and /src/client/main.tsx, are dev-server
paths that Vite resolves from public/ and src/. Both files exist:

  packages/inspector/public/favicon-black.svg
  packages/inspector/src/client/main.tsx

lychee has no web root to resolve them against, and a repo-wide
--root-dir cannot supply one: pointed at the repo root it looks for
<repo>/favicon-black.svg and fails the same way.

Add the file to the exclude_path list that already skips generated
changelogs, with the reason inline. Offline run over every tracked
markdown and html file, before and after:

  before  612 total, 1 error
  after   610 total, 0 errors

The two links that stop being counted are the two Vite paths.

* ci(links): fix the changelog exclusion that names a directory that does not exist

exclude_path skips libraries/typescript/packages/mcp-use/CHANGELOG.md.
There is no such tracked directory: `mcp-use` is the npm package name,
and its source lives in packages/server.

  $ git ls-files libraries/typescript/packages/mcp-use | wc -l
  0

So that entry matches nothing and packages/server/CHANGELOG.md is still
scanned, which is not what the comment above the list intends. Point it at
the real path.

The effect today is small: that changelog currently holds one URL. The
entry was simply never doing its job.

2026-08-25 09:56:29 -07:00

2.1 KiB

Raw Permalink Blame History

View Raw