Repository navigation
Bump API schema to 8753a857 - #19868
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 pins a new OpenAPI schema SHA at build time. API reference pages rebuild from that file. The plan checks API page loads, API not-found counts, and client errors. An issue escalates when API pages stop loading or those errors rise. Monitoring in Services: Mention PlanWhat changedThe API docs build now fetches OpenAPI schema 8753a857 instead of f73faaac. User requests to API pages then receive pages built from that schema. The published OpenAPI JSON is the same at both SHAs. Only ownership stats changed in the schema repository. sentry-docs must deploy before API pages go live. develop-docs also deploys. Vercel skip-build rebuilds every RiskA bad schema fetch or parse can fail the sentry-docs build or drop API routes. Users then see not-found pages on API paths. The shared Intended effectThe schema SHA is not visible in telemetry. The OpenAPI JSON did not change, so no new page appears. Success is that API pages keep rendering after the rebuild.
Regression watchThis rebuild can drop API routes or ship a bad shared client bundle. Watch API not-found counts and client errors on both deploys.
If API not-found counts rise, inspect missing API slugs. If develop-docs errors rise without API not-found movement, inspect the shared client bundle. Not observableAPI pageload latency. One trace search for |
|
Verified in
|
No description provided.