Repository navigation
Bump API schema to 35fcbf58 - #20149
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 production errors. An issue escalates when API 404s rise or production errors rise. Services: Mention PlanWhat changedAPI reference pages rebuild from schema SHA 35fcbf58. The OpenAPI document matches the previous pin. Endpoint pages stay the same. sentry-docs must deploy before the new pin is live. develop-docs also deploys this commit from the shared source tree. The OpenAPI fetch runs only during the sentry-docs build. RiskA missing or invalid schema file fails the sentry-docs build. API pages then 404. A slug change would 404 old API URLs. This pin does not change schema JSON, so slug churn is unlikely. The shared page module could break the develop-docs build if init fetched the schema. Current code does not fetch it there. Intended effectAPI pages keep loading after the rebuild. The API load share should hold. Absent looks like the API load share near zero while API 404s rise. This pin adds no new endpoint pages.
Regression watchA bad pin can drop API pages or raise errors on the docs site.
Not observableProduction does not emit the schema SHA. Per-endpoint page text has no telemetry. Pageload p95 for API pages had no usable trace query. develop-docs page-load volume for the prior 24h was not measured. Last 24h had 15 docs errors on /api/ URLs. The prior 24h for that slice was not measured. |
No description provided.