Repository navigation
Bump API schema to f73faaac - #19867
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 reference page loads, API-path 404s, and client errors on those pages. An issue escalates when API 404s rise or Monitor API pages stop loading. Services: Mention PlanWhat changedThe docs build now fetches OpenAPI schema f73faaac. Monitor API pages no longer document alert_rule request and response fields. sentry-docs must deploy before this change is live. The OpenAPI pin feeds user-docs API routes only. The same commit rebuilds develop-docs, but that site does not render these pages. The ship is sentry-docs because Production deploys named sentry-docs map to that catalog id, and only that site calls apiCategories. RiskA bad schema can omit API routes at build time. Readers then see 404s on former Monitor and other API pages. A client render break on those pages can raise errors while page loads fall. Intended effectThis change updates generated page content. Telemetry cannot show that alert_rule left the page. Use Crons and Monitor API page loads as a reachability proxy. Absent looks like those loads at zero while other API page loads continue.
Regression watchThis pin can drop generated
If API 404s rise, inspect Not observableWhether Monitor API pages still list alert_rule. No page-content probe is connected. Pageload traces are sampled at 30%, so Crons path latency is too sparse for a band. |
No description provided.