Bump API schema to 35974eba

[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 7, 2026 11:20am UTC
sentry-docs	Error		Oct 7, 2026 11:20am 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 path 404s, and client errors on those pages. An issue escalates when API page loads drop, or when 404s or new client errors on those pages rise.

Monitoring in production

Services: sentry-docs, develop-docs.

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

Plan

What changed

API reference pages now list geo_country_code on filter condition fields. The site build fetches OpenAPI schema 35974ebad9d43eaed78cebda0db11545ca4992c6 instead of a1824c257dc164ac2d830e6fcef5410e34a1b8d2. The schema adds that enum value on existing endpoints. It does not add or remove API paths. sentry-docs and develop-docs must both deploy this commit. Only sentry-docs renders the OpenAPI pages. The effect is live after sentry-docs deploys.

Risk

A broken schema can omit API pages or crash the API page renderer. Readers then hit 404s or fail to load API reference pages. Search widget fetch errors already occur on these pages. Those fetch errors are not this change.

Intended effect

The change updates generated page text. Sentry cannot show that geo_country_code is on the page. Absent looks like the old condition field list without geo_country_code. Leave intended_effect unknown from telemetry.

Regression watch

This diff can drop or break API reference pages during the static build. Watch page loads, 404s, and client errors on that path. Most current client errors are search widget fetch failures. Treat new error titles as the symptom.

Signal	Baseline	Window	Source	Rule
API reference page loads	811-901 per 24h	2026-10-06T11:15:00Z to 2026-10-07T11:15:00Z measured 901. 2026-09-30T11:15:00Z to 2026-10-07T11:15:00Z measured 5676, about 811 per day	Sentry org sentry, project docs, metric docs.page.load, query page_type:api environment:production	Hold this band. Escalate if the 24h count falls below 811
API path 404 rate	1.3-1.4% of API page loads. 10-13 404s per 24h	Same windows. 13 404s and 901 loads in 24h. 72 404s and 5676 loads in 7d	Sentry org sentry, project docs, metric docs.page.not_found, query environment:production requested_path:api*	Hold this band. Known noise on api/alerts. Escalate if the 24h rate rises above 1.4% or a former live path 404s
Client errors on API URLs	13 events in 24h. About 45 per day over 7d	Same windows. 13 in 24h. 315 in 7d	Sentry org sentry, project docs, errors query environment:production http.url:"*/api/*"	Escalate if 24h events rise above 45, or if new titles appear. TypeError Failed to fetch on insights.algolia.io and proxy.kapa.ai is known noise

Daily volume may vary. Compare the same 24h length after deploy. If the error count rises, check titles on /api/ URLs for renderer failures, not only widget fetch failures.

Not observable

Page body text that lists geo_country_code. Request traces with transaction /api/ returned zero spans. The transaction name is /:path*? so those traces cannot fill this plan.