Repository navigation
docs: stop the API reference link check flagging the llms.txt indexes the build writes - #25770
Merged
Merged
Conversation
… the build writes The build writes a scoped llms.txt into each built API reference folder after docusaurus runs, so the link check, which reads static/, reported the aztec.js reference page's link to it as broken. The check now takes the list of those indexes from the code that writes them; missing folders, missing files and indexes the build does not write stay broken.
…option A source URL like /-e<api dir>/llms.txt resolved because grep took it as -e.
asterite
approved these changes
Nov 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
llms.txtindex, which production serves but the build writes only after the site is generated, so the link check, which runs earlier, never saw it.Not changed
logLevel: 0) also hides the plugin's real warnings, such as unreadable pages or cache failures. The exclusions are intended: the historical v5.2.0 pages, search and tag pages, and the API reference folders, which get their own indexes.