[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 8:02pm UTC
sentry-docs	Ready	Preview	Oct 27, 2026 8:02pm 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 reference page loads, API 404s, and client errors on those pages. An issue escalates when API page loads fall, API 404s rise, or client errors rise. The rebuild can also raise errors on other pages.

Rollout complete

Services: sentry-docs, develop-docs.

Plan

What changed

The production build fetches OpenAPI from schema SHA 2fc9a138 instead of 978abb76. API reference pages still generate from openapi-derefed.json at that SHA. That JSON file did not change in schema release 0.412.0. The release only added an SDK operation catalog that these pages do not read.

sentry-docs must deploy before API pages use the new SHA. develop-docs also deploys because this file sits outside content directories. develop-docs does not call the OpenAPI loader at runtime.

Risk

A missing or invalid schema file fails the production build. A parse break drops API pages from static generation and serves 404s. The full-site rebuild can break other pages such as search and the platform selector. develop-docs rebuilds from the same commit and can error without rendering API pages.

Intended effect

API reference pages keep loading after deploy. The OpenAPI document is unchanged, so page content should not shift. Absent looks like API page loads near zero while other page types hold.

Signal	Baseline	Rule	Source
docs.page.load with page_type:api in production	751 in 2026-10-26T19:56Z to 2026-10-27T19:56Z. 1062 in 2026-10-25T19:56Z to 2026-10-26T19:56Z. 1813 of 37517 total page loads over those 48h, a 4.8% share.	Hold in 751-1062 per 24h and near the 4.8% share. Do not treat the band edge as the goal.	Sentry metrics, sentry/docs

Regression watch

A schema parse break would 404 API paths that used to resolve. The site rebuild can raise client errors on API pages and on other pages. The 404 paths below look like guessed category names, not missing generated endpoints.

Signal	Baseline	Rule	Source
docs.page.not_found with requested_path matching api* in production, as a share of API page loads plus those 404s	13 of 764 attempts, 1.7%, in 2026-10-26T19:56Z to 2026-10-27T19:56Z. 4 of 1066 attempts, 0.4%, in 2026-10-25T19:56Z to 2026-10-26T19:56Z.	Stay in 0.4-1.7%. Escalate if the share rises above 1.7%.	Sentry metrics, sentry/docs
Production errors on URLs that contain /api/	5 errors against 1813 API page loads, 0.3%, in 2026-10-25T19:56Z to 2026-10-27T19:56Z.	Hold under 0.3% of API page loads. Escalate if the share rises above 0.3%.	Sentry errors, sentry/docs
Production errors against all docs.page.load events	1679 errors against 37517 page loads, 4.5%, in 2026-10-25T19:56Z to 2026-10-27T19:56Z. 795 errors in the last 24h. 884 errors in the prior 24h.	Hold near 4.5%. Escalate if the share rises above 4.5%.	Sentry errors and metrics, sentry/docs

Not observable

Pageload latency for /api/ URLs was not measured. The catch-all route does not name those paths as transactions. The SHA pin is not exposed on the page, so telemetry cannot prove the new pin. develop-docs has no pre-ship page-load count, so its error rate cannot be judged. The 24h split of API-page errors was not queried.

[cursor]

Verified in production

• API reference pages still load after this ship, and error rates stayed normal.