Important Changes

• feat(node): Instrument cloud functions for firebase v2 (#17952)

  We added instrumentation for Cloud Functions for Firebase v2, enabling automatic performance tracking and error monitoring. This will be added automatically if you have enabled tracing.

• feat(core): Instrument LangChain AI (#17955)

  Instrumentation was added for LangChain AI operations. You can configure what is recorded like this:

  Sentry.init({
   integrations: [
   Sentry.langChainIntegration({
   recordInputs: true, // Record prompts/messages
   recordOutputs: true, // Record responses
   }),
   ],
  });

Other Changes

• feat(cloudflare,vercel-edge): Add support for LangChain instrumentation (#17986)
• feat: Align sentry origin with documentation (#17998)
• feat(core): Truncate request messages in AI integrations (#17921)
• feat(nextjs): Support node runtime on proxy files (#17995)
• feat(node): Pass requestHook and responseHook option to OTel (#17996)
• fix(core): Fix wrong async types when instrumenting anthropic's stream api (#18007)
• fix(nextjs): Remove usage of chalk to avoid runtime errors (#18010)
• fix(node): Pino capture serialized err (#17999)
• fix(node): Pino child loggers (#17934)
• fix(react): Don't trim index route / when getting pathname (#17985)
• fix(react): Patch spanEnd for potentially cancelled lazy-route transactions (#17962)

Bundle size 📦

Important Changes

• feat(browserProfiling): Add trace lifecycle mode for UI profiling (#17619)

  Adds a new trace lifecycle mode for UI profiling, allowing profiles to be captured for the duration of a trace. A manual mode will be added in a future release.

• feat(nuxt): Instrument Database (#17899)

  Adds instrumentation for Nuxt database operations, enabling better performance tracking of database queries.

• feat(nuxt): Instrument server cache API (#17886)

  Adds instrumentation for Nuxt's server cache API, providing visibility into cache operations.

• feat(nuxt): Instrument storage API (#17858)

  Adds instrumentation for Nuxt's storage API, enabling tracking of storage operations.

Other Changes

• feat(browser): Add onRequestSpanEnd hook to browser tracing integration (#17884)
• feat(nextjs): Support Next.js proxy files (#17926)
• feat(replay): Record outcome when event buffer size exceeded (#17946)
• fix(cloudflare): copy execution context in durable objects and handlers (#17786)
• fix(core): Fix and add missing cache attributes in Vercel AI (#17982)
• fix(core): Improve uuid performance (#17938)
• fix(ember): Use updated version for clean-css (#17979)
• fix(nextjs): Don't set experimental instrumentation hook flag for next 16 (#17978)
• fix(nextjs): Inconsistent transaction naming for i18n routing (#17927)
• fix(nextjs): Update bundler detection (#17976)

Work in this release was contributed by @0xbad0c0d3. Thank you for your contribution!

Bundle size 📦

Contributors

• @0xbad0c0d3

This release is a preview release for sending spans in browser via spanV2 instead of transaction event envelopes. All of this is experimental and subject to change. Use at your own risk. More Details.

• export withStreamSpan from @sentry/browser

Bundle size 📦

This release is a preview release for sending spans in browser via spanV2 instead of transaction event envelopes. All of this is experimental and subject to change. Use at your own risk. More Details.

Bundle size 📦

Important Changes

• feat(flags): Add Growthbook integration (#17440)

  Adds a new Growthbook integration for feature flag support.

• feat(solid): Add support for TanStack Router Solid (#17735)

  Adds support for TanStack Router in the Solid SDK, enabling better routing instrumentation for Solid applications.

• feat(nextjs): Support native debugIds in turbopack (#17853)

  Adds support for native Debug IDs in Turbopack, improving source map resolution and error tracking for Next.js applications using Turbopack. Native Debug ID generation will be enabled automatically for compatible versions.

Other Changes

• feat(nextjs): Prepare for next 16 bundler default (#17868)
• feat(node): Capture pino logger name (#17930)
• fix(browser): Ignore React 19.2+ component render measure entries (#17905)
• fix(nextjs): Fix createRouteManifest with basePath (#17838)
• fix(react): Add POP guard for long-running pageload spans (#17867)
• fix(tracemetrics): Send boolean for internal replay attribute (#17908)
• ref(core): Add weight tracking logic to browser logs/metrics (#17901)

Work in this release was contributed by @seoyeon9888, @madhuchavva and @thedanchez . Thank you for your contributions!

Bundle size 📦

Contributors

• @thedanchez
• @madhuchavva
• @seoyeon9888

• feat(tracemetrics): Add trace metrics behind an experiments flag (#17883)

Bundle size 📦

Important Changes

• feat(node): pino integration (#17584)

  This release adds a new pino integration for Node.js, enabling Sentry to capture logs from the Pino logging library.

• feat: Remove @sentry/pino-transport package (#17851)

  The @sentry/pino-transport package has been removed. Please use the new pino integration in @sentry/node instead.

• feat(node-core): Extend onnhandledrejection with ignore errors option (#17736)

  Added support for selectively suppressing specific errors with configurable logging control in onnhandledrejection integration.

Other Changes

• feat(core): Rename vercelai.schema to gen_ai.request.schema (#17850)
• feat(core): Support stream responses and tool calls for Google GenAI (#17664)
• feat(nextjs): Attach headers using client hook (#17831)
• fix(core): Keep all property values in baggage header (#17847)
• fix(nestjs): Add support for Symbol as event name (#17785)
• fix(nuxt): include sentry.client.config.ts in nuxt app types (#17830)
• fix(react-router): Fix type for OriginalHandleRequest with middleware (#17870)

Work in this release was contributed by @stefanvanderwolf. Thank you for your contribution!

Bundle size 📦

Contributors

• @stefanvanderwolf

Important Changes

• feat(nuxt): Implement server middleware instrumentation (#17796)

  This release introduces instrumentation for Nuxt middleware, ensuring that all middleware handlers are automatically wrapped with tracing and error reporting functionality.

• fix(aws-serverless): Take http_proxy into account when choosing
  useLayerExtension default (#17817)

  The default setting for useLayerExtension now considers the http_proxy environment variable.
  When http_proxy is set, useLayerExtension will be off by default.
  If you use a http_proxy but would still like to make use of the Sentry Lambda extension, exempt localhost in a no_proxy environment variable.

Other Changes

• feat(node): Split up http integration into composable parts (#17524)
• fix(core): Remove check and always respect ai.telemetry.functionId for Vercel AI gen spans (#17811)
• doc(core): Fix outdated JSDoc in beforeSendSpan (#17815)

Bundle size 📦

• feat(logs): Add internal replay_is_buffering flag (#17752)
• feat(react-router): Update loadContext type to be compatible with middleware (#17758)
• feat(replay/logs): Only attach sampled replay Ids to logs (#17750)
• fix(browser): Use current start timestamp for CLS span when CLS is 0 (#17800)
• fix(core): Prevent instrumentAnthropicAiClient breaking MessageStream api (#17754)
• fix(nextjs): Don't use chalk in turbopack config file (#17806)
• fix(react): Do not send additional navigation span on pageload (#17799)

Important Changes

• feat(cloudflare): Add honoIntegration with error-filtering function (#17743)

  This release adds a honoIntegration to @sentry/cloudflare, which exposes a shouldHandleError function that lets you define which errors in onError should be captured.
  By default, Sentry captures exceptions with error.status >= 500 || error.status <= 299.

  The integration is added by default, and it's possible to modify this behavior like this:

   integrations: [
   honoIntegration({
   shouldHandleError: (err) => true; // always capture exceptions in onError
   })
   ]

• feat(node): Add instrumentation for hono handler (#17428)

This PR enhances the Hono integration by adding comprehensive handler instrumentation, error handling capabilities.

• feat(aws): Enable Lambda extension by default when using the Lamba layer (#17684)

• feat(browser): Add setActiveSpanInBrowser to set an active span in the browser (#17714)

This PR adds a feature to the browser SDKs only: Making an inactive span active. We do this to enable use cases where having a span only being active in the callback is not practical.

Other Changes

• fix(browser): Improve handling of 0 and undefined resource timing values (#17751)
• ref(nextjs): Display build compatibility warning for webpack (#17746)

Work in this release was contributed by @Karibash. Thank you for your contribution!

Bundle size 📦

Contributors

• @Karibash