chore(deps): Bump @sentry/api to 1.53.0 by sentry-junior[bot] · Pull Request #2113 · getsentry/toolkit

sentry-junior · 2026-11-09T16:29:14Z

Bumps the @sentry/api catalog entry from 1.51.0 to 1.53.0. The minimumReleaseAgeExclude entry and the lockfile are updated to match.

1.52.0 is the first release with the stricter response types from getsentry/sentry: literal unions, UUID formats, activities keyed on type, and typed event contexts. It was published after fix(build): Unbreak the build for uint64 fields and the bound client type sentry-api-schema#136 fixed that repo's build.
1.53.0 adds the spec sync that landed while 1.52.0 was pending (getsentry/sentry-api-schema@83a2b744). It only adds the 30-day search limit to the AI conversation endpoint descriptions; no types change.

What broke

pnpm run tsc failed in two CLI spots. Both were real mismatches, not just stricter types:

issue-app-links.ts: a Sentry App component's schema is now a union keyed on type, and only issue-link has link. Sentry stores each component's schema as the app's schema element, type included (SentryAppComponent.objects.create(type=element["type"], schema=element) in sentry_apps/logic.py). The CLI now narrows on schema.type === "issue-link" before it validates link with the existing LinkFormSchema.
human.ts (formatIssueDetails): firstRelease/lastRelease can be just { version }. serialize_releases in api/helpers/group_index/index.py returns that when it can't load the release. The CLI read only shortVersion, so it dropped the release from issue details. A small releaseVersion helper now falls back to version.

Tests

issue-app-links.test.ts: the new response validators check UUID formats and the issue-link schema shape. The fixtures used "install-uuid"-style IDs and a { link }-only schema, so they no longer passed. They now use real UUIDs and a full { type: "issue-link", link, create } schema. The unsupported-form case now sends a field type the CLI can't fill (checkbox), instead of a missing link that the API contract rules out.
human.details.test.ts: new case for the { version }-only release fallback.
Nothing in toolkit read invite_link, so there were no tests to update for its removal.

Generated files

packages/cli/plugins/sentry-cli/skills/sentry-cli/references/{alert,event,release}.md were regenerated by the CLI typecheck docs step from the new field descriptions. A few config fields now read unknown / object | unknown. That comes from how the generator renders the new schema unions, not from a CLI change. 1.53.0 didn't change them again.
pnpm run --filter @sentry/mcp-core generate-definitions reports the definitions are up to date. Tool definitions didn't change, so measure-tokens isn't affected.

Quality gate (local sandbox, on 1.53.0)

pnpm run tsc: passes.
pnpm run lint: passes.
Tests: mcp-core, toolkit-core, mcp-cloudflare, mcp-test-client, logger, apps/local, apps/docs-mcp and apps/games-api all pass. The CLI passes 12951 tests with 6 failures. The same 6 fail on unchanged main in this sandbox and passed in this PR's CI on 1.52.0: permission and EACCES cases in completions, upgrade lock, resilient DB and code-scanner, and a delta-upgrade patch case. @sentry/cli3to4 can't run here because its codemod binary needs GLIBC 2.35.

No UI change, so no screenshots.

The branch is still named deps/sentry-api-1.52.0, so the PR stays the same.

Please keep this trailer in the squash commit message:

Co-Authored-By: BYK 126780+BYK@users.noreply.github.com

via @BYK.

--

View Session in Sentry

1.52.0 carries the stricter getsentry/sentry response typing. Two CLI spots relied on looser types: - Sentry App component `schema` is now a union keyed on `type`, so issue-app-links narrows on `issue-link` before reading `link`. - An issue's `firstRelease`/`lastRelease` can be just `{ version }` when Sentry can't load the release, which the CLI dropped from the issue details. They now fall back to `version`. Test fixtures now use real UUIDs and a full issue-link schema, which the new response validators check. The CLI skill references are regenerated from the new field descriptions.

vercel · 2026-11-09T16:29:19Z

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

Project	Deployment	Actions	Updated
sentry-local	Ready	Preview	Nov 9, 2026 5:08pm UTC

1.53.0 adds the generated spec sync from 2026-11-09 15:53Z (83a2b744), which landed while 1.52.0 was pending. It only updates the AI conversation endpoint descriptions with their 30-day search limit. Co-Authored-By: BYK <126780+BYK@users.noreply.github.com>

Main now has #2113, which bumps @sentry/api to 1.53.0 and fixes the same two type errors this branch fixed. Conflicts resolved toward main for the bump, the release-version fallback in human.ts and its tests, and the issue-app-links fixture UUIDs. This branch's tolerant component listing and its test stay. Co-Authored-By: BYK <126780+BYK@users.noreply.github.com>

…nces After merging #2113, the link-form comment in issue-app-links.ts still said the component schema is typed per component type. The component listing on this branch leaves each app's schema unchecked, so say that. The regenerated alert reference shows `config` as `object` again. Main's copy shows `unknown` because #2113 ran the extractor before it handled `strictObject`. Co-Authored-By: BYK <126780+BYK@users.noreply.github.com>

@BYK

…2117) #2113 already moved main to `@sentry/api` 1.53.0. This PR fixes what that bump left broken. The branch started as a 1.52.0 bump and merges main, so it doesn't change any dependencies. 1.53.0 only adds docs for the 2 AI-conversation operations on top of 1.52.0. Its validators are identical once descriptions are stripped. 1.52.0 gives types to many response fields that used to be open records. It adds about 250 patterns and 140 enums, and replaces about 125 `additionalProperties: {}` objects with typed ones. I diffed every valibot schema the CLI validates responses with against 1.51.0. Two of them can reject real responses: - **Trace meta.** `transactionChildCountMap[].transaction.event_id` is now a required string. Sentry returns null there for spans that belong to no transaction (#494). With 1.52.0 or later, `getTraceMeta` throws on those traces, and `replay view` drops their counts. The CLI now accepts null. The spec is wrong here, see getsentry/sentry#130461. - **Sentry App components.** `schema` is now the UI element union that Sentry checks apps against when they're saved. Main still validates every component against it. One installed app whose stored schema doesn't match it would fail the whole listing and block linking through every app. The CLI now leaves `schema` unchecked and still validates the selected app's link form with `LinkFormSchema`. The output-schema field extractor now recognizes `strictObject`, which 1.52.0 emits for closed objects. Alert `config` shows as `object` again in the skill reference instead of `unknown`. Monitor `config` still has no description, because the generated validators drop the description on `anyOf` unions (getsentry/sentry-api-schema#139). I checked the other changes against the Sentry serializers: - The integration `status` enum and the typed `aspects` match every provider. - Timeseries `groupBy.value` only got looser. - The replay segment, external issue and installation schemas didn't change. - Toolkit doesn't use the removed `targetSampleRate`, `samplingMode` and `invite_link` fields. Testing: `tsc` and `lint` pass on the merged branch. CLI `test:unit` passes except for the 5 known file-permission tests (EACCES/EPERM). Before the merge, the full `pnpm run test`, `measure-tokens` and CLI `ci:policy` also passed, except for those tests and the codemod test, which needs glibc 2.35. New tests cover a null trace-meta id, a non-conforming component from another app, and strict objects in the field extractor.  via @BYK.    -- [View Session in Sentry](https://sentry.sentry.io/explore/conversations/agent%3A9671a009327aa256e6910769b597562b/?project=4510944073809921)  --------- Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com> Co-authored-by: BYK <126780+BYK@users.noreply.github.com>

vercel Bot deployed to Preview November 9, 2026 16:29

View deployment

sentry-junior Bot assigned BYK Nov 9, 2026

sentry-junior Bot changed the title ~~chore(deps): Bump @sentry/api to 1.52.0~~ chore(deps): Bump @sentry/api to 1.53.0 Nov 9, 2026

vercel Bot deployed to Preview November 9, 2026 17:08

View deployment

BYK approved these changes Nov 9, 2026

View reviewed changes

BYK merged commit 32481e4 into main Nov 9, 2026
60 of 62 checks passed

BYK deleted the deps/sentry-api-1.52.0 branch November 9, 2026 17:33

sentry-junior Bot mentioned this pull request Nov 9, 2026

fix(cli): Keep response validation working with @sentry/api 1.53.0 #2117

Merged

Navigation Menu

Repository navigation

chore(deps): Bump @sentry/api to 1.53.0 - #2113

chore(deps): Bump @sentry/api to 1.53.0#2113
BYK merged 2 commits into
mainfrom
deps/sentry-api-1.52.0

sentry-junior Bot commented Nov 9, 2026 •

edited

Loading

Uh oh!

vercel Bot commented Nov 9, 2026 •

edited

Loading

Uh oh!

Uh oh!

This branch was successfully deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

sentry-junior Bot commented Nov 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What broke

Tests

Generated files

Quality gate (local sandbox, on 1.53.0)

Uh oh!

vercel Bot commented Nov 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

This branch was successfully deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

sentry-junior Bot commented Nov 9, 2026 •

edited

Loading

vercel Bot commented Nov 9, 2026 •

edited

Loading