[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 22, 2026 6:57pm UTC
sentry-docs	Ready	Preview	Oct 22, 2026 6:57pm 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 documentation page loads, 404s on those pages, and client errors on those pages. An issue escalates when API page errors or 404s rise. This pin does not add new API page content.

Services: sentry-docs, develop-docs.

Mention @change-monitor in a comment to update the plan.

Plan

What changed

The production build now loads the OpenAPI schema from git SHA 67fda936. The dereferenced OpenAPI file at that SHA matches the previous SHA blob. API documentation pages keep the same endpoints and text.

sentry-docs and develop-docs must deploy this commit. skip-build rebuilds both because the change sits in src/. API category and endpoint pages render only on sentry-docs.

Risk

A bad schema fetch fails the sentry-docs build. The old site then stays live. A malformed schema can drop API pages and raise 404s. This SHA does not change the OpenAPI document, so that content risk is low. The shared src rebuild can still break both sites if the page module fails.

Intended effect

This change has no queryable new behavior. The OpenAPI blob is the same at both SHAs. Do not treat a quiet error rate as proof that a new schema is live. Record intended_effect as unknown.

Regression watch

These checks cover missing API pages and client failures on the API docs path.

Signal	Baseline	Window	Source	Rule
Client error events on /api/ URLs as a share of API page loads	0.7-1.9%	2026-10-20T18:51:19Z to 2026-10-22T18:51:19Z	Sentry org sentry project docs. Errors: environment:production AND url:"*/api/*". Loads: metric.name:docs.page.load AND page_type:api AND sentry.environment:production. Last 24h was 6 errors and 884 loads. Prior 24h was about 14 errors and 758 loads.	Hold in 0.7-1.9%. A rise above the band is a regression.
Pageload and navigation span error rate on https://docs.sentry.io/api/*	1.3-3.3%	2026-10-20T18:51:19Z to 2026-10-22T18:51:19Z	Sentry org sentry project docs. Query: span.op:[pageload,navigation] url.full:"https://docs.sentry.io/api/*" sentry.environment:production. Last 24h was 10 errors in 747 spans. Prior 24h was about 23 errors in 706 spans. Traces are sampled at 30%.	Hold in 1.3-3.3% of sampled spans. A rise above the band is a regression.
API page 404s as a share of API page loads	1.9% from 17 of 884 loads	2026-10-21T18:51:19Z to 2026-10-22T18:51:19Z	Sentry org sentry project docs. Query: metric.name:docs.page.not_found AND requested_path:api* AND sentry.environment:production. Last 24h split: api/alerts 9, api/events 4, api/projects 2, api/explore 1, api/discover 1.	Hold near 1.9%. A rise that doubles this share with stable loads is a regression. The prior 24h 404 count is not measured.

If 404s rise, group docs.page.not_found by requested_path. A single API category that jumps is this change until proven otherwise.

Not observable

Prior 24h count of docs.page.not_found for requested_path:api*. develop-docs page volume, so its error rate cannot be formed. Whether the running build fetched schema SHA 67fda936. Schema fetch failures occur at build time and do not emit a production metric.