[sentry-junior]

When VERCEL is set, v10's @sentry/node-core/light init() adds a SIGTERM flush listener on every init and never removes it. Library-mode commands (createSentrySDK) call initSentry() per command, so in-process callers like @sentry/bundler-plugins hit MaxListenersExceededWarning during Vercel builds. v11 registers that listener once (getsentry/sentry-javascript#25146), and the rest of toolkit is already on v11, so the CLI now uses the workspace catalog @sentry/core and @sentry/node (11.6.0). The local @sentry/node-core and @sentry/core patches are gone.

SDK defaults. The CLI now uses v11 defaults rather than recreating v10 behavior:

• CLI mode uses Sentry.init() defaults, including dataCollection and attachStacktrace. The bundle didn't grow, because the bundled MCP code already pulled in v11's integrations.
• The SDK's Http/NodeFetch integrations now create the http.client spans and inject sentry-trace/baggage. The CLI's own HTTP spans and manual header injection existed only because Bun's fetch didn't fire undici diagnostics channels, and the CLI now runs on Node. Response-cache hits are no longer wrapped in an http.client span, so span.op:http.client counts only requests that went out. Cache telemetry is unchanged: the response cache still emits cache.get/cache.put spans and the cache.hit_rate metric. Retries now show one span per attempt.
• Library mode uses getDefaultIntegrationsWithoutPerformance() and leaves out integrations that hook the host process or its diagnostics channels (process handlers, HTTP/fetch, child process, worker threads, framework error handlers). Without those integrations, and on Bun (whose fetch doesn't fire undici diagnostics channels), the API client still creates its own http.client span and adds sentry-trace/baggage, so in-process callers keep request tracing.
• Runtime channel injection is stripped at build time with the SDK's __SENTRY_CHANNEL_INJECTION__ define, which is what the bundler plugins' excludeChannelInjection sets. That makes index.cjs ~72 KB smaller. enableRuntimeChannelInjection: false stays so unbundled dev and test runs behave the same.
• unknown_command and invalid_argument are sent with captureEvent instead of captureMessage. With attachStacktrace on, captureMessage adds a synthetic exception, which marks the session errored.

Kept on purpose:

• traceLifecycle: "static", because dashboards rely on scope tags on transactions and beforeSendTransaction scrubs server_name; both are dropped under v11's default span streaming. Moving to streamed spans should be its own change.
• v11 removed enableLogs, so library mode drops logs via beforeSendLog instead.

Two v11 issues fixed here:

• v11 attaches the client to the current scope before switching to the AsyncLocalStorage context strategy. When initSentry() runs inside a still-pending pre-init span, as it does in the CLI's middleware chain, the client is lost, so commands like sentry org list sent no telemetry at all. initSentry() now re-binds the client after init.
• attachSentryReporter() used a runtime require() that the bundler leaves unresolved, so shipped builds either failed it silently or, in library mode, could load the host app's @sentry/node. It's now a static import, which means shipped builds now forward consola logs, which they never did on v10.

Repeated initSentry() calls with VERCEL=1 keep one SIGTERM listener.

Fixes #1692

--

View Junior Session [Sentry]

[vercel]

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

Project	Deployment	Actions	Updated
sentry-local	Ready	Preview	Oct 28, 2026 9:02pm UTC

[BYK]

Actually, maybe we should just patch the Sentry Node SDK and then submit a bug and a PR to it instead?

[BYK]

Wait, why are we not on v11 of the SDK? Does it also have the same problem?

[cursor]

Stale Bugbot comment from a previous run.

[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 99eb7f4. Configure here.}

[BYK]

Looks good but please address my earlier comments.

Also, we have some merge conflicts that needs to be resolved.

[sentry-warden]

Tracing tests read the operation from nonexistent SpanJSON.attributes

spanToJSON() exposes the operation as top-level op and span attributes under data, so tracedRequest() records undefined and both tracing tests fail. This breaks the CLI unit-test run.

Evidence

• @sentry/core v11's SpanJSON shape uses top-level op and data; it has no attributes property.
• tracedRequest() reads spanToJSON(span).attributes?.[SEMANTIC_ATTRIBUTE_SENTRY_OP], which evaluates to undefined even when a span is active.
• The library-mode and CLI-mode tests assert activeSpanOp is "http.client" and "test"; the package's test:unit script runs test/lib, so these assertions fail in that run.

_{Identified by Warden · code-review · ARY-TQS}