Skip to content

Bump API schema to c7d6eef6 - #20154

Merged
sentry-api-schema-updater[bot] merged 1 commit into
masterfrom
bot/bump-api-schema-to-c7d6eef6
Oct 21, 2026
Merged

sentry-api-schema-updater[bot] merged 1 commit into
masterfrom
bot/bump-api-schema-to-c7d6eef6

Conversation

@sentry-api-schema-updater

Copy link
Copy Markdown
Contributor

No description provided.

@vercel

vercel Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
develop-docs Ready Ready Preview Oct 21, 2026 8:44pm UTC
sentry-docs Error Error Oct 21, 2026 8:44pm UTC

Request Review

@sentry-api-schema-updater
sentry-api-schema-updater Bot merged commit 330727b into master Oct 21, 2026
15 of 17 checks passed
@sentry-api-schema-updater
sentry-api-schema-updater Bot deleted the bot/bump-api-schema-to-c7d6eef6 branch October 21, 2026 20:42
@github-actions github-actions Bot added the Priority: Needs Triage The PR description is missing valid priority information label Oct 21, 2026
@github-actions

Copy link
Copy Markdown
Contributor

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

cursor Bot commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

The plan checks that two new endpoint pages appear and that existing API pages still load. An issue escalates when those new pages stay missing or API 404s rise.

Services: sentry-docs.

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

Plan

What changed

The public API docs now include two Integrations endpoints from schema SHA c7d6eef6. Readers can open List Code Owner Associations and Update Settings for Organization Repositories. The paths are /api/integrations/list-code-owner-associations/ and /api/integrations/update-settings-for-organization-repositories/. sentry-docs must deploy before these pages are live. develop-docs shares this source file. It does not render these OpenAPI pages.

Risk

A bad schema pin can omit API pages from the static build. Readers then see 404s on API paths. A schema shape change can throw in the API page renderer. That failure hits every API endpoint page. The Integrations category is the first slice.

Intended effect

The change worked when the two new endpoint pages return 200. Absent means those URLs still return 404. Existing API page loads can continue in that case. The new page-load counters start at zero. Confirmed means they rise above zero after a visit. Absent means they stay at zero while other API page loads continue.

Signal Baseline Rule Source
HTTP status of /api/integrations/list-code-owner-associations/ 404 at 2026-10-21T20:42:36Z Move to 200. Absent is still 404. GET https://docs.sentry.io/api/integrations/list-code-owner-associations/
HTTP status of /api/integrations/update-settings-for-organization-repositories/ 404 at 2026-10-21T20:42:36Z Move to 200. Absent is still 404. GET https://docs.sentry.io/api/integrations/update-settings-for-organization-repositories/
docs.page.load for api_endpoint:list-code-owner-associations 0 in 2026-10-20T20:42:36Z to 2026-10-21T20:42:36Z Rise above 0. Absent is stay at 0 while other API page loads continue. Sentry org sentry project docs. sum(value, docs.page.load) with environment:production page_type:api api_endpoint:list-code-owner-associations
docs.page.load for api_endpoint:update-settings-for-organization-repositories 0 in 2026-10-20T20:42:36Z to 2026-10-21T20:42:36Z Rise above 0. Absent is stay at 0 while other API page loads continue. Sentry org sentry project docs. sum(value, docs.page.load) with environment:production page_type:api api_endpoint:update-settings-for-organization-repositories

Regression watch

This change can drop or slow API docs pages. Watch volume, 404s, and pageload latency on API paths. If 404s rise, check whether Integrations pages are missing from the build.

Signal Baseline Rule Source
docs.page.load with page_type:api 775 per 24h in 2026-10-20T20:42:36Z to 2026-10-21T20:42:36Z. 805 per 24h in 2026-10-19T20:42:36Z to 2026-10-20T20:42:36Z. Band 775-805 per 24h. Hold in 775-805 per 24h. Escalate if the 24h sum falls below 775. Sentry org sentry project docs. sum(value, docs.page.load) with environment:production page_type:api
docs.page.not_found on requested_path:api* 11 per 24h in 2026-10-20T20:42:36Z to 2026-10-21T20:42:36Z. 15 per 24h in 2026-10-19T20:42:36Z to 2026-10-20T20:42:36Z. Share of API-path outcomes 1.4-1.8%. Hold in 11-15 per 24h and 1.4-1.8% of API-path outcomes. Escalate if the 24h count rises above 15 or the share rises above 1.8%. Sentry org sentry project docs. sum(value, docs.page.not_found) with environment:production requested_path:api*. Denominator is that count plus docs.page.load with page_type:api.
p95 pageload duration for url.path:/api/* 6.3s in 2026-10-20T20:42:36Z to 2026-10-21T20:42:36Z. 7.3s in 2026-10-19T20:42:36Z to 2026-10-21T20:42:36Z. Band 6.3-7.3s. Hold in 6.3-7.3s. Escalate if p95 rises above 7.3s. Sentry org sentry project docs. p95(span.duration) with span.op:pageload environment:production url.path:/api/*. Traces are sampled at 30%. This span misses soft navigations.

Not observable

The new page bodies are not in telemetry. The plan cannot confirm field lists or examples. The prior 24h error count for API URLs is missing. The last 24h count was 14. The 48h error query timed out. The prior 24h Integrations page-load count is missing. The last 24h count was 14. The 48h query timed out.

This branch had an error being deployed

1 failed and 1 active deployments
Preview – develop-docs — 71500d73 Deployed Oct 21, 2026 by vercel[bot]
Preview – sentry-docs — 71500d73 Deployed Oct 21, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Priority: Needs Triage The PR description is missing valid priority information

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants