Repository navigation
Bump API schema to 6bb07ed1 - #20169
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 not-found pages, and errors on API URLs. An issue escalates when not-found pages rise or API page loads fall. Services: PlanWhat changedThe site build now fetches OpenAPI from SHA 6bb07ed1. API reference pages regenerate from that schema. The schema JSON matches prior SHA 2da92393. Only the schema changelog and package version changed. sentry-docs must deploy before API pages update. develop-docs also ships this source. It does not render OpenAPI pages. Deploy config maps both Vercel projects. The catalog says src changes ship to both. RiskA bad schema fetch can fail the sentry-docs build. A shape change can crash API page render. Removed endpoints return 404. This bump has identical JSON, so content risk is low. A failed static generation still 404s the API section. Intended effectThis bump does not add new API page content. The OpenAPI JSON did not change. The running SHA is not a metric. There is no new-content signal. Do not treat a steady page-load count as proof the new SHA is live. Report intended effect unknown. Regression watchWatch the API section on sentry-docs. A schema break 404s pages or drops loads. Put each risk on these checks.
The two 24h load samples sit close. A real drop is a fall well below 809, not a few dozen events. Some API URL errors are search-beacon noise. A schema render break would add new TypeError volume on those URLs. If not-found rate rises, check which Not observablePageload traces for |
No description provided.