[sentry-junior]

Next step after #2073 and #2075, which moved the CLI onto the generated @sentry/api operations. @sentry/api 1.46.0 includes the API docs fixes from getsentry/sentry#130348, #130349 and #130350, so six more call sites now match their generated operation. This PR bumps the package and moves them.

Moved onto generated operations

Command(s)	Call	Operation	Unblocked by
issue resolve/unresolve/archive, feedback resolve/spam/… (org-scoped)	updateIssueStatus	updateOrganizationIssue	sentry#130348 (body fields no longer all required)
issue merge	mergeIssues	updateOrganizationIssues with numeric ids and {merge: true}	sentry#130348
dashboard view chart widgets	queryWidgetTimeseries	listOrganizationEventsTimeseries	sentry#130349 (yAxis array, interval int or duration)
explore time series	queryEventsTimeSeries	listOrganizationEventsTimeseries	sentry#130349
agent-conversation list	listConversations	listOrganizationAiConversations with sort	sentry#130350
trace view, span view, log view	getDetailedTrace	getOrganizationTrace with timestamp	sentry#130349

Trace meta already used getOrganizationTraceMeta and doesn't send timestamp, so nothing changes there.

Behavior notes

• Responses are validated exactly as before: EventsTimeseriesResponseSchema for widgets and ConversationListItemSchema for conversations. The explore time series and trace detail responses were not validated before and still aren't.
• issue merge still turns a 204 (no matching issues) into the same friendly error, and still clears each affected issue's cross-origin cache.
• agent-conversation list --sort is now typed with the endpoint's sort enum. The command's sort values are a subset of it.
• Errors on the moved calls use the SDK wording, as in ref(cli): Move API calls with generated operations onto @sentry/api #2073 and fix(cli): Send the API params the endpoints accept #2075, e.g. Failed to update issue: 403 Forbidden. Status codes and the 401/403 enrichment are unchanged.
• The 1.46.0 regen also changes uniqueValues/key/name descriptions in the generated issue skill reference, which is committed here. Typecheck is otherwise unaffected.

Remaining apiRequest* call sites and raw fetches

Details for each are in getsentry/sentry#130351.

Not in the public schema (needs a getsentry/sentry API docs decision):

• organizations.ts:66, projects.ts:576/591: region lookups
• users.ts:21: current user
• trials.ts:30/70: trials list/start
• org-auth-tokens.ts:77: delete org auth token
• dashboards.ts:201/235: dashboard revisions/restore
• issues.ts:329: unscoped GET /issues/{id}/
• issues.ts:632: legacy unscoped PUT /issues/{id}/
• logs.ts:486: logs query
• traces.ts:225: trace-items detail (experimental)
• releases.ts:425: release set-commits
• preprod-artifacts.ts:283/449: build/snapshot upload
• Raw fetches: getSharedIssue (issues.ts) and openSnapshotArchive (preprod-artifacts.ts)

Dynamic request identity / transport:

• auth.ts:17
• org-auth-tokens.ts:37/59
• preprod-artifacts.ts:508/526: snapshot downloads

Kept on purpose:

• replays.ts:201: replay list keeps requesting info_ids/warning_ids because --json prints them (see fix(cli): Send the API params the endpoints accept #2075).

The Oxlint rule that bans the helpers comes last, after these are resolved.

Verification

• pnpm install --frozen-lockfile passes with the committed lockfile.
• pnpm run tsc and pnpm run lint pass.
• CLI tests: 12919 pass and 5 fail. All 5 are the sandbox-only permission tests that also fail on main (completions ×2, upgrade acquireLock, db/resilient readonly, dsn/code-scanner).
• The dashboard time series tests now mock listOrganizationEventsTimeseries. I added an org-scoped updateIssueStatus test. The conversation, explore and trace tests run at the fetch layer and pass unchanged.
• API discovery no longer lists the moved call sites.

via @BYK.

--

View Session [Sentry]

[vercel]

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

Project	Deployment	Actions	Updated
sentry-local	Ready	Preview	Nov 7, 2026 2:27am UTC