chore(deps): update JavaScript SDK to v9.19.0

[github-actions]

Bumps scripts/update-javascript.sh from 8.54.0 to 9.19.0.

Auto-generated by a dependency updater.

Changelog

9.19.0

• feat(react-router): Add otel instrumentation for server requests (#16147)
• feat(remix): Vendor in opentelemetry-instrumentation-remix (#16145)
• fix(browser): Ensure spans auto-ended for navigations have cancelled reason (#16277)
• fix(node): Pin fastify/otel fork to direct url to allow installing without git (#16287)
• fix(react): Handle nested parameterized routes in reactrouterv3 transaction normalization (#16274)

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

9.18.0

Important changes

• feat: Support Node 24 (#16236)

We now also publish profiling binaries for Node 24.

Other changes

• deps(node): Bump import-in-the-middle to 1.13.1 (#16260)
• feat: Export consoleLoggingIntegration from vercel edge sdk (#16228)
• feat(cloudflare): Add support for email, queue, and tail handler (#16233)
• feat(cloudflare): Improve http span data (#16232)
• feat(nextjs): Add more attributes for generation functions (#16214)
• feat(opentelemetry): Widen peer dependencies to support Otel v2 (#16246)
• fix(core): Gracefully handle invalid baggage entries (#16257)
• fix(node): Ensure traces are propagated without spans in Node 22+ (#16221)
• fix(node): Use sentry forked fastify/otel dependency with pinned Otel v1 deps (#16256)
• fix(remix): Remove vendored types (#16218)

9.17.0

• feat(node): Migrate to fastify/otel (#15542)

9.16.1

• fix(core): Make sure logs get flushed in server-runtime-client (#16222)
• ref(node): Remove vercel flushing code that does nothing (#16217)

9.16.0

Important changes

• feat: Create a Vite plugin that injects sentryConfig into the global config (#16197)

Add a new plugin makeConfigInjectorPlugin within our existing vite plugin that updates the global vite config with sentry options

• feat(browser): Add option to sample linked traces consistently (#16037)

This PR implements consistent sampling across traces as outlined in (#15754)

• feat(cloudflare): Add support for durable objects (#16180)

This PR introduces a new instrumentDurableObjectWithSentry method to the SDK, which instruments durable objects. We capture both traces and errors automatically.

• feat(node): Add Prisma integration by default (#16073)

Prisma integration is enabled by default, it should work for both ESM and CJS.

• feat(react-router): Add client-side router instrumentation (#16185)

Adds client-side instrumentation for react router's HydratedRouter. To enable it, simply replace browserTracingIntegration() with reactRouterTracingIntegration() in your client-side init call.

• fix(node): Avoid double-wrapping http module (#16177)

When running your application in ESM mode, there have been scenarios that resulted in the http/https emitting duplicate spans for incoming requests. This was apparently caused by us double-wrapping the modules for incoming request isolation.

In order to solve this problem, the modules are no longer monkey patched by us for request isolation. Instead, we register diagnosticschannel hooks to handle request isolation now.
While this is generally not expected to break anything, there is one tiny change that _may affect you if you have been relying on very specific functionality:

The ignoreOutgoingRequests option of httpIntegration receives the RequestOptions as second argument. This type is not changed, however due to how the wrapping now works, we no longer pass through the full RequestOptions, but re-construct this partially based on the generated request. For the vast majority of cases, this should be fine, but for the sake of completeness, these are the only fields that may be available there going forward - other fields that may have existed before may no longer be set:

ignoreOutgoingRequests(url: string, {
  method: string;
  protocol: string;
  host: string;
  hostname: string; // same as host
  path: string;
  headers: OutgoingHttpHeaders;
})

Other changes

• feat(cloudflare): Add logs exports (#16165)
• feat(vercel-edge): Add logs export (#16166)
• feat(cloudflare): Read SENTRY_RELEASE from env (#16201)
• feat(node): Drop http.server spans with 404 status by default (#16205)
• fix(browser): Respect manually set sentry tracing headers in XHR requests (#16184)
• fix(core): Respect manually set sentry tracing headers in fetch calls (#16183)
• fix(feedback): Prevent removeFromDom() from throwing (#16030)
• fix(node): Use class constructor in docstring for winston transport (#16167)
• fix(node): Fix vercel flushing logic & add test for it (#16208)
• fix(node): Fix 404 route handling in express 5 (#16211)
• fix(logs): Ensure logs can be flushed correctly (#16216)
• ref(core): Switch to standardized log envelope (#16133)

9.15.0

Important Changes

• feat: Export wrapMcpServerWithSentry from server packages (#16127)

Exports the wrapMcpServerWithSentry which is our MCP server instrumentation from all the server packages.

• feat(core): Associate resource/tool/prompt invocations with request span instead of response span (#16126)

Adds a best effort mechanism to associate handler spans for resource, tool and prompt with the incoming message requests instead of the outgoing SSE response.

Other Changes

• fix: Vercel ai ESM patching (#16152)
• fix(node): Update version range for module.register (#16125)
• fix(react-router): Spread unstable_sentryVitePluginOptions correctly (#16156)
• fix(react): Fix Redux integration failing with reducer injection (#16106)
• fix(remix): Add ESM-compatible exports (#16124)
• fix(remix): Avoid rewrapping root loader. (#16136)

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

9.14.0

Important Changes

• feat: Add Supabase Integration (#15719)

This PR adds Supabase integration to sentry/core, allowing automatic instrumentation of Supabase client operations (database queries and authentication) for performance monitoring and error tracking.

• feat(nestjs): Gracefully handle RPC scenarios in SentryGlobalFilter (#16066)

This PR adds better RPC exception handling to sentry/nestjs, preventing application crashes while still capturing errors and warning users when a dedicated filter is needed. The implementation gracefully handles the 'rpc' context type in SentryGlobalFilter to improve reliability in hybrid applications.

• feat(react-router): Trace propagation (#16070)

This PR adds trace propagation to sentry/react-router by providing utilities to inject trace meta tags into HTML headers and offering a pre-built Sentry-instrumented request handler, improving distributed tracing capabilities across page loads.

Other Changes

• feat(deps): Bump prisma/instrumentation from 6.5.0 to 6.6.0 (#16102)
• feat(nextjs): Improve server component data (#15996)
• feat(nuxt): Log when adding HTML trace meta tags (#16044)
• fix(node): Make body capturing more robust (#16105)
• ref(node): Log when incoming request bodies are being captured (#16104)

9.13.0

Important Changes

• feat(node): Add support for winston logger (#15983)

  Sentry is adding support for structured logging. In this release we've added support for sending logs to Sentry via the winston logger to the Sentry Node SDK (and SDKs that use the Node SDK under the hood like sentry/nestjs). The Logging APIs in the Sentry SDK are still experimental and subject to change.

  const winston = require('winston');
  const Transport = require('winston-transport');
  
  const transport = Sentry.createSentryWinstonTransport(Transport);
  
  const logger = winston.createLogger({
    transports: [transport],
  });

• feat(core): Add wrapMcpServerWithSentry to instrument MCP servers from modelcontextprotocol/sdk (#16032)

  The Sentry SDK now supports instrumenting MCP servers from the modelcontextprotocol/sdk package. Compatible with versions ^1.9.0 of the modelcontextprotocol/sdk package.

  import { McpServer } from 'modelcontextprotocol/sdk/server/mcp.js';
  
  // Create an MCP server
  const server = new McpServer({
    name: 'Demo',
    version: '1.0.0',
  });
  
  // Use the instrumented server in your application
  const instrumentedServer = Sentry.wrapMcpServerWithSentry(server);

• feat(core): Move console integration into core and add to cloudflare/vercel-edge (#16024)

  Console instrumentation has been added to sentry/cloudflare and sentry/nextjs Edge Runtime and is enabled by default. Now calls to the console object will be captured as breadcrumbs for those SDKs.

• feat(bun): Support new Bun.serve APIs (#16035)

  Bun 1.2.6 and above have a new Bun.serve API, which the Bun SDK now supports. The SDK instruments the new routes object that can be used to define routes for the server.

  Thanks to Jarred-Sumner for helping us get this supported!

Other Changes

• feat(browser): Warn on duplicate browserTracingIntegration (#16042)
• feat(core): Allow delayed sending with offline transport (#15937)
• feat(deps): Bump sentry/webpack-plugin from 3.2.4 to 3.3.1 (#16057)
• feat(vue): Apply stateTransformer to attachments in Pinia Plugin (#16034)
• fix(core): Run beforeSendLog after we process log (#16019)
• fix(nextjs): Don't show turbopack warning for newer Next.js canaries (#16065)
• fix(nextjs): Include patch version 0 for min supported 15.3.0 (#16026)
• fix(node): Ensure late init works with all integrations (#16016)
• fix(react-router): Pass unstable_sentryVitePluginOptions to cli instance (#16033)
• fix(serverless-aws): Overwrite root span name with GraphQL if set (#16010)

9.12.0

Important Changes

• feat(feedback): Implement highlighting and hiding controls for screenshots (#15951)

  The Sentry SDK now supports highlighting and hiding controls for screenshots in user feedback reports. This functionality is enabled by default.

• feat(node): Add ignoreIncomingRequestBody callback to httpIntegration (#15959)

  The httpIntegration now supports an optional ignoreIncomingRequestBody callback that can be used to skip capturing the body of incoming requests.

  Sentry.init({
    integrations: [
      Sentry.httpIntegration({
        ignoreIncomingRequestBody: (url, request) => {
          return request.method === 'GET' && url.includes('/api/large-payload');
        },
      }),
    ],
  });

  The ignoreIncomingRequestBody callback receives the URL of the request and should return true if the body should be ignored.

• Logging Improvements

  Sentry is adding support for structured logging. In this release we've made a variety of improvements to logging functionality in the Sentry SDKs.

  • feat(node): Add server.address to nodejs logs (#16006)
  • feat(core): Add sdk name and version to logs (#16005)
  • feat(core): Add sentry origin attribute to console logs integration (#15998)
  • fix(core): Do not abbreviate message parameter attribute (#15987)
  • fix(core): Prefix release and environment correctly (#15999)
  • fix(node): Make log flushing logic more robust (#15991)

Other Changes

• build(aws-serverless): Include debug logs in lambda layer SDK bundle (#15974)
• feat(astro): Add tracking of errors during HTML streaming (#15995)
• feat(browser): Add onRequestSpanStart hook to browser tracing integration (#15979)
• feat(deps): Bump sentry/cli from 2.42.3 to 2.43.0 (#16001)
• feat(nextjs): Add captureRouterTransitionStart hook for capturing navigations (#15981)
• feat(nextjs): Mark clientside prefetch request spans with http.request.prefetch: true attribute (#15980)
• feat(nextjs): Un experimentify clientInstrumentationHook (#15992)
• feat(nextjs): Warn when client was initialized more than once (#15971)
• feat(node): Add support for SENTRY_DEBUG env variable (#15972)
• fix(tss-react): Change authToken type to string (#15985)

Work in this release was contributed by Page- and Fryuni. Thank you for your contributions!

9.11.0

• feat(browser): Add http.redirect_count attribute to browser.redirect span (#15943)
• feat(core): Add consoleLoggingIntegration for logs (#15955)
• feat(core): Don't truncate error messages (#15818)
• feat(core): Emit debug log when transport execution fails (#16009)
• feat(nextjs): Add release injection in Turbopack (#15958)
• feat(nextjs): Record turbopack as tag (#15928)
• feat(nuxt): Base decision on source maps upload only on Nuxt source map settings (#15859)
• feat(react-router): Add sentryHandleRequest (#15787)
• fix(node): Use module instead of require for CJS check (#15927)
• fix(remix): Remove mentions of deprecated ErrorBoundary wrapper (#15930)
• ref(browser): Temporarily add sentry.previous_trace span attribute (#15957)
• ref(browser/core): Move all log flushing logic into clients (#15831)
• ref(core): Improve URL parsing utilities (#15882)

9.10.1

• fix: Correct sentry-internal/feedback docs to match the code (#15874)
• deps: Bump bundler plugins to version 3.2.4 (#15909)

9.10.0

Important Changes

• feat: Add support for logs

  • feat(node): Add logging public APIs to Node SDKs (#15764)
  • feat(core): Add support for beforeSendLog (#15814)
  • feat(core): Add support for parameterizing logs (#15812)
  • fix: Remove critical log severity level (#15824)

  All JavaScript SDKs other than sentry/cloudflare and sentry/deno now support sending logs via dedicated methods as part of Sentry's upcoming logging product.

  Logging is gated by an experimental option, _experiments.enableLogs.

  Sentry.init({
    dsn: 'PUBLIC_DSN',
    // `enableLogs` must be set to true to use the logging features
    _experiments: { enableLogs: true },
  });
  
  const { trace, debug, info, warn, error, fatal, fmt } = Sentry.logger;
  
  trace('Starting database connection', { database: 'users' });
  debug('Cache miss for user', { userId: 123 });
  error('Failed to process payment', { orderId: 'order_123', amount: 99.99 });
  fatal('Database connection pool exhausted', { database: 'users', activeConnections: 100 });
  
  // Structured logging via the `fmt` helper function. When you use `fmt`, the string template and parameters are sent separately so they can be queried independently in Sentry.
  
  info(fmt(`Updated profile for user ${userId}`));
  warn(fmt(`Rate limit approaching for endpoint ${endpoint}. Requests: ${requests}, Limit: ${limit}`));

  With server-side SDKs like sentry/node, sentry/bun or server-side of sentry/nextjs or sentry/sveltekit, you can do structured logging without needing the fmt helper function.

  const { info, warn } = Sentry.logger;
  
  info('User %s logged in successfully', [123]);
  warn('Failed to load user %s data', [123], { errorCode: 404 });

  To filter logs, or update them before they are sent to Sentry, you can use the _experiments.beforeSendLog option.

• feat(browser): Add diagnoseSdkConnectivity() function to programmatically detect possible connectivity issues (#15821)

  The diagnoseSdkConnectivity() function can be used to programmatically detect possible connectivity issues with the Sentry SDK.

  const result = await Sentry.diagnoseSdkConnectivity();

  The result will be an object with the following properties:

  • "no-client-active": There was no active client when the function was called. This possibly means that the SDK was not initialized yet.
  • "sentry-unreachable": The Sentry SaaS servers were not reachable. This likely means that there is an ad blocker active on the page or that there are other connection issues.
  • undefined: The SDK is working as expected.

• SDK Tracing Performance Improvements for Node SDKs

  • feat: Stop using dropUndefinedKeys (#15796)
  • feat(node): Only add span listeners for instrumentation when used (#15802)
  • ref: Avoid dropUndefinedKeys for spanToJSON calls (#15792)
  • ref: Avoid using SentryError for PromiseBuffer control flow (#15822)
  • ref: Stop using dropUndefinedKeys in SpanExporter (#15794)
  • ref(core): Avoid using SentryError for event processing control flow (#15823)
  • ref(node): Avoid dropUndefinedKeys in Node SDK init (#15797)
  • ref(opentelemetry): Avoid sampling work for non-root spans (#15820)

  We've been hard at work making performance improvements to the Sentry Node SDKs (sentry/node, sentry/aws-serverless, sentry/nestjs, etc.). We've seen that upgrading from 9.7.0 to 9.10.0 leads to 30-40% improvement in request latency for HTTP web-server applications that use tracing with high sample rates. Non web-server applications and non-tracing applications will see smaller improvements.

Other Changes

• chore(deps): Bump rrweb to 2.35.0 (#15825)
• deps: Bump bundler plugins to 3.2.3 (#15829)
• feat: Always truncate stored breadcrumb messages to 2kb (#15819)
• feat(nextjs): Disable server webpack-handling for static builds (#15751)
• fix(nuxt): Don't override Nuxt options if undefined (#15795)

9.9.0

Important Changes

• feat(nextjs): Support instrumentation-client.ts (#15705)

  Next.js recently added a feature to support client-side (browser) instrumentation via a instrumentation-client.ts file.

  To be forwards compatible, the Sentry Next.js SDK will now pick up instrumentation-client.ts files even on older Next.js versions and add them to your client bundles.
  It is suggested that you either rename your sentry.client.config.ts file to instrumentation-client.ts, or if you already happen to have a instrumentation-client.ts file move the contents of sentry.client.config.ts to instrumentation-client.ts.

• feat(browser): Add previous_trace span links (#15569)

  The sentry/browser SDK and SDKs based on sentry/browser now emits a link from the first root span of a newly started trace to the root span of a previously started trace. You can control this feature via an option in browserTracingIntegration():

  Sentry.init({
    dsn: 'your-dsn-here'
    integrations: [
      Sentry.browserTracingIntegration({
        // Available settings:
        // - 'in-memory' (default): Stores previous trace information in memory
        // - 'session-storage': Stores previous trace information in the browser's `sessionStorage`
        // - 'off': Disable storing and sending previous trace information
        linkPreviousTrace: 'in-memory',
      }),
    ],
  });

• feat(browser): Add logger.X methods to browser SDK (#15763)

  For Sentry's upcoming logging product, the SDK now supports sending logs via dedicated methods.

  Sentry.init({
    dsn: 'your-dsn-here',
    _experiments: {
      enableLogs: true, // This is required to use the logging features
    },
  });
  
  Sentry.logger.info('This is a trace message', { userId: 123 });
  // See PR for better documentation

  Please note that the logs product is still in early access. See the link above for more information.

Other Changes

• feat(browser): Attach host as part of error message to "Failed to fetch" errors (#15729)
• feat(core): Add parseStringToURL method (#15768)
• feat(core): Optimize dropUndefinedKeys (#15760)
• feat(node): Add fastify shouldHandleError (#15771)
• fix(nuxt): Delete no longer needed Nitro 'close' hook (#15790)
• perf(nestjs): Remove usage of addNonEnumerableProperty (#15766)
• ref: Avoid some usage of dropUndefinedKeys() (#15757)
• ref: Remove some usages of dropUndefinedKeys() (#15781)
• ref(nextjs): Fix Next.js vercel-edge runtime package information (#15789)

9.8.0

• feat(node): Implement new continuous profiling API spec (#15635)
• feat(profiling): Add platform to chunk envelope (#15758)
• feat(react): Export captureReactException method (#15746)
• fix(node): Check for res.end before passing to Proxy (#15776)
• perf(core): Add short-circuits to eventFilters integration (#15752)
• perf(node): Short circuit flushing on Vercel only for Vercel (#15734)

9.7.0

• feat(core): Add captureLog method (#15717)
• feat(remix/cloudflare): Export sentryHandleError (#15726)
• fix(node): Always flush on Vercel before Lambda freeze (#15602)
• fix(node): Ensure incoming traces are propagated without HttpInstrumentation (#15732)
• fix(node): Use fatal level for unhandled rejections in strict mode (#15720)
• fix(nuxt): Delete Nuxt server template injection (#15749)

9.6.1

• feat(deps): bump prisma/instrumentation from 6.4.1 to 6.5.0 (#15714)
• feat(deps): bump sentry/cli from 2.42.2 to 2.42.3 (#15711)
• fix(nextjs): Re-patch router if it is overridden by Next.js (#15721)
• fix(nuxt): Add Nitro Rollup plugin to inject Sentry server config (#15710)
• chore(deps): Bump rollup to 4.35.0 (#15651)

9.6.0

Important Changes

• feat(tanstackstart): Add sentry/tanstackstart-react package and make sentry/tanstackstart package a utility package (#15629)

  Since TanStack Start is supposed to be a generic framework that supports libraries like React and Solid, the sentry/tanstackstart SDK package was renamed to sentry/tanstackstart-react to reflect that the SDK is specifically intended to be used for React TanStack Start applications.
  Note that the TanStack Start SDK is still in alpha status and may be subject to breaking changes in non-major package updates.

Other Changes

• feat(astro): Accept all vite-plugin options (#15638)
• feat(deps): bump sentry/webpack-plugin from 3.2.1 to 3.2.2 (#15627)
• feat(tanstackstart): Refine initial API (#15574)
• fix(core): Ensure fill only patches functions (#15632)
• fix(nextjs): Consider pageExtensions when looking for instrumentation file (#15701)
• fix(remix): Null-check options (#15610)
• fix(sveltekit): Correctly parse angle bracket type assertions for auto instrumentation (#15578)
• fix(sveltekit): Guard process variable (#15605)

Work in this release was contributed by angelikatyborska and nwalters512. Thank you for your contributions!

9.5.0

Important Changes

We found some issues with the new feedback screenshot annotation where screenshots are not being generated properly. Due to this issue, we are reverting the feature.

• Revert "feat(feedback) Allowing annotation via highlighting & masking (#15484)" (#15609)

Other Changes

• Add cloudflare adapter detection and path generation (#15603)
• deps(nextjs): Bump rollup to 4.34.9 (#15589)
• feat(bun): Automatically add performance integrations (#15586)
• feat(replay): Bump rrweb to 2.34.0 (#15580)
• fix(browser): Call original function on early return from patched history API (#15576)
• fix(nestjs): Copy metadata in custom decorators (#15598)
• fix(react-router): Fix config type import (#15583)
• fix(remix): Use correct types export for sentry/remix/cloudflare (#15599)
• fix(vue): Attach Pinia state only once per event (#15588)

Work in this release was contributed by msurdi-a8c, namoscato, and rileyg98. Thank you for your contributions!

9.4.0

• feat(core): Add types for logs protocol and envelope (#15530)
• feat(deps): Bump sentry/cli from 2.41.1 to 2.42.2 (#15510)
• feat(deps): Bump sentry/webpack-plugin from 3.1.2 to 3.2.1 (#15512)
• feat(feedback) Allowing annotation via highlighting & masking (#15484)
• feat(nextjs): Add use client directive to client SDK entrypoints (#15575)
• feat(nextjs): Allow silencing of instrumentation warning (#15555)
• feat(sveltekit): Ensure AsyncLocalStorage async context strategy is used in Cloudflare Pages (#15557)
• fix(cloudflare): Make cloudflare/workers-types an optional peer dependency (#15554)
• fix(core): Don't reverse values in event filters (#15584)
• fix(core): Handle normalization of null prototypes correctly (#15556)
• fix(nextjs): Only warn on missing onRequestError in version 15 (#15553)
• fix(node): Allow for undefined transport to be passed in (#15560)
• fix(wasm): Fix wasm integration stacktrace parsing for filename (#15572)
• perf(node): Store normalized request for processing (#15570)

9.3.0

Important Changes

With this release we're publishing two new SDKs in experimental alpha stage:

• feat(tanstackstart): Add TanStack Start SDK (#15523)

For details please refer to the README

• feat(react-router): Add React Router SDK (#15524)

For details please refer to the README

• feat(remix): Add support for Hydrogen (#15450)

This PR adds support for Shopify Hydrogen applications running on MiniOxygen runtime.

Other Changes

• feat(core): Add forceTransaction to trpc middleware options (#15519)
• feat(core): Default filter unactionable error (#15527)
• feat(core): Rename inboundFiltersIntegration to eventFiltersIntegration (#15434)
• feat(deps): bump prisma/instrumentation from 6.2.1 to 6.4.1 (#15480)
• feat(react-router): Add build-time config (#15406)
• feat(replay): Bump rrweb to 2.33.0 (#15514)
• fix(core): Fix allowUrls and denyUrls for linked and aggregate exceptions (#15521)
• fix(nextjs): Don't capture devmode server-action redirect errors (#15485)
• fix(nextjs): warn about missing onRequestError handler #15488)
• fix(nextjs): Prevent wrong culprit from showing up for clientside error events #15475)
• fix(nuxt): Ignore 300-400 status codes on app errors in Nuxt (#15473)
• fix(react): Add support for cross-usage of React Router instrumentations (#15283)
• fix(sveltekit): Guard process check when flushing events (#15516)

Work in this release was contributed by GerryWilko and leoambio. Thank you for your contributions!

9.2.0

Important Changes

• feat(node): Support Express v5 (#15380)

This release adds full tracing support for Express v5, and improves tracing support for Nest.js 11 (which uses Express v5) in the Nest.js SDK.

• feat(sveltekit): Add Support for Cloudflare (#14672)

This release adds support for deploying SvelteKit applications to Cloudflare Pages.
A docs update with updated instructions will follow shortly.
Until then, you can give this a try by setting up the SvelteKit SDK as usual and then following the instructions outlined in the PR.

Thank you SG60 for contributing this feature!

Other Changes

• feat(core): Add addLink(s) to Sentry span (#15452)
• feat(core): Add links to span options (#15453)
• feat(deps): Bump sentry/webpack-plugin from 2.22.7 to 3.1.2 (#15328)
• feat(feedback): Disable Feedback submit & cancel buttons while submitting (#15408)
• feat(nextjs): Add experimental flag to not strip origin information from different origin stack frames (#15418)
• feat(nuxt): Add enableNitroErrorHandler to server options (#15444)
• feat(opentelemetry): Add addLink(s) to span (#15387)
• feat(opentelemetry): Add links to span options (#15403)
• feat(replay): Expose rrweb recordCrossOriginIframes under _experiments (#14916)
• fix(browser): Ensure that performance.measure spans have a positive duration (#15415)
• fix(bun): Includes correct sdk metadata (#15459)
• fix(core): Add Google gmo error to Inbound Filters (#15432)
• fix(core): Ensure http.client span descriptions don't contain query params or fragments (#15404)
• fix(core): Filter out unactionable Facebook Mobile browser error (#15430)
• fix(nestjs): Pin dependency on opentelemetry/instrumentation (#15419)
• fix(nuxt): Only use filename with file extension from command (#15445)
• fix(nuxt): Use SentryNuxtServerOptions type for server init (#15441)
• fix(sveltekit): Avoid loading vite config to determine source maps setting (#15440)
• ref(profiling-node): Bump chunk interval to 60s (#15361)

Work in this release was contributed by 6farer, dgavranic and SG60. Thank you for your contributions!

9.1.0

• feat(browser): Add graphqlClientIntegration (#13783)
• feat(core): Allow for nested trpc context (#15379)
• feat(core): Create types and utilities for span links (#15375)
• feat(deps): bump opentelemetry/instrumentation-pg from 0.50.0 to 0.51.0 (#15273)
• feat(node): Extract Sentry-specific node-fetch instrumentation (#15231)
• feat(vue): Support Pinia v3 (#15383)
• fix(sveltekit): Avoid request body double read errors (#15368)
• fix(sveltekit): Avoid top-level vite import (#15371)

Work in this release was contributed by Zen-cronic and filips-alpe. Thank you for your contribution!

9.0.1

• ref(flags): rename unleash integration param (#15343)

9.0.0

Version 9.0.0 marks a release of the Sentry JavaScript SDKs that contains breaking changes.
The goal of this release is to trim down on unused and potentially confusing APIs, prepare the SDKs for future framework versions to build deeper instrumentation, and remove old polyfills to reduce the packages' size.

How To Upgrade

Please carefully read through the migration guide in the Sentry docs on how to upgrade from version 8 to version 9.
Make sure to select your specific platform/framework in the top left corner: https://docs.sentry.io/platforms/javascript/migration/v8-to-v9/

A comprehensive migration guide outlining all changes for all the frameworks can be found within the Sentry JavaScript SDK Repository: https://github.com/getsentry/sentry-javascript/blob/develop/MIGRATION.md

Breaking Changes

• doc(deno)!: Make Deno v2 the minimum supported version (#15085)
• feat!: Bump typescript to ~5.0.0 (#14758)
• feat!: Drop nitro-utils package (#14998)
• feat!: Only collect ip addresses with sendDefaultPii: true (#15084)
• feat!: Remove autoSessionTracking option (#14802)
• feat!: Remove enableTracing (#15078)
• feat!: Remove getCurrentHub(), Hub, and getCurrentHubShim() (#15122)
• feat!: Remove spanId from propagation context (#14733)
• feat!: Remove deprecated and unused code (#15077)
• feat!: Remove metrics API from the JS SDK (#14745)
• feat!: Require Node >=18 as minimum supported version (#14749)
• feat(astro)!: Respect user-specified source map setting (#14941)
• feat(browser)!: Remove captureUserFeedback method (#14820)
• feat(build)!: Drop pre-ES2020 polyfills (#14882)
• feat(core)!: Add normalizedRequest to samplingContext (#14902)
• feat(core)!: Always use session from isolation scope (#14860)
• feat(core)!: Pass root spans to beforeSendSpan and disallow returning null (#14831)
• feat(core)!: Remove BAGGAGE_HEADER_NAME export (#14785)
• feat(core)!: Remove TransactionNamingScheme type (#14865)
• feat(core)!: Remove addOpenTelemetryInstrumentation method (#14792)
• feat(core)!: Remove arrayify method (#14782)
• feat(core)!: Remove debugIntegration and sessionTimingIntegration (#14747)
• feat(core)!: Remove flatten method (#14784)
• feat(core)!: Remove getDomElement method (#14797)
• feat(core)!: Remove makeFifoCache method (#14786)
• feat(core)!: Remove memoBuilder export & WeakSet fallback (#14859)
• feat(core)!: Remove transactionContext from samplingContext (#14904)
• feat(core)!: Remove urlEncode method (#14783)
• feat(core)!: Remove deprecated Request type (#14858)
• feat(core)!: Remove deprecated request data methods (#14896)
• feat(core)!: Remove standalone Client interface & deprecate BaseClient (#14800)
• feat(core)!: Remove validSeverityLevels export (#14765)
• feat(core)!: Stop accepting event as argument for recordDroppedEvent (#14999)
• feat(core)!: Stop setting user in requestDataIntegration (#14898)
• feat(core)!: Type sdkProcessingMetadata more strictly (#14855)
• feat(core)!: Update hasTracingEnabled to consider empty trace config (#14857)
• feat(core)!: Update requestDataIntegration handling (#14806)
• feat(deno)!: Remove deno prepack (#14829)
• feat(ember)!: Officially drop support for ember <=3.x (#15032)
• feat(nestjs)!: Move nestIntegration into nest sdk and remove setupNestErrorHandler (#14751)
• feat(nestjs)!: Remove WithSentry decorator (#14762)
• feat(nestjs)!: Remove SentryService (#14759)
• feat(nextjs)!: Don't rely on Next.js Build ID for release names (#14939)
• feat(nextjs)!: Remove experimental_captureRequestError (#14607)
• feat(nextjs)!: Respect user-provided source map generation settings (#14956)
• feat(node)!: Add support for Prisma v6 and drop v5 support (#15120)
• feat(node)!: Avoid http spans by default for custom OTEL setups (#14678)
• feat(node)!: Collect request sessions via HTTP instrumentation (#14658)
• feat(node)!: Remove processThreadBreadcrumbIntegration (#14666)
• feat(node)!: Remove fine grained registerEsmLoaderHooks (#15002)
• feat(opentelemetry)!: Exclusively pass root spans through sampling pipeline (#14951)
• feat(pinia)!: Include state of all stores in breadcrumb (#15312)
• feat(react)!: Raise minimum supported TanStack Router version to 1.63.0 (#15030)
• feat(react)!: Remove deprecated getNumberOfUrlSegments method (#14744)
• feat(react)!: Remove deprecated react router methods (#14743)
• feat(react)!: Update ErrorBoundary componentStack type (#14742)
• feat(remix)!: Drop support for Remix v1 (#14988)
• feat(remix)!: Remove autoInstrumentRemix option (#15074)
• feat(solidstart)!: Default to --import setup and add autoInjectServerSentry (#14862)
• feat(solidstart)!: No longer export sentrySolidStartVite (#15143)
• feat(solidstart)!: Respect user-provided source map setting (#14979)
• feat(svelte)!: Disable component update tracking by default (#15265)
• feat(sveltekit)!: Drop support for SvelteKit 1.x (#15037)
• feat(sveltekit)!: Remove fetchProxyScriptNonce option (#15123)
• feat(sveltekit)!: Respect user-provided source map generation settings (#14886)
• feat(utils)!: Remove sentry/utils package (#14830)
• feat(vue)!: Remove configuring Vue tracing options anywhere else other than through the vueIntegration's tracingOptions option (#14856)
• feat(vue/nuxt)!: No longer create "update" spans for component tracking by default (#14602)
• fix(node)!: Fix name of vercelAIIntegration to VercelAI (#15298)
• fix(vue)!: Remove logError from vueIntegration (#14958)
• ref!: Don't polyfill optional chaining and nullish coalescing (#14603)
• ref(core)!: Cleanup internal types, including ReportDialogOptions (#14861)
• ref(core)!: Mark exceptions from captureConsoleIntegration as handled: true by default (#14734)
• ref(core)!: Move shutdownTimeout option type from core to node (#15217)
• ref(core)!: Remove Scope type interface in favor of using Scope class (#14721)

⚠️ Changelog content truncated by 12743 characters because it was over the limit (60000) and wouldn't fit into PR description.