Repository navigation
Bump API schema to 285d9cbc - #20119
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 API 404s or API errors rise. Services: Mention PlanWhat changedThe docs build now fetches the public API schema at SHA 285d9cbc. The OpenAPI JSON blob matches the previous SHA f56baf12. API documentation pages stay the same when the build succeeds. sentry-docs must deploy before this pin is live on API pages. develop-docs also deploys this shared src file. develop-docs does not render API pages. RiskA failed schema fetch can fail the public docs build. A broken schema can drop API routes or crash API pages. This pin uses the same JSON blob, so content risk is low. Users then see API 404s or client errors on API pages. Intended effectThe pin has no new production counter. API pages must keep loading after deploy. absent looks like other docs page loads hold while API page loads drop.
The 7d API page-load TPM was 0.48. The two 24h samples were 0.56 then 0.61. The rate may vary with weekday traffic. Regression watchThis pin could drop API routes or crash API page render. Watch API 404s, API-path errors, and all docs errors.
If the API 404 share rises, inspect Not observableProduction telemetry does not show the live schema SHA. Page body content is not compared to the OpenAPI JSON. The JSON blob did not change, so no new endpoint volume exists. develop-docs has no API page-load signal. The develop-docs error rate lacks a measured page-load denominator. |
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
No description provided.