Repository navigation
Bump API schema to 5bd01cda - #20266
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 page loads, API 404s, and client errors on API pages. An issue escalates when API 404s rise or API page loads fall while other pages hold. The rendered API schema content did not change. Monitoring in Services: Mention PlanWhat changedThe production build now fetches the OpenAPI document at schema SHA 5bd01cda. That commit did not change RiskA failed schema fetch fails the production build and leaves the live pin unchanged. A dropped endpoint slug returns 404 for that page. A broken schema would crash API page render. This bump only changed ownership stats, so content risk is low. Blast radius is the generated API docs pages and the shared page render. Intended effectThe pin is live when API docs pages keep loading after deploy. The OpenAPI file did not change, so loads should hold.
The earlier 24h in the 48h sample had 1029 API loads. The 7d total was 5028, about 718 per day. Use the share, not the raw count, if site traffic shifts. Regression watchThis diff can drop generated slugs or break API page render. Watch 404s on API paths and errors on those URLs. Also watch site-wide errors on the same ship.
Current API 404s are mostly unknown slugs such as Not observableNo signal shows the OpenAPI body text on the page. The prior 24h count for API URL errors was not sampled. Errors cannot group by |
No description provided.