Repository navigation
Bump API schema to bce6c855 - #19978
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 pins a new OpenAPI schema for generated API reference pages. The published schema file did not change, so page content should hold. The plan checks API page loads, API 404s, and the error rate. An issue escalates when API 404s rise or the error rate rises. Services: Mention PlanWhat changedThe docs build now fetches OpenAPI from git SHA bce6c855. Generated API reference pages come from that file. The published OpenAPI file did not change from the prior pin. sentry-docs must deploy before those pages go live. develop-docs also deploys because it shares src/ and skip-build rebuilds both apps. develop-docs does not render the generated API pages. RiskA missing or invalid schema fails the production build or drops API pages. Users then see 404s on API reference paths. A shared app rebuild can also raise errors on both sites. Intended effectNo new API page is expected. The published OpenAPI file is unchanged between the old pin and bce6c855. Confirm the pin by API page loads that hold. Absent looks like the API load share falling below the band while total page loads hold.
Regression watchA bad schema can drop API pages or break the shared app. Watch API 404s first. Also watch site errors and server 5xx.
Client traces use a 30% sample for users. Metrics and errors are not sampled that way. If API 404s rise, inspect Not observableThe SHA that the running build fetched is not in production telemetry. Field-level API page text is not measured. Build-time fetch of the schema is not in these signals. Most page errors use transaction |
No description provided.