Repository navigation
Bump API schema to fe8bd6fa - #20268
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 page-load failures on those pages. An issue escalates when API pages stop loading or those 404s rise. It also checks page-load time on API reference pages. Services: PlanWhat changedAPI reference pages now build from OpenAPI schema SHA fe8bd6fa8b6c90500c7c05645712ed8ac8147764. That schema commit did not change openapi-derefed.json. Rendered API pages should stay the same. The sentry-docs ship must deploy before this pin is live. The develop-docs ship compiles this file but does not fetch the schema. That is why develop-docs is not in RiskA missing or invalid schema file fails the production build. A dropped API path then returns 404. A schema field that ApiPage cannot render throws on that page. The blast radius is the API reference section. Other pages do not read this pin. Intended effectOpenAPI-backed API pages keep loading at the current share of all page loads. Hold that share in the measured band. Absent looks like those loads fall toward zero while other page loads continue.
Hourly OpenAPI-inclusive API loads ranged from 7 to 93 in that 24h window. Compare on the 24h share. Do not compare one hour to another hour. Regression watchThis pin can drop API paths or break ApiPage render. Watch 404s and page-load failures on API URLs. Put each risk on these checks.
Not observableBuild-time fetch of the schema has no runtime metric. A miss fails the Vercel build. This session did not compare rendered HTML to the prior pin. Client errors on API URLs in the last 24h were three third-party fetch failures. Those errors are not a schema signal. |
|
Verified in
|
No description provided.