Bump API schema to 678631a8

[sentry-api-schema-updater]

No description provided.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
develop-docs	Ready	Preview, Comment	Jun 15, 2026 3:56pm
sentry-docs	Ready	Preview, Comment	Jun 15, 2026 3:56pm

[sentry]

Bug: The code in apiCategoriesUncached directly accesses properties of a fetched OpenAPI schema without null checks, which could cause a build failure if the schema structure changes.
_{Severity: MEDIUM}

Suggested Fix

Add validation and defensive checks when processing the fetched OpenAPI schema. Wrap property access in try-catch blocks or use optional chaining (?.) and nullish coalescing operators (??) to provide default empty values (e.g., (data.tags || []).forEach(...)) to prevent crashes if a required field is missing.

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#L9

Potential issue: The function `apiCategoriesUncached` in `resolveOpenAPI.ts` fetches and
parses an OpenAPI schema. It directly accesses properties on the resulting data object,
such as `data.tags`, without defensive checks. If the schema fetched from the new commit
SHA is missing properties that the code assumes are present (like the `tags` array), the
build process will crash with a `TypeError` when `forEach` is called on `undefined`.
This lack of error handling or validation for the external schema makes the build
process brittle and susceptible to failures from upstream schema changes.

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

[aldy505]

Conflict with newer branch, skipping this