Repository navigation
chore: Update docs changelog - #20229
getsantry[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
|
Please update the IS YOUR CHANGE URGENT? section of the PR description:
This information helps the Docs team prioritize your review. |
|
The plan uses changelog page loads, changelog 404s, and client errors on changelog URLs. An issue escalates when those 404s appear or those errors rise. The new changelog entries have no metric. Services: Mention PlanWhat changedThe RiskA bad MDX include can render an empty changelog body. The Include component returns null for ENOENT and MDX_RUNTIME_ERROR. Users then see a 200 page with no entries. A compile failure during the production build can block the whole site deploy. The include grew by about 135 lines. Load time on Intended effectThis change only rewrites documentation content. No metric shows the new 23 October entries. Regression watchWrong MDX on this include can 404 Do not filter
Not observableThe rendered changelog text is not in telemetry. An empty body from a swallowed |
Automated update of the docs changelog from recent merged PRs.