Repository navigation
Bump API schema to 6cddbd97 - #19882
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. An issue escalates when API page loads fall away or those 404s or errors rise. Monitoring in Services: Mention PlanWhat changedThe static build now fetches OpenAPI from schema SHA 6cddbd9721600d181331c7ed718b93d39f81e732. API category and endpoint pages under /api/ render from that schema. sentry-docs must deploy before the new pin is live. The schema commit does not change openapi-derefed.json, so page bodies should match the prior pin. develop-docs shares this source file but does not generate API pages. RiskA broken schema can omit API pages from the static build. Readers then get 404s on former endpoint URLs. A schema that builds can still throw in the API page renderer. Other docs pages share the same catch-all route. A render crash can surface as site-wide client errors. Intended effectAPI pages keep loading after deploy. This pin has no new OpenAPI body, so success is continued API page loads, not new paths. Absent looks like the API page-load share falling toward zero while all page loads hold.
Regression watchThis pin can drop or break API pages. Watch API 404s and client errors on the shared catch-all route.
Not observableThe pinned SHA is not emitted at runtime. Errors cannot be scoped to API pages because transactions use /:path*?. Build-time schema fetch failures block deploy and never appear in production. Endpoint text cannot be verified in telemetry. |
|
Verified in
|
No description provided.