[billyvg]

Why?

apiContracts.generated.ts is built from backend serializers and response annotations, so it goes stale whenever a backend response changes. Right now it's only regenerated when someone runs make build-api-contracts by hand.

• feat(api): Add the generated frontend API contracts #129590

How?

One backend job, api typescript generation, replaces the API URL job. On every backend change it regenerates knownSentryApiUrls.generated.ts, then the contracts from those URLs, and commits both back to the PR in one commit. Before committing, it typechecks the frontend against the new contracts, so a backend change that breaks a frontend consumer fails the job instead of being committed.

build-api-contracts now depends on a new build-api-urls make target, so the contracts are never built against stale URLs, in CI or locally.

Decisions

• The URL and contracts syncs are one job because the contracts generator keys its response types on the known URLs file. Run side by side, the contracts were built against the old URLs and dropped any new route. Each job also committed separately, and each bot commit cancelled and restarted the whole backend run.
• It runs on every backend change, not only urls.py, since response types can come from anywhere in the backend. The URL sync only takes seconds once the job has set up.
• It isn't part of the required Backend check yet, while the contracts are new. If the contracts fail to build, typecheck or lint, the job fails but drops them and still commits the URLs, so the existing URL sync keeps working.
• On PRs it runs on ubuntu-26.04-arm, like the other backend jobs.
• Fork PRs get no secrets, so there it still regenerates and typechecks but skips the commit. The app token is minted only after the PR's own code has run. The old URL job minted it before checkout.
• Like the API URL file, the generated file has no CODEOWNERS owner and doesn't count toward the frontend/backend scope warning, so the bot's commit doesn't request frontend review on backend PRs.
• Catching drift on master (e.g. two PRs merging out of order) and making the job required are left for a follow-up.

🤖 Generated with Claude Code

[github-actions]

🚨 Warning: This pull request contains Frontend and Backend changes!

It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently.

Have questions? Please ask in the #discuss-dev-infra channel.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 9e112ec. Configure here.}

[cursor]

Typecheck missing Node heap limit

Medium Severity

The new required job runs pnpm run typecheck without the NODE_OPTIONS heap limit that frontend.yml and type-coverage-diff.yml set for the same command. Combined with backend-ci services on ubuntu-26.04-arm, tsc can exhaust the Node heap and fail the Backend check on backend-only PRs.

 

^{Reviewed by Cursor Bugbot for commit 9e112ec. Configure here.}

[linear-code]

CW-3039

[sentry]

Sentry Snapshot Testing

Name	Added	Removed	Changed	Renamed	Unchanged	Skipped	Status
sentry-frontend sentry-frontend	0	0	0	0	780	0	✅ Unchanged

⚙️ sentry-frontend Snapshot Settings

[joshuarli]

cool

[scttcper]

feels like we might combine these jobs that all run when an api changes, like the knownApi thing