Repository navigation
Bump API schema to 81b0732b - #20046
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 not-found events, and client errors on API pages. An issue escalates when API page loads fall or not-found events rise. Services: Mention PlanWhat changedThe API reference build now fetches OpenAPI schema SHA 81b0732b. Requests to API reference pages still render the same spec. The OpenAPI document did not change from the prior SHA. sentry-docs must deploy before this change is live. API reference pages are generated only for that Vercel project. develop-docs ships the shared file but does not generate those pages. RiskA bad schema can omit API pages from the static build. Users then see not-found on former API URLs. A render break shows as client errors on those pages. The blast radius is the API reference tree. Other pages do not read this schema at runtime. A failed schema fetch fails the docs build and blocks deploy. Intended effectAPI page loads must continue after the rebuild. The spec content is unchanged, so the share should hold. absent looks like the API share falling while other page loads hold.
Regression watchThis diff can drop or rename API pages and break those URLs. Watch not-found events and client errors on the API path. Most current API not-found events are already on api/alerts.
Not observableProduction metrics do not show the GitHub schema fetch during build. Metrics do not show whether page text matches the OpenAPI document. Pageload traces do not match API paths reliably. |
No description provided.