Repository navigation
Bump API schema to c22a3401 - #20282
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, not-found events on API paths, and client errors on those pages. An issue escalates when API page loads collapse while other pages hold. It also escalates when API not-found events or API-page errors rise. Services: Mention PlanWhat changedAPI reference pages now build from schema SHA sentry-docs must deploy before the pin is live. develop-docs also deploys this shared source file. Developer docs do not render API pages. Catalog and Vercel both ship RiskA missing or invalid schema file fails the production build. Users then lose the API reference tree. Old API URLs would 404 if endpoint slugs changed. This pin does not change the JSON, so slug drift is unlikely. A broken shared rebuild can still raise client errors on both sites. Intended effectThe pin adds no new metric. Success is API reference pages still loading at the measured share. Hold the pooled share in the band. Do not treat a traffic shift that keeps the share as
Regression watchThis pin can drop the API tree or 404 old endpoint URLs. It can also break the shared app after rebuild.
If API not-found events rise, check Not observableThe schema SHA is not shown on the page, so the pin itself is not queryable. Release 0.415.0 lists no new endpoints. The OpenAPI JSON did not change, so no new-path load signal exists. API pageload duration has only one 24h sample. p75 was 4853ms. p95 was 12378ms. Count was 313 sampled pageloads. The prior-day split was not taken. Soft-navigation LCP was not queried. Record latency as The 48h fleet error count on project The prior-day develop-docs error rate was not sampled. The 24h rate above is the only measured point. |
No description provided.