[docs-infra] Run link checker during docs build instead of as separate CI step#48634
Merged
Conversation
Deploy previewBundle size
Check out the code infra dashboard for more information about this PR. |
Janpot
added
the
scope: code-infra
1 task
brijeshb42
approved these changes
Jun 9, 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
2 participants
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.
Reverts the CI-orchestration part of #48088, which moved the broken-links checker out of the docs build into a standalone GitHub Actions step (
pnpm docs:link-check).The checker doesn't just validate links — it also writes
export/material-ui/link-structure.json, which gets deployed to https://mui.com/material-ui/link-structure.json and is consumed by other products' link checkers (e.g. mui-x). Running it in a separate CI step meant the file was no longer produced inside the Netlify build'sexport/output, so that URL started returning 404. Downstream checkers fetch it and throw on the non-OK response, breaking their docs builds — see mui/mui-x#22707.This restores the prior behavior:
pnpm link-checkruns at the end ofdocs build(during the Netlify build), solink-structure.jsonis generated and deployed again. The separate CI step is removed.The HTML-validation work from #48088 (the
htmlValidateconfig anderrorCountexit handling inreportBrokenLinks.mts) is intentionally kept — only the run-location change is reverted.