Repository navigation
ref(cli): Bump @sentry/api to 1.59.0 and use dsn-lookup, user details and trace item operations - #2132
Merged
Conversation
… and trace item operations Bump @sentry/api from 1.55.0 to 1.59.0. Three CLI calls move from apiRequestToRegion to the generated operations: - DSN lookup uses resolveOrganizationDsn. The self-hosted /projects/?query=dsn: fallback stays. - getCurrentUser reads GET /users/me/ with retrieveUserDetails. On a 403, which servers older than getsentry/sentry#130368 return for every bearer token, it falls back to /auth/. - Span and log item details use retrieveProjectTraceItem, which Sentry publishes as experimental. The skill references are regenerated from the new schema descriptions. Co-Authored-By: BYK <126780+BYK@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
BYK
approved these changes
Nov 9, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps
@sentry/apifrom 1.55.0 to 1.59.0, the newest version on npm. Three CLI calls move fromapiRequestToRegiononto the generated operations. The endpoints they use were published in getsentry/sentry#130367, #130368 and #130373.What moved
projects.ts) now usesresolveOrganizationDsn. A 404 still means "not here" when its detail isDSN not found/Invalid DSN, and "this server can't look up DSNs" otherwise. The self-hosted/projects/?query=dsn:fallback stays, and it still never runs on SaaS.users.ts) now readsGET /users/me/withretrieveUserDetails. Servers older than feat(apidocs): Publish user details GET with token access sentry#130368 return 403 there for every bearer token, so on a 403 it falls back to/auth/, which returns the same body. Other errors still throw.traces.ts, used byspan viewandlog view) now useretrieveProjectTraceItem. The operation is markedexperimentalin the@sentry/api/operationscatalog.The CLI keeps its valibot schemas (
DsnLookupResponseSchema,SentryUserSchema,TraceItemDetailSchema) on top of the generated calls, so responses are validated the same way as before.Behavior change worth a look
A network failure during DSN lookup now comes back as the SDK's
ApiError(status 0, with the original error ascause), like every other migrated call. Before, the raw error came through. The best-effort lookup still reports it and moves on to the next org.api-client.multiregion.test.tsasserts the new shape.Other changes
pnpm install --frozen-lockfilepasses.@sentry/api's dependencies and peers are the same as in 1.55.0.alert.mdandevent.mdunderskills/sentry-cli/referencesare regenerated from the 1.59.0 schema descriptions./auth/as the user source now name/users/me/.Not in this PR
The leftover helpers and the no-allowlist Oxlint rule come separately. The raw calls left are the agreed exceptions:
/customers/*and the product-trial PUT, snapshotupload-optionsand archive?download, the replay list, the self-hosted/projects/?query=dsn:fallback, and now the/auth/fallback.Testing
pnpm run tsc: passes.pnpm run lint: 0 warnings, 0 errors.db/resilientanddsn/code-scanner.@sentry/cli3to4can't run there, because it needs GLIBC 2.35.getCurrentUsertests cover/users/me/success, the 403 fallback to/auth/, and no fallback on 401.via @BYK.
--
View Session [Sentry]