Repository navigation
Bump API schema to 45d2f893 - #20223
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. |
|
Generated API reference pages rebuild from a new schema. The plan checks those page loads, API-path 404s, and client errors on those pages. An issue escalates when 404s rise or those errors rise. Services: Mention PlanWhat changedGenerated API reference pages now render from OpenAPI schema 45d2f893. The schema JSON changed three lines. sentry-docs must deploy before those pages are live. The same commit also deploys develop-docs. develop-docs does not generate API reference pages. RiskOld endpoint URLs return 404 if the schema renames or drops a slug. The API page component throws if the new schema shape does not match. A schema fetch failure fails the sentry-docs production build. Intended effectGenerated API pages keep loading after deploy. That volume is a proxy. The new schema text is not queryable. Absent looks like generated page loads falling below the band. Other docs pages would still load. Generated page loads should hold in the 370-494 band per 24h. That band is the 7d daily mean through the last 24h.
Regression watchThis change can 404 old API slugs. It can also throw in the API page component. Watch API-path 404 rate. Watch client errors on API URLs. Watch p95 of API pageload and navigation. Watch static API page loads as a sibling slice. If generated loads fall and static API loads hold, the schema is the likely cause. Last-24h client errors were browser noise. Titles were
Not observableThe exact OpenAPI field that changed. GitHub omitted the patch for the large schema file. Whether rendered page text matches schema 45d2f893. A 404 rate for the unknown changed endpoint alone. |
No description provided.