Repository navigation
Bump API schema to 80b62b7f - #19846
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. |
|
This change rebuilds API reference pages from a new OpenAPI schema. The plan uses API page loads, API 404s, and client errors on those pages as signals. An issue escalates when API page loads drop or those 404s and errors rise. Services: Mention PlanWhat changedAPI reference pages now build from OpenAPI schema 80b62b7f. That schema only changes the Vercel installation RiskA bad schema can fail the docs build or drop API pages. Users then see 404s or client errors on API reference paths. This SHA changes one unused field. The blast radius may stay small. A parse failure would still hit every API reference page. Intended effectTelemetry cannot show that pages now use schema 80b62b7f. Use API page loads as the proxy that rebuilt API pages are served.
Regression watchThis schema rebuild can drop API routes or break API page render. Watch 404s on API paths and client errors on those pages. Search and chat fetch errors are already in the API error baseline. Do not treat those alone as a schema failure.
If API 404s rise, inspect missing category or endpoint slugs from the new schema. If API errors rise beyond Algolia and Kapa fetch noise, inspect API page render. Not observableThe live page does not expose schema SHA 80b62b7f. The renderer has no |
No description provided.