Repository navigation
Bump API schema to 4bc5d301 - #19845
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 rebuilds generated API reference pages from a new schema pin. The pinned OpenAPI document is unchanged, so page content should hold. The plan checks API page loads, API not-found counts, and client errors. An issue escalates when API page loads drop or those errors rise. Services: Mention PlanWhat changedBuild output for generated API reference pages now pins schema 4bc5d301. Requests to those pages should keep serving the same catalog. The OpenAPI file at this pin matches pin 3099d249. sentry-docs must deploy before the pin is live. develop-docs also ships this shared src/ file. develop-docs does not render the generated API catalog. RiskA bad pin can omit endpoints or rename slugs. Readers then get not-found on former API URLs. A schema shape change can crash API page render. That failure reaches every generated API category and endpoint page. A broken shared page module can also fail the develop-docs boot. Intended effectThe generated API catalog stays reachable after deploy. Absent looks like API page loads near zero while other page types still load.
Regression watchThis pin regenerates every API reference page at build time. Slug drift shows as not-found on API paths. Render faults show as client errors.
If API not-found counts rise, inspect generated slugs under Not observablePageload traces with an |
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
No description provided.