Repository navigation
Bump API schema to f8bf85ea - #20042
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 404s, and errors on those pages. An issue escalates when API page loads fall or API 404s rise. Services: Mention PlanWhat changedAPI reference pages now build from OpenAPI schema pin f8bf85ea. The schema file matches the prior pin. The two pins differ only in changelog and package files. sentry-docs must deploy before this pin is live. develop-docs also rebuilds from this commit. That site does not fetch the OpenAPI schema, so it is not in RiskA bad pin fails the production build. A broken schema omits API pages or serves 404. Malformed endpoint text can throw in the API page renderer. Users then lose API reference pages. Intended effectThe pin does not add or change endpoint pages. Success is that API pages still load at the baseline share. Absent means that share falls below the band while other page types hold. Sentry does not expose the live schema SHA.
Regression watchA bad schema first shows as 404s or errors on API pages. If 404s rise, group
Not observableSentry does not record the schema SHA from the built site. Endpoint body text is not in telemetry. Pageload p95 on API pages is too noisy for a rule. |
No description provided.