@sentry/node-core

Important Changes

• effect: Add @sentry/effect SDK (Alpha)

  This release introduces @sentry/effect, a new SDK for Effect.ts applications. The SDK provides Sentry integration via composable Effect layers for both Node.js and browser environments.

  Compose the effectLayer with optional tracing, logging, and metrics layers to instrument your Effect application:

  import * as Sentry from '@sentry/effect';
  import * as Layer from 'effect/Layer';
  import * as Logger from 'effect/Logger';
  
  const SentryLive = Layer.mergeAll(
    Sentry.effectLayer({ dsn: '__DSN__', tracesSampleRate: 1.0, enableLogs: true }),
    Layer.setTracer(Sentry.SentryEffectTracer),
    Logger.replace(Logger.defaultLogger, Sentry.SentryEffectLogger),
    Sentry.SentryEffectMetricsLayer,
  );

  Alpha features are still in progress, may have bugs and might include breaking changes. Please reach out on GitHub if you have any feedback or concerns.

• astro: Add Astro 6 support

  This release enables full support for Astro v6 by adjusting our Astro SDK's middleware to some Astro-internal
  changes. We cannot yet guarantee full support for server-islands, due to a bug in Astro v6
  but we'll follow up on this once the bug is fixed.

• hono: Add basic instrumentation for Node runtime

  Adds a new package @sentry/hono/node (alpha) with basic instrumentation for Hono applications running in Node.js.
  The Hono middleware for Cloudflare (@sentry/hono/cloudflare - alpha) comes with fixes, and it's now possible to access the Cloudflare Worker Bindings (env) from the options' callback.

  Start using the new Hono middlewares by installing @sentry/hono and importing the respective middleware for your runtime.
  More instructions can be found in the Hono readme.

  Alpha features are still in progress, may have bugs and might include breaking changes. Please reach out on GitHub if you have any feedback or concerns.

• nestjs: Instrument @nestjs/bullmq @Processor decorator

  Automatically capture exceptions and create transactions for BullMQ queue processors in NestJS applications.

  When using the @Processor decorator from @nestjs/bullmq, the SDK now automatically wraps the process() method
  to create queue.process transactions with proper isolation scopes, preventing breadcrumb and scope leakage between
  jobs and HTTP requests. Errors thrown in processors are captured with the auto.queue.nestjs.bullmq mechanism type.

  Requires @nestjs/bullmq v10.0.0 or later.

• nestjs: Instrument @nestjs/schedule decorators

  Automatically capture exceptions thrown in @Cron, @Interval, and @Timeout decorated methods.

  Previously, exceptions in @Cron methods were only captured if you used the SentryCron decorator. Now they are
  captured automatically. The exception mechanism type changed from auto.cron.nestjs.async to
  auto.function.nestjs.cron. If you have Sentry queries or alerts that filter on the old mechanism type, update them
  accordingly.

• node: Expose headersToSpanAttributes option on nativeNodeFetchIntegration()

  Response headers like http.response.header.content-length were previously captured automatically on outgoing
  fetch spans but are now opt-in since @opentelemetry/instrumentation-undici@0.22.0. You can now configure which
  headers to capture via the headersToSpanAttributes option.

  Sentry.init({
    integrations: [
      Sentry.nativeNodeFetchIntegration({
        headersToSpanAttributes: {
          requestHeaders: ['x-custom-header'],
          responseHeaders: ['content-length', 'content-type'],
        },
      }),
    ],
  });

Other Changes

• browser/cloudflare: Export conversation id from browser and cloudflare runtimes

• bun: Set http response header attributes instead of response context headers

• core: Add sentry.timestamp.sequence attribute for timestamp tie-breaking

• deno: Set http response header attributes instead of response context headers

• nestjs: Use more specific span origins for NestJS guards, pipes, interceptors, and exception filters

• nextjs: Vercel queue instrumentation

• node: Avoid OTEL instrumentation for outgoing requests on Node 22+

• browser: Skip browserTracingIntegration setup for bot user agents

• cloudflare: Recreate client when previous one was disposed

• core: Align Vercel embedding spans with semantic conventions

• core: Fallback to sendDefaultPii setting in langchain and langgraph in non-node environments

• core: Improve Vercel AI SDK instrumentation attributes

• hono: Align error mechanism

• hono: Allow passing env and fix type issues

• nestjs: Fork isolation scope in @nestjs/event-emitter instrumentation

• nextjs: Log correct lastEventId when error is thrown in component render

• nextjs: Strip sourceMappingURL comments after deleting source maps in turbopack builds

• nuxt: Upload client source maps

• profiling-node: Fix NODE_VERSION rendered as [object Object] in warning

Internal Changes