[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 21, 2026 2:29pm UTC
sentry-docs	Ready	Preview	Oct 21, 2026 2:29pm 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 not-found events, and client errors on API pages. An issue escalates when API page loads fall or those errors rise.

Rollout complete

Services: sentry-docs, develop-docs.

Plan

What changed

API reference pages now rebuild from OpenAPI schema SHA 8de28f6d. The OpenAPI body at that SHA matches the prior pin. Only ownership stats changed in the schema repository.

sentry-docs must deploy before those pages are live. develop-docs also deploys this commit because it shares the src tree. Only sentry-docs renders API pages. Deploy config maps both Vercel production ships to these catalog ids.

Risk

A bad schema pin can omit API routes from the static path list. Former API URLs then return not-found. A fetch or parse failure fails the sentry-docs production build. The shared src import can fail the develop-docs build even though that site does not render API pages.

Intended effect

The schema body is unchanged, so no new API page content is expected. Confirm the rebuild still serves API pages. The signal is docs.page.load with page_type api as a share of all docs.page.load. Absent: that share falls toward zero while other page loads continue.

Signal	Baseline	Rule	Source
API page load share	4.3% from 743 of 17286 page loads in 2026-10-20T14:23:52Z to 2026-10-21T14:23:52Z. 5.1% from 852 of 16812 page loads in 2026-10-19T14:23:52Z to 2026-10-20T14:23:52Z. Band 4.3-5.1%.	Hold in 4.3-5.1%. Expected shift is none.	Sentry org sentry, project docs. sum(docs.page.load) with page_type:api environment:production over sum(docs.page.load) with environment:production.

Regression watch

This pin can drop or break API pages. It can also fail the shared compile on the sibling ship.

This error rate uses error events over API page loads.

Signal	Baseline	Rule	Source
API not-found rate	2.0% from 15 not-found of 758 API attempts in 2026-10-20T14:23:52Z to 2026-10-21T14:23:52Z. 1.0% from 9 of 861 in 2026-10-19T14:23:52Z to 2026-10-20T14:23:52Z. Band 1.0-2.0%.	Hold in 1.0-2.0%. Rise above the band means dropped API routes.	Sentry org sentry, project docs. sum(docs.page.not_found) with requested_path:api environment:production over that count plus sum(docs.page.load) with page_type:api environment:production.
API-path error rate	1.8% from 13 errors of 743 API page loads in 2026-10-20T14:23:52Z to 2026-10-21T14:23:52Z. 1.1% from 9 of 852 in 2026-10-19T14:23:52Z to 2026-10-20T14:23:52Z. Band 1.1-1.8%.	Hold in 1.1-1.8%. Rise above the band means broken API pages.	Sentry org sentry, project docs. count() of errors with environment:production (transaction:/api/ OR http.url:/api/) over sum(docs.page.load) with page_type:api environment:production.

Not observable

Pageload and navigation span counts for transaction /api/* were zero in 2026-10-20T14:23:52Z to 2026-10-21T14:23:52Z. API page latency is not available from traces. The schema SHA is not exposed in production telemetry. develop-docs error counts were 29 in 2026-10-20T14:23:52Z to 2026-10-21T14:23:52Z and 35 the day before. Page-load volume for that project was not measured, so there is no rate.

[cursor]

Verified in production

• API pages still load after the rebuild, and not-found and error rates stay in band.