Repository navigation
Bump API schema to 6d0a2152 - #20216
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 reference page loads, missing API paths, and client TypeErrors. An issue escalates when API page loads fall or missing API paths rise. Other docs page loads must hold. Services: PlanWhat changedAPI reference pages now build from OpenAPI schema 6d0a2152. The OpenAPI JSON did not change from the prior SHA. Users must still see the same API pages. sentry-docs must deploy before the new SHA is live. develop-docs also rebuilds this commit from the same tree. That site does not generate API pages. develop-docs is listed because src/ ships in both Vercel projects. RiskA failed schema fetch can fail the production build. A slug change can return not-found for API pages. A parameter shape change can crash API page render. Those failures stay on the API reference path. The same deploy also ships every other docs page. Intended effectAPI pages must keep loading at the measured share of all page loads. The OpenAPI JSON is unchanged, so the share must hold. Absent looks like a drop in the API share while other page types hold. Query
Regression watchA slug or render break on API pages shows as not-found events or TypeErrors. Sibling platforms pages show whether the whole deploy is broken.
Not observableTelemetry cannot read the HTML of query-parameter types on API pages. That gap does not hide a new content shift because the OpenAPI JSON did not change. Pageload transactions use /:path*?, so TypeErrors cannot be sliced to /api/ URLs. Use the API not-found signal for path-level failures. |
No description provided.