[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 26, 2026 11:33pm UTC
sentry-docs	Ready	Preview	Oct 26, 2026 11:33pm 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 plan checks API page loads, API 404s, and production errors. An issue escalates when API page loads drop. An issue also escalates when API 404s or error volume rise.

Rollout complete

Services: sentry-docs.

Plan

What changed

The production build fetches OpenAPI snapshot 916a2cd6. API reference pages rebuild from that snapshot. The snapshot JSON matches the currently pinned generated commit. Only sentry-docs must deploy for this change to go live. develop-docs rebuilds the same SHA. It does not generate API pages.

Risk

A failed schema fetch blocks the production build. Users then keep the previous pages. A bad schema can drop endpoint pages and return 404. A bad schema can also throw while a page renders. This pin does not change documented endpoints. The watch is still a failed rebuild of the API section.

Intended effect

This pin does not add or remove documented endpoints. The intended effect is that API pages keep loading after the rebuild. Absent: API page loads fall toward zero while other page types still load.

Signal	Baseline	Window	Source	Rule
docs.page.load page_type=api	505-1072 counts per 24h. Weekday 24h was 1072. Weekend 24h was 505.	2026-10-24T23:26:00Z to 2026-10-26T23:26:00Z	Sentry metrics sentry/docs, page_type:api environment:production on docs.page.load	Hold on the weekday side of the band. Volume is weekday-heavy. Absent if a 24h count falls below 200 while platforms page loads still increment.

Regression watch

A dropped or renamed endpoint would 404. A render throw would raise production errors. Put both on the API path, not fleet health alone.

Signal	Baseline	Window	Source	Rule
docs.page.not_found requested_path api*	3-7 counts per 24h. Share of API page loads was 0.6-0.7%.	2026-10-24T23:26:00Z to 2026-10-26T23:26:00Z	Sentry metrics sentry/docs, requested_path:api* environment:production on docs.page.not_found	Hold the share in 0.5-0.8% of API page loads. Detected if the share rises above 2% or the 24h count exceeds 20.
production error events	Last 24h was 873 events. 757 of those share one noisy title. The other 116 are the usable weekday baseline. Prior 24h was about 12069 events. That day is not a normal band.	2026-10-25T23:26:00Z to 2026-10-26T23:26:00Z	Sentry errors sentry/docs, environment:production	Hold near 116 events per 24h after you exclude that noisy title. Detected if that remainder exceeds 250, or total events exceed 1800, or new MDX or render titles appear.

If API 404s rise while platforms page loads hold, treat it as this change. If both drop, treat it as a wider outage.

Not observable

Pageload traces and LCP for /api URLs returned zero rows. Error events filtered to transaction /api/ returned zero rows. HTTP 5xx spans returned zero rows. Field-level correctness of regenerated endpoint docs has no metric. The build-time GitHub fetch of openapi-derefed.json is not in runtime telemetry. The 24h page-load total is incomplete, so the error-rate denominator for all traffic is missing.

[cursor]

Verified in production

• API pages kept loading on this build, and not-found counts did not rise.
• Live API reference pages still load after this rebuild.