Repository navigation
Bump API schema to 786d404c - #20184
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Please update the IS YOUR CHANGE URGENT? section of the PR description:
This information helps the Docs team prioritize your review. |
|
The plan checks API page loads, API 404s, and client errors on API pages. An issue escalates when API page loads fall or those 404s and errors rise. Services: Mention PlanWhat changedAPI category and endpoint pages now build from schema SHA 786d404c. The compare did not list a change to the OpenAPI file. sentry-docs must deploy before those pages go live. develop-docs also ships the shared source on the same commit. develop-docs does not render API reference pages. The runtime Sentry project tag is RiskA bad schema can rename or drop endpoint slugs. Users then get 404s on old API page URLs. A fetch or parse failure fails the docs build. A render defect can throw client errors on API pages. The blast radius is the API reference section. Intended effectAPI pages stay reachable after the pin. The OpenAPI file itself did not change operations.
Regression watchWatch 404s and client errors on API URLs. A slug change would raise 404s first. A render break would raise client errors on those URLs.
Not observablePageload latency and LCP for API pages. The trace query timed out. Warning logs for missing MDX at runtime. The log query timed out. Prior 24h API page loads by |
No description provided.