[sentry-api-schema-updater]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
develop-docs	Ready	Preview	Oct 27, 2026 6:14pm UTC
sentry-docs	Ready	Preview	Oct 27, 2026 6:14pm UTC

[github-actions]

Please update the IS YOUR CHANGE URGENT? section of the PR description:

• Select exactly one option.
• If you selected an urgent or other deadline, provide the date as YYYY-MM-DD.

This information helps the Docs team prioritize your review.

[cursor]

The change rebuilds generated API pages from a new schema pin. The schema file matches the previous pin. An issue escalates when generated API page loads fall, API 404s rise, or API page errors rise.

Rollout complete

Services: sentry-docs.

Plan

What changed

Generated API pages now build from schema pin b26eb866. The OpenAPI file at that pin matches the previous pin. Requests to generated API routes keep the same paths and bodies as before.

This change is live after a production deploy of sentry-docs. Vercel project sentry-docs ships those pages. develop-docs also builds this commit. It does not generate OpenAPI pages.

Risk

A bad schema pin can omit generated API routes. Users then get 404s on old endpoint URLs. A heavy schema page can slow endpoint views. A render fault can mark those navigations as errors. The OpenAPI file is identical at both pins, so a content remap is unlikely. A failed rebuild can still hide every generated API page.

Intended effect

Generated API pages must keep loading after the rebuild. absent looks like docs.page.load with page_type:api and has:api_category falling toward 0 while page_type:api loads without api_category hold. Those untagged loads are static /api/ guides, not OpenAPI pages.

Signal	Baseline	Window	Rule	Source
Share of API page loads that set api_category (docs.page.load, page_type:api, has:api_category over all page_type:api)	53-61% (404 of 760 last 24h, 631 of 1040 prior 24h)	2026-10-25T18:08Z to 2026-10-27T18:08Z	Hold in this band	Sentry metrics, org sentry, project docs, environment production

Regression watch

A slug miss shows up as API 404s. A render fault shows up as error spans on /api/ navigations. A heavy page shows up as slower endpoint pageloads. Static /api/ guides sit on the same /api/ path family and must keep loading.

Signal	Baseline	Window	Rule	Source
API 404 rate (docs.page.not_found requested_path:api* over docs.page.load page_type:api)	0.4-1.7% (4 of 1040 prior 24h, 13 of 760 last 24h)	2026-10-25T18:08Z to 2026-10-27T18:08Z	Do not rise above this band	Sentry metrics, org sentry, project docs, environment production
Error share on /api/ pageload and navigation spans (span.status:error and url.path:/api/*)	2.6% (17 of 653 spans)	2026-10-26T18:08Z to 2026-10-27T18:08Z	Hold near this share. Do not treat a jump above 5% as noise	Sentry traces, org sentry, project docs, environment production. Traces sample at 30%
p95 duration for /api/*/* pageload and navigation spans	7980-8150ms (7976ms over 48h, 8148ms last 24h)	2026-10-25T18:08Z to 2026-10-27T18:08Z	Hold in this band	Sentry traces, org sentry, project docs, environment production. Query span.op:[pageload,navigation] url.path:/api/*/*
Static API guide loads (docs.page.load, page_type:api, no api_category)	356 last 24h and 409 prior 24h, 1.8-2.3% of all page loads	2026-10-25T18:08Z to 2026-10-27T18:08Z	Hold in this band. A drop with generated loads still present is not this pin	Sentry metrics, org sentry, project docs, environment production

If API 404s rise, inspect requested_path for dropped category slugs. If error spans rise, inspect /api/ traces for render faults on ApiPage.

Not observable

Error events do not slice to /api/ URLs. The Next route name is /:path*?.

The prior 24h error-span rate on /api/ was not measured with the same url.path:/api/* filter. That prior share is unknown.

[cursor]

Verified in production

• Generated API pages kept loading after the rebuild, and API 404s did not rise.