Repository navigation
Bump API schema to de3e9904 - #20040
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, API page latency, and errors on those pages. An issue escalates when API page load share falls or those errors rise. Services: PlanWhat changedThe production build fetches the OpenAPI document from commit de3e9904. That document matches the prior pin 7fb093da. API reference pages keep the same paths and the same content. sentry-docs and develop-docs must deploy before this commit is live. Only the sentry-docs build generates API reference pages from the schema. develop-docs ships the same source file and does not generate those pages. The Vercel deploy workflow reports both services. RiskA failed schema fetch fails the sentry-docs build. A bad static generate would drop API pages or break their render. Removed endpoint slugs would 404. This SHA does not change the schema file. Intended effectThis pin does not add a new page or a new metric. The OpenAPI file is unchanged between the two SHAs. There is no queryable intended effect. Production telemetry cannot show Regression watchA missing generate would cut API page load share and raise API 404s. A broken API page would raise errors on API URLs and pageload time. Current API page errors are third-party fetch failures from Algolia and Kapa. Hourly pageload p95 is noisy and often 0 when volume is low. Use pooled 24h values. Share may move with weekday traffic mix. If the error rate rises, check error titles for ApiPage or schema parse failures.
Not observableThe pinned SHA is not emitted at runtime. develop-docs has no OpenAPI page signal. Build-time GitHub fetch success is not in Sentry. |
No description provided.