Repository navigation
Bump API schema to a1e7464c - #20105
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 API reference pages. The plan checks API page loads, API 404s, and errors on those pages. An issue escalates when API page loads drop or those 404s rise. Services: Mention PlanWhat changedThe production build fetches OpenAPI from GitHub at schema SHA a1e7464c55cb6eabf4565482e22c9c8002b8ee3b. API category and endpoint pages under /api/ render from that schema. The schema JSON matches the prior pin. The upstream diff only changed the changelog and package version. sentry-docs must deploy before the new pin is live. RiskA bad schema can omit or rename API pages during static generation. Users who open those old URLs then get a 404. A schema parse failure fails the production build. Then the pin does not ship. The matching JSON makes a slug change unlikely this time. Intended effectThe pin does not add a new API page. The schema JSON did not change. Confirmed means API pages still load after deploy. Absent means page_type api loads fall toward zero while other page loads hold.
Regression watchThis pin can 404 old API URLs if slugs change. It can also throw on API pages if render breaks. Do not use
Not observableThe pinned SHA is not in production telemetry. Page body text for API endpoints is not in metrics. Build-time GitHub fetch is not in Sentry after a successful deploy. |
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
No description provided.