Bump API schema to dcb185fa

[getsantry]

No description provided.

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
develop-docs	Ready	Preview	Comment	Dec 12, 2025 7:23pm
sentry-docs	Ready	Preview	Comment	Dec 12, 2025 7:23pm

[sentry]

Bug: The fetch call in resolveOpenAPI lacks error handling. It calls response.json() without first checking if the network request was successful via response.ok, which can cause crashes.
_{Severity: CRITICAL | Confidence: High}

🔍 Detailed Analysis

The resolveOpenAPI function fetches a JSON schema from GitHub using fetch. However, it does not check if the response was successful (e.g., response.ok) before attempting to parse the body as JSON with response.json(). If GitHub returns a non-2xx status code, such as a 404 or 500, response.json() will fail when trying to parse the resulting error page's HTML. This unhandled promise rejection will cause a Next.js server component to crash, resulting in a 500 error for the user, or cause the entire site build to fail during the mdx.ts execution.

💡 Suggested Fix

Before calling await response.json(), add a check to ensure the request was successful. For example: if (!response.ok) { throw new Error(Failed to fetch API schema: ${response.statusText}); }. This will provide a clear error message and prevent crashes from attempting to parse non-JSON responses.

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: src/build/resolveOpenAPI.ts#L12

Potential issue: The `resolveOpenAPI` function fetches a JSON schema from GitHub using
`fetch`. However, it does not check if the response was successful (e.g., `response.ok`)
before attempting to parse the body as JSON with `response.json()`. If GitHub returns a
non-2xx status code, such as a 404 or 500, `response.json()` will fail when trying to
parse the resulting error page's HTML. This unhandled promise rejection will cause a
Next.js server component to crash, resulting in a 500 error for the user, or cause the
entire site build to fail during the `mdx.ts` execution.

_{Did we get this right? 👍 / 👎 to inform future reviews.
Reference ID: 7465370}