Repository navigation
Bump API schema to b5335bf4 - #20233
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 and not-found counts. An issue escalates when API page loads collapse or not-found counts rise. Rendered API reference content is expected to stay the same. Services: Mention PlanWhat changedThe docs build fetches the public API schema from git SHA b5335bf4. API reference pages must keep the same OpenAPI document as SHA 46e6baad. The JSON blob hash did not change. sentry-docs must deploy before the new fetch SHA is live. develop-docs also ships this shared source file. develop-docs does not fetch or render the OpenAPI schema. RiskA failed schema fetch fails the production docs build. A parse error drops API endpoint pages from the static path list. Users then see not-found responses for those endpoints. A new tag slug can replace an existing API guide page. Intended effectAPI reference pages must keep loading after the rebuild. The OpenAPI body did not change. Absent means API page loads fall far below the band while other docs traffic continues.
Regression watchThis change can drop generated API endpoint pages. Those misses show up as not-found events. If not-found volume rises, group by requested_path and inspect api paths.
The 24h not-found top paths included api/events at 2 counts. That path was the only api path in the top 10. Not observablePageload p95 and span count for /api/ paths. Sentry trace search timed out twice. |
No description provided.