Repository navigation
Bump API schema to d12bf35d - #19843
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 events, and production errors. An issue escalates when API page loads fall or API not-found events rise. Error volume on the remounted sites is the sibling watch. Services: Mention PlanWhat changedThe generated API docs now list a 429 Too Many Requests response on one existing endpoint. Build fetches OpenAPI schema SHA d12bf35d26e7e3fe9eacf3a04a034ee1535d693c. sentry-docs and develop-docs must both deploy. Only the public docs site serves generated API pages. RiskA bad schema can drop API pages or break the response status buttons. Users then see not-found pages or a broken endpoint page. The shared source tree also remounts the developer docs site. Intended effectThe new 429 text is not a metric. Use API page loads as the same-path proxy that the schema still built those pages. Absent looks like API page loads near zero while other page loads stay in band.
Regression watchThis diff can drop or break API endpoint pages. The shared
If API not-found events rise, check whether generateStaticParams omitted an endpoint slug. If Not observableThe new 429 response text has no metric. Error events cannot be sliced to |
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
No description provided.