Repository navigation
Bump API schema to ca7b22fe - #20091
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 change rebuilds API reference pages from a new schema pin. The schema document itself did not change. The plan checks API page loads, API 404s, and the API category mix. An issue escalates when API page loads drop or API 404s rise. Services: Mention PlanWhat changedAPI reference pages now build from OpenAPI schema commit ca7b22fe. That document matches the prior pin, so published endpoint pages should stay the same. sentry-docs must deploy before those pages use the new pin. develop-docs also ships this commit from the shared src tree. It does not generate OpenAPI pages. Catalog and deploy config name both sites for this repo. OpenAPI generation runs only for sentry-docs. RiskA bad schema pin can drop endpoint pages or change their slugs. Readers then see 404s on former API URLs. This pin matches the prior schema, so that blast radius is small. A fetch failure fails the build and does not reach production. Intended effectThe schema JSON did not change, so no new endpoint page should appear. Success is that API reference pages keep loading at the measured rate. Absent looks like API page loads falling toward zero while other page types keep loading. Platforms had 7210 loads in the same 24h. These signals live on the product docs site. They become decisive after sentry-docs deploys. A develop-docs-only deploy does not change them.
Regression watchThis pin can still 404 former API URLs if a page fails to generate. Watch 404s on API paths. Also watch the API category mix. A missing category would show as a load drop on that slice.
If API 404s rise, inspect the new Not observableSchema field text on each page has no content hash metric. Client errors scoped to |
No description provided.