Repository navigation
Bump API schema to 42958f35 - #20277
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. |
|
API documentation pages should keep loading after this schema pin. The plan checks API page loads, API 404s, and server 5xx responses. An issue escalates when API page loads fall or API 404s rise. Services: Mention PlanWhat changedBuild now fetches the OpenAPI schema at git commit 42958f353ec9cd48951c98610ec163a870e6b084. The JSON blob matches the prior pin 9f048abeb531ed4bfa183fca51d9357f5854e035. API endpoint pages should keep the same paths and the same content. sentry-docs must deploy before those pages are live. develop-docs also rebuilds shared src. OpenAPI pages render only on sentry-docs. RiskA bad schema can drop endpoint pages or break page render. Users then see 404s or client errors on API docs. The same src rebuild ships to develop-docs. That site does not render OpenAPI pages. If GitHub fetch fails, the production build fails and this change does not go live. Intended effectAPI docs pages keep loading. The schema blob did not change, so volume should hold.
Regression watchThis pin rebuilds every API docs URL. A dropped path shows as 404s. A broken render shows as client errors or server 5xx.
If API 404s rise, inspect Not observabledevelop-docs has no OpenAPI-generated pages. Intended effect cannot be confirmed on that ship. Server 5xx is site-wide, not sliced to |
No description provided.