Repository navigation
Bump API schema to e3ee5395 - #20157
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 OpenAPI page loads, API-path 404s, and client errors on those pages. An issue escalates when OpenAPI page loads drop or those 404s or errors rise. Services: Mention PlanWhat changedThe product-docs build fetches the public API schema from git SHA e3ee5395. The schema JSON matches the prior pin. Generated API docs pages stay the same after deploy. sentry-docs must deploy before this change is live. develop-docs rebuilds the same repository and does not render OpenAPI pages. RiskA missing schema file fails the product-docs build and blocks the ship. A schema that changes slugs returns 404 on old API docs URLs. Broken endpoint markup can throw in the browser. This pin has identical JSON, so those content failures are unlikely. Intended effectOpenAPI-generated API docs pages keep loading after the pin change. Absent looks like those loads fall toward zero while other docs pages still load.
Regression watchThis pin can still 404 API docs URLs if the static paths do not build. It can also throw in the API page client.
The error rate may include third-party script noise. Known titles include Algolia fetch failures and Event promise rejections. Escalate when new titles appear from API page render. If API-path 404s rise, split by Not observableNo signal compares page body text to schema fields. Traces sample at 30 percent, so pageload counts are not full traffic. The 24h pageload p95 query for docs.sentry.io/api did not return. Use 404s and errors for failure, not pageload time. |
No description provided.