Repository navigation
Bump API schema to a25931d5 - #20115
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-path 404s, and client errors on API pages. An issue escalates when API page loads fall or those 404s and errors rise. Monitoring in Services: Mention PlanWhat changedThe site now builds API pages from OpenAPI schema SHA a25931d59d71c403d7d912bf9eca4308ab36f70b. The sentry-api-schema range from 3cdad0342a56d71baff4742c39b83a22c76f9fbd only edits CHANGELOG.md and package.json to 0.367.0. The OpenAPI document used at build time did not change. Requests to /api/ category and endpoint pages should keep serving the same content. sentry-docs must deploy before these pages are live. develop-docs also builds this src file from the same commit. develop-docs does not call apiCategories and does not serve API pages. RiskA failed fetch of the new SHA can fail the sentry-docs build. Dropped endpoint slugs can 404 on existing API URLs. Invalid description markdown can break API page render. The shared src module can fail the develop-docs build or bundle. Intended effectThis pin does not add a new runtime counter. The OpenAPI document did not change, so new API pages should not appear. confirmed means API page loads stay in the measured share band. absent means that share falls toward 0 while other page loads hold.
Regression watchAPI-path 404s would rise if slugs disappear. Client errors on /api/ URLs would rise if page render breaks. Site-wide client errors would rise if the shared page module fails. develop-docs client errors would rise if the shared bundle breaks. The 7d docs error count is 12184 and is not this band. An earlier spike likely raised that week total. Use the last 48h for docs errors.
Not observablePageload traces for /api/ docs routes returned 0 rows. A later HTTP span search for url.full:/api/ mixed other /api/ calls, so page latency and HTTP 5xx for API docs routes are not named here. No runtime signal exposes the live schema SHA, so HTML parity with a25931d5 cannot be confirmed from telemetry. Web vitals for API pages were not measured. develop-docs page load volume was not measured, so that error watch lacks a traffic denominator. |
No description provided.