Repository navigation
Bump API schema to 96ef41e3 - #20267
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 API reference pages from a new schema pin that matches the prior schema file. The plan checks API page loads, API 404s, and client errors on those pages. An issue escalates when API page loads drop or API 404s rise. Monitoring in Services: Mention PlanWhat changedRequests to RiskThe user docs build fetches this schema while it generates every page path. A missing or invalid schema file fails that production build. A schema that parses but drops endpoints returns 404s for old API URLs. A schema that changes slugs breaks inbound links to those pages. This pin does not change the schema JSON. Those content failures are unlikely for this deploy. Client failures on API pages would show as errors on the catch-all route. Intended effectThis pin does not add a metric or a new route. The schema file is unchanged. Confirm the change by API page loads holding as a share of all page loads.
Regression watchThis pin can drop API pages if the fetched schema is empty or renamed. It can also fail client render on those pages. Watch API 404s, client errors on API URLs, and platforms page loads as the sibling path.
Site-wide pageload p95 was 10.9s in the latest 24h. API pageload and navigation p95 was 8.2s on 767 sampled spans. Latency is not a primary watch for this identical schema pin. Not observableProduction telemetry does not report the live schema SHA. The plan cannot confirm the pin itself. API endpoint copy is not in metrics. Client errors on API URLs were not measured for the prior 24h window with the same query. |
No description provided.