[dependabot]

Bumps @sentry/node from 10.76.2 to 11.9.0.

Release notes

Sourced from @​sentry/node's releases.

11.9.0

Important Changes

• feat: Rename diagnostic_channel, fetch and gRPC span origins (#25601)

  Some span origins changed their names to match the other v11 origins:

  • auto.graphql.diagnostic_channel is now auto.graphql.graphql.
  • auto.db.redis.diagnostic_channel, auto.db.mysql2.diagnostic_channel and auto.db.mongoose.diagnostic_channel now end in .native_channel.
  • auto.http.wintercg_fetch is now auto.http.fetch, as on Bun, Deno and Cloudflare.
  • auto.grpc.serverless is now auto.grpc.google_cloud.

  If you have ignoreSpans rules, queries or alerts on the old origins, change them to use the new origins.

• feat(deno): Add incoming request options to denoServeIntegration (#25493)

  denoServeIntegration now accepts ignoreRequestBody, ignoreIncomingRequests, ignoreStaticAssets, spans, onSpanCreated and onSpanEnd, with the same meaning as in denoHttpIntegration. The callbacks receive the web Request.

  ignoreStaticAssets defaults to true, so Deno.serve no longer creates spans for GET requests to common static assets such as favicon.ico, robots.txt or *.js files. To keep these spans, set denoServeIntegration({ ignoreStaticAssets: false }). Deno.serve spans also follow the client's tracing configuration by default, so the integration does not start spans when tracing is disabled.

• feat(deno): Record request sessions for Deno.serve (#25496)

  denoServeIntegration now records a request session for each incoming request, as denoHttpIntegration does for node:http. This gives release health and crash-free rates for Deno.serve apps. Sessions are sent only when a release is set. To turn them off, set denoServeIntegration({ sessions: false }). sessionFlushingDelayMS sets how long the SDK waits before it sends the session aggregate.

• feat(deno): Register channel injection hooks from init() (#25546)

  Sentry.init() in @sentry/deno now registers the diagnostics-channel injection hooks, as @sentry/node does. The channel integrations now record spans without --preload=npm:@sentry/deno/import, for modules that you import after init(). To also instrument modules that load before init(), such as static imports in your entry module, keep the preload. With debug: true, the SDK logs a warning when no injection is active.

  On Node.js, tracing-hooks messages now show with debug: true instead of with DEBUG=@apm-js-collab/*.

• feat(nextjs): Add a tunnel route handler that sends only the event payload to Sentry (#25456)

  The tunnelRoute option can now send events through a route handler in your app. The handler forwards only the event payload to Sentry, and no request headers. To use it, add this file next to your tunnelRoute option:

  // app/sentry-tunnel/route.ts (or src/app/sentry-tunnel/route.ts)
  export { POST } from '@sentry/nextjs/tunnel';

  The handler accepts events for the DSN of your server SDK. To accept other DSNs, use createSentryTunnelRoute({ allowedDsns }) from the same import. Without the file, the tunnel route works as before.

  Also, the server no longer sends spans of tunnel requests when span streaming is on, because these spans only show the SDK's own traffic.

• feat(nextjs): Never emit trace meta tags from a prerender (#25141)

  Pageloads of apps with cacheComponents enabled are connected to their server request again. Pages that Next.js prerenders no longer carry trace information, so a cached page can no longer connect visitors to a request that was not theirs. This also applies to ISR pages. The pageload waits for the trace information when it arrives with the part of the page that streams in after a cached shell.

  If you set up OpenTelemetry yourself and register SentryPropagator, register NextSentryPropagator instead and pass your tracer provider to markPrerendersOnTracerProvider, so that your prerendered pages carry no trace information either.

• feat(nextjs): Send tunnel route requests with credentials: 'omit' (#25509)

... (truncated)

Changelog

Sourced from @​sentry/node's changelog.

11.9.0

Important Changes

• feat: Rename diagnostic_channel, fetch and gRPC span origins (#25601)

  Some span origins changed their names to match the other v11 origins:

  • auto.graphql.diagnostic_channel is now auto.graphql.graphql.
  • auto.db.redis.diagnostic_channel, auto.db.mysql2.diagnostic_channel and auto.db.mongoose.diagnostic_channel now end in .native_channel.
  • auto.http.wintercg_fetch is now auto.http.fetch, as on Bun, Deno and Cloudflare.
  • auto.grpc.serverless is now auto.grpc.google_cloud.

  If you have ignoreSpans rules, queries or alerts on the old origins, change them to use the new origins.

• feat(deno): Add incoming request options to denoServeIntegration (#25493)

  denoServeIntegration now accepts ignoreRequestBody, ignoreIncomingRequests, ignoreStaticAssets, spans, onSpanCreated and onSpanEnd, with the same meaning as in denoHttpIntegration. The callbacks receive the web Request.

  ignoreStaticAssets defaults to true, so Deno.serve no longer creates spans for GET requests to common static assets such as favicon.ico, robots.txt or *.js files. To keep these spans, set denoServeIntegration({ ignoreStaticAssets: false }). Deno.serve spans also follow the client's tracing configuration by default, so the integration does not start spans when tracing is disabled.

• feat(deno): Record request sessions for Deno.serve (#25496)

  denoServeIntegration now records a request session for each incoming request, as denoHttpIntegration does for node:http. This gives release health and crash-free rates for Deno.serve apps. Sessions are sent only when a release is set. To turn them off, set denoServeIntegration({ sessions: false }). sessionFlushingDelayMS sets how long the SDK waits before it sends the session aggregate.

• feat(deno): Register channel injection hooks from init() (#25546)

  Sentry.init() in @sentry/deno now registers the diagnostics-channel injection hooks, as @sentry/node does. The channel integrations now record spans without --preload=npm:@sentry/deno/import, for modules that you import after init(). To also instrument modules that load before init(), such as static imports in your entry module, keep the preload. With debug: true, the SDK logs a warning when no injection is active.

  On Node.js, tracing-hooks messages now show with debug: true instead of with DEBUG=@apm-js-collab/*.

• feat(nextjs): Add a tunnel route handler that sends only the event payload to Sentry (#25456)

  The tunnelRoute option can now send events through a route handler in your app. The handler forwards only the event payload to Sentry, and no request headers. To use it, add this file next to your tunnelRoute option:

  // app/sentry-tunnel/route.ts (or src/app/sentry-tunnel/route.ts)
  export { POST } from '@sentry/nextjs/tunnel';

  The handler accepts events for the DSN of your server SDK. To accept other DSNs, use createSentryTunnelRoute({ allowedDsns }) from the same import. Without the file, the tunnel route works as before.

  Also, the server no longer sends spans of tunnel requests when span streaming is on, because these spans only show the SDK's own traffic.

• feat(nextjs): Never emit trace meta tags from a prerender (#25141)

  Pageloads of apps with cacheComponents enabled are connected to their server request again. Pages that Next.js prerenders no longer carry trace information, so a cached page can no longer connect visitors to a request that was not theirs. This also applies to ISR pages. The pageload waits for the trace information when it arrives with the part of the page that streams in after a cached shell.

  If you set up OpenTelemetry yourself and register SentryPropagator, register NextSentryPropagator instead and pass your tracer provider to markPrerendersOnTracerProvider, so that your prerendered pages carry no trace information either.

• feat(nextjs): Send tunnel route requests with credentials: 'omit' (#25509)

... (truncated)

Commits

• 7b8ce4f meta(changelog): Add cherry-picked PRs to 11.9.0 changelog
• 487097d ci: Stop uploading duplicate tarballs to the release artifact (#25688)
• 1276d41 fix(deps): Allow @opentelemetry/api 1.9 again (#25684)
• c74f77f test(nextjs): Bump nextjs-16 E2E app to Next.js 16.4.2 (#25686)
• 47dec2a release: 11.9.0
• cc40f95 Merge pull request #25628 from getsentry/prepare-release/11.9.0
• 4689484 meta(changelog): Update changelog for 11.9.0
• b94aeb0 fix(hono): Read connection info from the runtime instead of Hono helpers (#25...
• ded8524 test(e2e): Retry tests in all dev-mode variants (#25640)
• 24186f0 feat: Rename diagnostic_channel, fetch and gRPC span origins (#25601)
• Additional commits viewable in compare view

[greptile-apps]

PR author is in the excluded authors list.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Repository UI (base), Organization UI (inherited)
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: c7aed34a-81e2-44aa-b704-7c71776aee38

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

[codspeed]

Merging this PR will not alter performance

1 warning

⚠️ 1 benchmark is dominated by system calls

System calls cannot be simulated consistently and are left out of the measure. The reported value understates the real cost. Switch to the Walltime instrument to measure them.

Learn more about system calls

See affected benchmarks

✅ 11 untouched benchmarks

---

_{Comparing dependabot/npm_and_yarn/sentry/node-11.9.0 (e3ba7a1) with main (8b5bae1)}

[unbraind]

Tracked by pm-t3jxjj, closed as #1403, #1448, #1503 and #1600 were. Release 11.9.0 is past the age floor, but this branch fails the TypeScript build with TS2353 at src/core/sentry/instrument.ts:490 because enableLogs is not in NodeOptions. It also still pulls @sentry/bundler-plugins, @sentry/server-runtime-injection and @sentry/server-utils, the footprint pm-t3jxjj records against the runtime bundle budget. Sentry 11 is adopted through that item's migration, not as a version bump.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.