unstale

npm / @sentry/vue

@sentry/vue

What changed in @sentry/vue 5 to 11, from its official release notes, upgrade guides and advisories. Also covers @sentry/browser, @sentry/core, @sentry/nextjs, @sentry/node, @sentry/node-native, @sentry/profiling-node, @sentry/react, @sentry/tanstackstart-react, @sentry/types, @sentry/vite-plugin. Sources checked 2026-10-23.

257 breaking6 security15 deprecations95 new APIs and options2 performance116 behavior and defaults8 tooling111 fixes and other

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

@unstale/cli 0.2.3 on npm

@sentry/vue 11228 changes

Breaking changes 139

  • Bundler plugins now require Node.js 20.19.0 or higher.

    11.8.0release notes

  • Vercel deploy environments now use VERCEL_TARGET_ENV values; configure release.deploy.env to retain old names.

    11.8.0release notes

  • The webpack plugin now requires webpack 5.1 or higher.

    11.8.0release notes

  • Next.js forbidden() errors are no longer captured as errors.

    11.5.0release notes

  • Sentry.close() now unbinds the closed client, allowing getClient() and isInitialized() to reflect an uninitialized state before later init().

    11.5.0release notes

  • AI integrations are no longer available in the browser SDK; they remain available in server-side SDKs.

    11.0.0upgrade guide

  • attachStacktrace now defaults to true.

    11.0.0release notesupgrade guide

  • Message events and non-Error values passed to captureException now receive a synthetic stack trace pointing to the call site. Set attachStacktrace to false to restore the previous behavior.

    11.0.0upgrade guide

  • The callback moved from _experiments to the top-level Sentry.init options.

    11.0.0upgrade guide

  • Now runs as each span finishes and receives StreamedSpanJSON with renamed fields; wrap it with withStaticSpan in transaction mode.

    11.0.0upgrade guide

  • No longer does anything in stream mode because transaction events are no longer produced; move span changes to beforeSendSpan.

    11.0.0upgrade guide

  • Sessions affected by an uncaught error are recorded as unhandled instead of crashed, which can shift crash-free session rates.

    11.0.0upgrade guide

  • Collected INP is always sent as a Web Vital span, with its value in this attribute instead of as a span measurement.

    11.0.0upgrade guide

  • The lifecycle option defaults to 'page': a session is created on page load and is not renewed on navigation.

    11.0.0upgrade guide

  • It no longer captures performance.mark() and performance.measure() spans by default and no longer accepts an _experiments object. Interaction timeout options belong on interactionsIntegration.

    11.0.0upgrade guide

  • Deprecated build-time configuration options were removed and can no longer be used.

    11.0.0release notesupgrade guide

  • Replaces the legacy http.client_ip attribute.

    11.0.0upgrade guide

  • AWS Lambda spans use this attribute instead of faas.id for the invoked function ARN.

    11.0.0upgrade guide

  • Replaces code.filepath on ui.long_animation_frame spans.

    11.0.0upgrade guide

  • Span-operation details such as framework, library, method, or lifecycle phase are preserved in attributes including this one.

    11.0.0upgrade guide

  • Ember's init span is now named Component mount; update filters that matched the previous name.

    11.0.0upgrade guide

  • The breadcrumbsIntegration console option was removed. Console breadcrumbs now come from the default consoleIntegration.

    11.0.0upgrade guide

  • Data collection is enabled by default.

    11.0.0release notes

  • dataCollection replaces sendDefaultPii.

    10.55.0, 11.0.0release notesrelease notesupgrade guideupgrade guide

  • Incoming HTTP body capture is controlled by dataCollection.httpBodies.

    11.0.0release notesupgrade guide

  • Data collection is enabled by default, and request data collection is aligned with v11 defaults.

    11.0.0upgrade guide

  • Replaces the legacy db.mongodb.collection attribute.

    11.0.0upgrade guide

  • Redis and ioredis instrumentations no longer emit this attribute; connections are described by server.address and server.port instead.

    11.0.0upgrade guide

  • Replaces the legacy db.name attribute.

    11.0.0upgrade guide

  • Replaces the legacy db.operation span attribute.

    11.0.0upgrade guide

  • Replaces db.statement; SQL query spans also include a sanitized-statement summary in db.query.summary.

    11.0.0upgrade guide

  • Replaces db.system and carries database-system identity; Mongoose spans report mongodb rather than mongoose.

    11.0.0upgrade guide

  • The default environment and deploy names no longer use the vercel- prefix.

    11.0.0upgrade guide

  • The option was removed; channel-based instrumentation means the SDK can no longer detect when a framework was imported before Sentry.init().

    11.0.0upgrade guide

  • Events created from a DOMException no longer carry this tag. Switch searches and alert rules using it to error.type.

    11.0.0upgrade guide

  • The enableLogs option is removed.

    11.0.0release notesupgrade guideupgrade guide

  • The enableMetrics option is removed.

    11.0.0release notesupgrade guideupgrade guide

  • Replace skipOpenTelemetrySetup with enableOpenTelemetrySetup for OpenTelemetry setup control.

    11.0.0release notesupgrade guide

  • The enableTruncation flag and AI integration truncation logic are removed.

    11.0.0release notesupgrade guide

  • endTimestamp is removed from SentrySpanArguments.

    11.0.0release notesupgrade guideupgrade guide

  • On file spans, replaces fs_error and holds the syscall error code rather than the full message.

    11.0.0upgrade guide

  • The integration reports its name as EventFilters instead of InboundFilters. Update references that look it up by name.

    11.0.0upgrade guide

  • The deprecated _experiments.enableLogs option is removed.

    10.0.0, 11.0.0release notesupgrade guideupgrade guide

  • AWS Lambda spans use this attribute instead of faas.execution for the request ID; Lambda Invoke spans from awsIntegration also use it.

    11.0.0upgrade guide

  • Span-operation details are preserved in attributes including this one.

    11.0.0upgrade guide

  • Next.js framework-function spans use the consolidated function operation instead of function.nextjs.

    11.0.0upgrade guide

  • Replaces ai.pipeline.name and langchain.chain.name; it is omitted for unnamed chains instead of being set to unknown_chain.

    11.0.0upgrade guide

  • The Anthropic integration no longer sets this attribute; legacy Completions prompts are reported as user messages on gen_ai.input.messages.

    11.0.0upgrade guide

  • gen_ai.system is renamed to gen_ai.provider.name.

    11.0.0release notesupgrade guide

  • Replaces the legacy ai.streaming attribute.

    11.0.0upgrade guide

  • gen_ai.tool.input is renamed to gen_ai.tool.call.arguments.

    11.0.0release notesupgrade guide

  • gen_ai.tool.output is renamed to gen_ai.tool.call.result.

    11.0.0release notesupgrade guide

  • gen_ai.request.available_tools is renamed to gen_ai.tool.definitions.

    11.0.0release notesupgrade guide

  • The deprecated gen_ai.tool.type span attribute is no longer set.

    11.0.0release notes

  • No longer set on tool spans.

    11.0.0upgrade guide

  • Replaces the legacy cache-creation token usage attributes.

    11.0.0upgrade guide

  • Replaces the legacy cache-read and cached-input token usage attributes.

    11.0.0upgrade guide

  • Replaces the legacy reasoning output-token attribute.

    11.0.0upgrade guide

  • genAI defaults now collect AI data by default.

    11.0.0release notesupgrade guide

  • Deprecated http.* span attributes are renamed.

    11.0.0release notesupgrade guide

  • Replaces the legacy request content-length attribute and is always reported from the server-side content-length header.

    11.0.0upgrade guide

  • Cookie attributes are no longer split by cookie name; this attribute holds ordered name=value entries, with sensitive values filtered.

    11.0.0upgrade guide

  • Set-Cookie attributes are no longer split by cookie name; this attribute holds ordered name=value entries, with sensitive values filtered and attributes omitted.

    11.0.0upgrade guide

  • HTTP header attributes preserve hyphens in header names and report values as string arrays, with one entry per value.

    11.0.0upgrade guide

  • Replaces http.method and is now the request-method key in SanitizedRequestData for HTTP breadcrumb and client-span data.

    11.0.0upgrade guide

  • Replaces the legacy url.same_origin attribute.

    11.0.0upgrade guide

  • Replaces the legacy http.decoded_response_content_length attribute.

    11.0.0upgrade guide

  • Replaces the legacy response content-length attribute and is always reported from the server-side content-length header.

    11.0.0upgrade guide

  • Replaces the legacy http.response_transfer_size attribute.

    11.0.0upgrade guide

  • Replaces the legacy http.status_code attribute.

    11.0.0upgrade guide

  • Replaces the legacy http.status_text attribute.

    11.0.0upgrade guide

  • The deprecated http.target span attribute is replaced.

    11.0.0release notesupgrade guide

  • Use this option to drop spans in place of ignoreTransactions; filtering a service span also drops its child spans.

    11.0.0upgrade guide

  • No longer does anything in stream mode; use ignoreSpans to drop spans.

    11.0.0upgrade guide

  • The deprecated inboundFiltersIntegration is removed.

    11.0.0release notesupgrade guide

  • The export was removed; the integration now reports itself as EventFilters.

    11.0.0upgrade guide

  • The positional spanOrigin argument was removed. Pass an options object as the last argument instead.

    11.0.0upgrade guide

  • The deprecated instrumentLangGraph API is removed.

    11.0.0release notesupgrade guide

  • Span kind is removed and moved to the sentry.kind attribute.

    11.0.0release notesupgrade guide

  • Koa router and middleware spans no longer set this attribute; use http.route for the route and code.function.name for the middleware handler.

    11.0.0upgrade guide

  • Locale routes such as [lng] are parameterized, and narrower routes take precedence over catch-alls.

    11.0.0upgrade guide

  • AMQP instrumentation no longer emits this attribute.

    11.0.0upgrade guide

  • Web-server middleware spans use the consolidated middleware operation instead of framework-specific operations, including Next.js http.server.middleware.

    11.0.0upgrade guide

  • Deprecated net. span attributes are renamed.

    11.0.0release notesupgrade guide

  • Replaces the legacy net.host.ip attribute.

    11.0.0upgrade guide

  • Replaces the legacy net.host.port attribute.

    11.0.0upgrade guide

  • Replaces the legacy net.peer.ip attribute.

    11.0.0upgrade guide

  • Replaces the legacy net.peer.port attribute.

    11.0.0upgrade guide

  • Replaces http.flavor; HTTP instrumentation reports the protocol version here.

    11.0.0upgrade guide

  • Replaces net.transport; transport values change from ip_tcp and ip_udp to tcp and udp.

    11.0.0upgrade guide

  • Support for Next.js 13 was removed, requiring applications to use a newer Next.js version.

    11.0.0release notesupgrade guide

  • The minimum supported Node.js version is now 20.19.0.

    11.0.0release notesupgrade guideupgrade guide

  • The SDK no longer takes over your OpenTelemetry setup, improving interoperability with existing OpenTelemetry configurations.

    11.0.0upgrade guide

  • Tracing is removed from pages router API routes.

    11.0.0upgrade guide

  • SDK initialization via --require is no longer supported.

    11.0.0release notesupgrade guide

  • Vue Router uses this attribute instead of navigation.route.id, with the same matched route name.

    11.0.0upgrade guide

  • tRPC spans now use the rpc span operation.

    11.0.0release notes

  • Safari 14 is no longer supported; the supported Safari and iOS Safari versions start at 15.

    11.0.0upgrade guide

  • attributes are now required in the sampling context.

    11.0.0release notesupgrade guideupgrade guide

  • Scope tags and extra are no longer applied to streamed spans, including the service span; use attributes for data searchable on spans, logs, and metrics.

    11.0.0upgrade guide

  • The scope.clear() method is removed.

    11.0.0release notesupgrade guideupgrade guide

  • attributes are now required on ScopeData.

    11.0.0release notesupgrade guideupgrade guide

  • The re-export was removed; import attribute constants directly from @sentry/core.

    11.0.0upgrade guide

  • Replaced by dataCollection; remove sendDefaultPii: true because the v11 default matches that behavior.

    11.0.0upgrade guide

  • Browser-only exports moved from @sentry/core to this subpath; platform SDKs continue to re-export as before.

    11.0.0upgrade guide

  • Server-only exports moved from @sentry/core to this subpath; platform SDKs continue to re-export as before.

    11.0.0upgrade guide

  • The package was merged back into @sentry/node. Import its contents from @sentry/node.

    11.0.0upgrade guide

  • The package was removed; use @sentry/tanstackstart-react.

    11.0.0upgrade guide

  • The package is no longer published. Import types from @sentry/core.

    11.0.0upgrade guide

  • The Cloudflare-specific attribute is no longer set.

    11.0.0upgrade guide

  • Metrics moved out of the base CDN bundle and are available only in *.logs.metrics bundles. On other bundles, the API is a no-op that warns in debug builds.

    11.0.0upgrade guide

  • AWS Lambda spans set this attribute to component in both trace lifecycles.

    11.0.0upgrade guide

  • Replaces sentry.source and is set only on the root span.

    11.0.0upgrade guide

  • The API now rejects with an Error in all failure cases; read the unchanged, customizable message from error.message.

    11.0.0upgrade guide

  • Replaces legacy host and peer name attributes, including http.host, net.host.name, and net.peer.name.

    11.0.0upgrade guide

  • Database spans use server.port instead of the legacy net.peer.port attribute.

    11.0.0upgrade guide

  • Events with a stack trace count as errors, so captureMessage marks the current session as errored. Crash-free session rate is not affected.

    11.0.0upgrade guide

  • Use attributes instead of scope tags for data that should be searchable on spans, logs, and metrics; attributes accept strings, numbers, booleans, and arrays of those.

    11.0.0upgrade guide

  • In stream mode, names follow Sentry conventions and avoid URLs, route parameters, and other client-supplied values; update name-based filters to use attributes such as url.full or http.route.

    11.0.0upgrade guide

  • spanToJSON now returns StreamedSpanJSON.

    11.0.0release notesupgrade guideupgrade guide

  • This helper was removed; replace calls with spanToJSON.

    11.0.0upgrade guide

  • The streamGenAiSpans flag is removed.

    11.0.0release notesupgrade guide

  • tracePropagation and propagateTrace option names are unified.

    11.0.0release notesupgrade guide

  • Set to 'static' to retain the previous transaction-based tracing model; transaction mode is a temporary backwards-compatibility measure.

    11.0.0upgrade guide

  • String and regular expression matching is now case-insensitive, and g and y flags are ignored because they made matching stateful.

    11.0.0upgrade guideupgrade guide

  • Tunnel route requests no longer bypass middleware.

    11.0.0upgrade guide

  • TypeScript 3.8 is no longer supported.

    11.0.0release notesupgrade guide

  • The minimum required TypeScript version is 5.0.4, and the SDK no longer ships down-leveled types.

    11.0.0upgrade guide

  • The unstable_sentryWebpackPluginOptions configuration was removed.

    11.0.0release notesupgrade guide

  • Replaces the legacy http.fragment attribute.

    11.0.0upgrade guide

  • All spans now use url.full, url.fragment and url.query.

    11.0.0release notesupgrade guide

  • TanStack Router reports path parameters here instead of under url.path.params.<key>.

    11.0.0upgrade guide

  • Replaces http.query and is used with url.path in place of http.target.

    11.0.0upgrade guide

  • Replaces the legacy http.scheme attribute.

    11.0.0upgrade guide

  • urlQueryParams replaces queryParams.

    11.0.0release notesupgrade guide

  • Replaces the legacy http.user_agent attribute.

    11.0.0upgrade guide

  • Use this integration instead of the removed addVercelAiProcessors helper.

    11.0.0upgrade guide

  • Vue's Application Render span is now named Root; update filters that matched the previous name.

    11.0.0upgrade guide

  • withSentryConfig moved to the @sentry/nextjs/config subpath.

    11.0.0release notesupgrade guide

Security 1

  • Query parameters are filtered in request error context to avoid sending sensitive values to Sentry.

    11.7.0release notes

Deprecations 4

  • The webpack.treeshake option is deprecated because bundleSizeOptimizations takes precedence when both are set.

    11.7.0release notes

  • This option is deprecated. To disable INP, use browserTracingIntegration({ webVitals: { ignore: ["inp"] } }).

    11.0.0upgrade guide

  • Nested reactComponentAnnotation options now emit deprecation notices.

    11.0.0release notesupgrade guide

  • The wrapper is now a no-op because streamed payloads are the default, and it is deprecated.

    11.0.0upgrade guide

New APIs and options 15

  • OpenAI decisions.create calls now produce gen_ai.decide spans for tracing.

    11.8.0release notes

  • Adds a Cloudflare Workers entry point exporting withSentry for Next.js Worker handlers, providing the same spans as on Node.js.

    11.6.0release notes

  • Next.js route provider registration enables route provider handling for Next.js applications.

    11.3.0release notes

  • Runtimes without auto-instrumentation can manually instrument TypeSafe clients.

    11.1.0release notes

  • A default integration now automatically wraps MCP server instances, so manual wrapping is no longer required.

    11.1.0release notes

  • showReportDialog now accepts an onError callback.

    11.1.0release notes

  • A default integration creates evaluation spans for TypeSafe calls through the TypeSafe SDK.

    11.1.0release notes

  • BrowserOptions now supports the TransportOptions generic.

    11.0.0upgrade guide

  • SQL query spans now include the summary of the sanitized statement in both trace lifecycles.

    11.0.0upgrade guide

  • GraphQL processing type is retained as an attribute when span names no longer include the processing phase.

    11.0.0upgrade guide

  • AMQP instrumentation reports the message conversation ID using this attribute.

    11.0.0upgrade guide

  • AMQP instrumentation reports the messaging operation name using this attribute.

    11.0.0upgrade guide

  • AMQP instrumentation reports the RabbitMQ destination routing key using this attribute.

    11.0.0upgrade guide

  • In Node.js, Bun, Vercel Edge, and Cloudflare, set this environment variable to static to retain transaction mode.

    11.0.0upgrade guide

  • Restore vitals are collected by default in stream mode when instrumentBfcacheRestore is enabled. Set this option to false to disable collection.

    11.0.0upgrade guide

Performance 1

  • Webpack and Turbopack use faster component annotation, improving bundler performance.

    11.1.0release notes

Behavior and default changes 51

  • The LinkedErrors integration now supports SuppressedError instances.

    11.8.0release notes

  • The top-level option now removes unused SDK code in webpack and Turbopack builds.

    11.7.0release notes

  • use cache fill spans now include the code.file.path attribute, providing the source file path for these spans.

    11.5.0release notes

  • Repeated Sentry.init() calls now warn; @sentry/nextjs returns the active client instead of undefined.

    11.5.0release notes

  • The server instrumentation now supports amqplib v2.

    11.1.0release notes

  • Vercel AI evaluation calls now create gen_ai.evaluate spans containing evaluation inputs and outputs.

    11.1.0release notes

  • Prisma 8 ORM calls now produce nested database query spans without requiring code changes.

    11.1.0release notes

  • The Turbopack orchestrion loader now runs only for instrumented packages.

    11.1.0release notes

  • AWS Lambda spans fall back to Serverless function execution when neither invocation context nor this environment variable provides a name.

    11.0.0upgrade guide

  • beforeSendSpan is compatible with streamed spans by default.

    11.0.0release notesupgrade guide

  • Event Timing and INP spans keep the DOM path on this attribute in both trace lifecycles; match it instead of filtering by DOM path elsewhere.

    11.0.0upgrade guide

  • BrowserTracing now automatically adds the WebVitals integration. Configure Web Vitals through webVitals options or register webVitalsIntegration explicitly.

    11.0.0upgrade guide

  • Next.js build options are aligned with BuildTimeOptionsBase.

    11.0.0upgrade guide

  • Cache spans now carry this attribute with the cache operation (get, put, or remove); cache keys are no longer part of span names.

    11.0.0upgrade guide

  • Default environment and deploy names no longer include the vercel- prefix.

    11.0.0release notes

  • GCP and Firebase function names come from FUNCTION_TARGET or K_SERVICE; the function name remains on faas.name.

    11.0.0upgrade guide

  • Next.js function spans emit low-cardinality names.

    11.0.0upgrade guide

  • Framework functions now use the function span operation.

    11.0.0release notesupgrade guide

  • GCP and Firebase trigger details are reported on gcp.function.context.*.

    11.0.0upgrade guide

  • The legacy Anthropic Completions API prompt is reported as a user message on this attribute.

    11.0.0upgrade guide

  • Terminal request handlers now use the handler span operation.

    11.0.0release notesupgrade guide

  • Click idle spans copy this attribute from the route span.

    11.0.0upgrade guide

  • Runs when a span starts, before its final name may be available; match span attributes instead of relying on names.

    11.0.0upgrade guide

  • BrowserTracing now starts a navigation span after a back/forward-cache restore by default. Set this option to false to disable it.

    11.0.0upgrade guide

  • Locale routes using [lng] are parameterized, and narrower routes are preferred over catch-alls.

    11.0.0release notes

  • Long task and long animation frame span names remain unchanged.

    11.0.0upgrade guide

  • AMQP instrumentation reports the destination name using this attribute.

    11.0.0upgrade guide

  • AMQP instrumentation reports the message ID using this attribute.

    11.0.0upgrade guide

  • Next.js middleware spans now use the middleware span operation.

    11.0.0release notesupgrade guide

  • Web-server middleware now uses the middleware span operation.

    11.0.0release notesupgrade guide

  • Build-time instrumentation is automatically wired for Next.js projects.

    11.0.0release notesupgrade guide

  • Next.js prerender control flow errors are no longer reported to Sentry.

    11.0.0release notesupgrade guide

  • reactComponentAnnotation behavior is unified across webpack and Turbopack.

    11.0.0upgrade guide

  • Its include options remain integration-level overrides: explicit false excludes a category and explicit true attaches it, subject to allow or deny filtering.

    11.0.0upgrade guide

  • Backend router layers now use the router span operation.

    11.0.0release notes

  • Click idle spans copy this route attribute from the route span.

    11.0.0upgrade guide

  • Component spans retain their original names on this attribute when their span names change.

    11.0.0upgrade guide

  • Span-operation details that previously lived in the op are preserved in attributes including this one.

    11.0.0upgrade guide

  • Function spans for server components emit low-cardinality names.

    11.0.0upgrade guide

  • The silent option now also suppresses the SDK's own build logs.

    11.0.0release notesupgrade guide

  • Span streaming is enabled by default.

    11.0.0release notesupgrade guide

  • Static route span names are now treated as low-cardinality names.

    11.0.0release notesupgrade guide

  • tracePropagationTargets matching is now case-insensitive.

    11.0.0release notesupgrade guide

  • Request data is now available to tracesSampler for edge middleware root spans.

    11.0.0release notesupgrade guide

  • Runs when a span starts, before its final name may be available; match span attributes instead of relying on names.

    11.0.0upgrade guide

  • Unsupported Turbopack warnings are now printed only once.

    11.0.0release notesupgrade guide

  • Click idle spans copy this attribute from the route span.

    11.0.0upgrade guide

  • Click idle spans copy this attribute from the route span; use it for route-path matching in sampling filters.

    11.0.0upgrade guide

  • Click idle spans copy this attribute from the route span.

    11.0.0upgrade guide

  • Cache spans are recorded for use cache functions.

    11.0.0upgrade guide

  • Soft-navigation vitals are enabled by default in stream mode on browsers supporting the Soft Navigations API. Set this option to false to keep one set of vitals for the page lifetime.

    11.0.0upgrade guide

Tooling 1

  • Bundler plugins now use the sentry CLI SDK instead of @sentry/cli.

    11.8.0release notes

Fixes and other changes 16

  • Corrects telemetry timestamps after device sleep by detecting performance clock drift and recalculating span end times.

    11.6.0release notes

  • Pages Router error request URLs now include the configured basePath.

    10.76.1, 11.5.0release notesrelease notes

  • Requests using @sentry/cloudflare no longer initialize Sentry inside the request.

    11.5.0release notes

  • Next.js unauthorized() errors are no longer captured as errors.

    11.5.0release notes

  • Absolute router navigation URLs are no longer incorrectly prefixed with basePath.

    11.1.0release notes

  • The server instrumentation now supports tedious v20.

    11.1.0release notes

  • Turbopack loaders no longer load the Sentry CLI.

    11.1.0release notes

  • Server chunks no longer embed absolute filesystem paths.

    11.0.0release notesupgrade guide

  • CLS DOM paths remain on this attribute.

    11.0.0upgrade guide

  • LCP DOM paths remain on this attribute.

    11.0.0upgrade guide

  • Adds an import.meta.url shim to address an Orchestrion bundling regression in Next.js.

    11.0.0release notesupgrade guide

  • Turbopack development-server stack frames now receive correct in_app attribution.

    11.0.0release notesupgrade guide

  • Tunnel route requests are no longer bypassed by middleware.

    11.0.0release notes

  • Back and forward navigation types are preserved during span streaming.

    11.0.0release notesupgrade guide

  • SourceMappingURL stripping no longer truncates minified chunks.

    11.0.0release notesupgrade guide

  • Event Timing and INP spans keep the annotated component on this attribute in both trace lifecycles.

    11.0.0upgrade guide

@sentry/vue 10256 changes

Breaking changes 27

  • Errors propagated to application code are no longer reported as unhandled before application error handling runs; uncaught errors remain captured globally.

    10.72.0release notes

  • Removes the optional vite peer dependency from server-utils.

    10.60.0release notes

  • dataCollection.userInfo now defaults to true when dataCollection is provided, collecting auto-populated user fields by default.

    10.57.0release notes

  • Request data is migrated to dataCollection, changing how request data collection is configured.

    10.55.0release notes

  • Log-event inference of user data is now gated by sendDefaultPii instead of being enabled by default.

    10.52.0release notes

  • The provider-specific response timestamp attribute was removed without a replacement.

    10.48.0release notes

  • The flags context is now attached only to error events.

    10.48.0release notes

  • The provider-specific attribute was removed; use gen_ai.response.id instead.

    10.48.0release notes

  • The provider-specific attribute was removed; use gen_ai.response.model instead.

    10.48.0release notes

  • The provider-specific response timestamp attribute was removed without a replacement.

    10.48.0release notes

  • The provider-specific attribute was removed; use gen_ai.usage.output_tokens instead.

    10.48.0release notes

  • The provider-specific attribute was removed; use gen_ai.usage.input_tokens instead.

    10.48.0release notes

  • Pino version 9.10 or newer is required to continue receiving Pino logs.

    10.40.0release notes

  • Tracing is removed from the Next.js generation function template.

    10.34.0release notes

  • Always redacts sensitive header content, including when sendDefaultPii is enabled.

    10.27.0release notes

  • The default value of maxValueLength: 250 was removed.

    10.23.0release notes

  • BaseClient was removed; use Client as a direct replacement.

    10.0.0upgrade guiderelease notes

  • The experimental beforeSendLog option is removed.

    10.0.0release notes

  • The experimental enableLogs option is removed.

    10.0.0release notes

  • The option was removed because its behavior is now the default.

    10.0.0upgrade guiderelease notes

  • The option was removed; use the top-level beforeSendLog option instead.

    10.0.0upgrade guide

  • The SDK no longer reports the First Input Delay web vital; remove event-processing logic and alerts that depend on FID or switch them to INP.

    10.0.0upgrade guiderelease notes

  • hasTracingEnabled was removed; use hasSpansEnabled as a direct replacement.

    10.0.0upgrade guiderelease notes

  • The internal logger export in @sentry/core was removed; use debug instead. The Sentry Logging logger export is unaffected.

    10.0.0upgrade guide

  • The Logger type export in @sentry/core was removed; use SentryDebugLogger instead.

    10.0.0upgrade guide

  • The deprecated logger is removed.

    10.0.0release notes

  • OpenTelemetry dependencies and instrumentations were upgraded, changing the Node.js compatibility range; use SDK v9 or @sentry/node-core if you cannot run OpenTelemetry v2.

    10.0.0upgrade guiderelease notes

Security 5

  • Aligned tunnel request matching in middleware with the tunnel rewrite behavior.

    9.47.2, 10.75.2release notesrelease notessecurity advisory

  • Lone surrogates are sanitized in log bodies and attributes before processing or transmission.

    10.54.0release notes

  • Data URLs in http.client spans are sanitized.

    10.36.0release notes

  • Allows sensitive routes to be excluded from injection into the client bundle.

    10.34.0release notes

  • Sentry's sensitive headers are leaked when sendDefaultPii is set to true

    10.27.0security advisory

Deprecations 8

  • Importing withSentryConfig from the existing entry point still works but logs a warning once, encouraging migration to the new path.

    10.73.0release notes

  • The scope.clear() method is deprecated.

    10.71.0release notes

  • sendDefaultPii is deprecated in favor of dataCollection and will be removed in v11.

    10.57.0release notes

  • The streamed fetch performance option is deprecated and replaced by fetchStreamPerformanceIntegration.

    10.54.0release notes

  • The Next.js integration now prints a Turbopack note when deprecated webpack options are used.

    10.33.0release notes

  • Webpack top-level options are deprecated in the Next.js integration; developers should avoid configuring Sentry through these options.

    10.30.0release notes

  • Deprecates transaction-based profiling through profilesSampleRate in favor of UI profiling sessions.

    10.27.0release notes

  • Metric options under _experiments are deprecated but continue working until the next major SDK version.

    10.24.0release notes

New APIs and options 70

  • Accepts a CollectBehavior shorthand for configuring HTTP header data collection.

    10.75.0release notes

  • Adds a new entry point exporting withSentryConfig, allowing next.config imports to remain compatible with the v11 path.

    10.73.0release notes

  • HTTP server spans now include parameterized routes through the http.route attribute.

    10.68.0release notes

  • HTTP server spans now include the complete request URL.

    10.68.0release notes

  • HTTP server spans now include the request URL path.

    10.68.0release notes

  • A new instrumentStateGraph API is available for instrumenting state graphs.

    10.68.0release notes

  • Stack frame variables can now be filtered by variable name.

    10.68.0release notes

  • @sentry/nextjs adds an opt-in for orchestrion instrumentation.

    10.66.0release notes

  • Set this Sentry.init option to opt out of the minimal provider and use OpenTelemetry's full BasicTracerProvider.

    10.64.0release notes

  • A new method lets developers extend integrations.

    10.63.0release notes

  • The async context strategy exposes whether tracing is suppressed.

    10.63.0release notes

  • Resource spans now include the url.full attribute for fuller URL details.

    10.63.0release notes

  • Adds functionality for recording database query summaries.

    10.61.0release notes

  • Adds a top-level API for setting Sentry attributes.

    10.61.0release notes

  • Adds a top-level API for setting multiple Sentry attributes.

    10.61.0release notes

  • Adds an API to bind a Sentry scope to an event emitter.

    10.60.0release notes

  • The dataCollection option lets you control each category of collected data.

    10.57.0release notes

  • Adds a client option for centrally controlling what data SDK features collect and send to Sentry.

    10.54.0release notes

  • Adds an integration for measuring time-to-first-byte and streaming duration of streamed fetch responses.

    10.54.0release notes

  • Adds a top-level applicationKey option to Next.js configuration.

    10.53.0release notes

  • Adds an option to send gen_ai spans separately when transaction payload size limits would otherwise drop them.

    10.53.0release notes

  • A client lifecycle hook now lets applications react when a replay session ends.

    10.50.0release notes

  • A client lifecycle hook now lets applications react when a replay session starts.

    10.50.0release notes

  • A tracing utility was added to propagate context across operations.

    10.50.0release notes

  • AI integrations can control whether large AI inputs and outputs are truncated.

    10.49.0release notes

  • Exposes rewriteSources as a top-level configuration option.

    10.49.0release notes

  • Adds an integration that captures the DOM structure when an error occurs for debugging.

    10.49.0release notes

  • Adds instrumentation for LangChain embeddings, creating gen_ai.embeddings spans; use this API in runtimes without automatic instrumentation.

    10.48.0release notes

  • The MCP integration now supports registerPrompt.

    10.48.0release notes

  • The MCP integration now supports registerResource.

    10.48.0release notes

  • The MCP integration now supports registerTool.

    10.48.0release notes

  • Adds instrumentation for Vercel queues in Next.js applications.

    10.44.0release notes

  • Adds experimental Turbopack React component name annotation for Next.js 16+, enabling component names in Replays, breadcrumbs, and performance monitoring.

    10.43.0release notes

  • Adds an experimental application key for enabling third-party error filtering in Turbopack builds.

    10.41.0release notes

  • A top-level option now controls which source map files are deleted after upload.

    10.40.0release notes

  • Enables automatic creation of Sentry cron monitors for Vercel Cron Jobs.

    10.39.0release notes

  • Adds an API to set a conversation ID that is automatically applied to spans, linking traces from the same multi-turn AI conversation.

    10.37.0release notes

  • Database spans support the db.system.name attribute.

    10.36.0release notes

  • Prisma v7 is supported by the Sentry integration.

    10.36.0release notes

  • Client reports can now identify ignored events with the ignored drop reason.

    10.35.0release notes

  • Enables additional context in fetch error messages to help with debugging.

    10.34.0release notes

  • OpenAI and LangChain instrumentation now adds the gen_ai.conversation.id attribute.

    10.33.0release notes

  • Tracing now adds gen_ai.request.messages.original_length attributes.

    10.33.0release notes

  • thirdPartyErrorFilterIntegration now supports ignoring Sentry internal frames during third-party error filtering.

    10.33.0release notes

  • WASM stack frames can receive an application key for first-party detection by thirdPartyErrorFilterIntegration.

    10.33.0release notes

  • Replay can attach raw request bodies from Request objects passed as the first fetch argument.

    10.32.0release notes

  • SDK scope attributes are applied to logs while their respective scopes are active.

    10.32.0release notes

  • Webpack tree-shaking flags can now be configured for the Next.js SDK.

    10.32.0release notes

  • Exports parameter types for captureException and captureMessage for use by TypeScript consumers.

    10.31.0release notes

  • Postgres.js instrumentation now supports ESM usage.

    10.31.0release notes

  • Adds the propagateTraceparent option for Node integrations.

    10.31.0release notes

  • Adds tracing support for AzureOpenAI.

    10.27.0release notes

  • Adds gibibyte and pebibyte values to the InformationUnit type.

    10.27.0release notes

  • Adds the manual UI profiling lifecycle mode, which is now the default and enables explicit profile control.

    10.27.0release notes

  • Introduces profileSessionSampleRate as the replacement for deprecated transaction-based profiling.

    10.27.0release notes

  • Adds APIs for working with scope attributes.

    10.27.0release notes

  • Adds an API to manually start UI profiling.

    10.27.0release notes

  • Adds support for universal random tunnel paths in Next.js.

    10.27.0release notes

  • Adds support for instrumenting LangGraph StateGraph operations in Node.

    10.26.0release notes

  • The Node instrumentation supports OpenAI SDK v6 integrations.

    10.26.0release notes

  • Adds beforeSendMetric as a top-level option for metric processing.

    10.24.0release notes

  • Adds enableMetrics as a top-level option for controlling metric sending.

    10.24.0release notes

  • Added automatic instrumentation for Firebase v2 Cloud Functions when tracing is enabled, providing performance tracking and error monitoring.

    10.22.0release notes

  • Added LangChain instrumentation support for Cloudflare and Vercel Edge environments.

    10.22.0release notes

  • Proxy files can now use the Node runtime, expanding runtime choices for Next.js proxy implementations.

    10.22.0release notes

  • Added LangChain AI instrumentation configurable through Sentry.langChainIntegration.

    10.22.0release notes

  • Added recordInputs to control whether prompts and messages are recorded by LangChain instrumentation.

    10.22.0release notes

  • Added recordOutputs to control whether LangChain responses are recorded.

    10.22.0release notes

  • Next.js proxy files are now supported by the integration.

    10.21.0release notes

  • Adds strictTraceContinuation.

    10.0.0release notes

Behavior and default changes 56

  • Attachments are excluded from internal exception events, preventing them from being included in those events.

    10.76.2release notes

  • Token usage is normalized while cache breakdowns are preserved for more consistent AI telemetry.

    10.76.2release notes

  • The SDK no longer instruments its own envelope requests, avoiding self-instrumentation.

    10.75.0release notes

  • The Pages Router runtime is excluded from App Router client bundles, reducing unintended client bundle content.

    10.74.0release notes

  • Vercel AI span processors are registered on Next.js for proper AI span processing.

    10.74.0release notes

  • The enableLogs client option now defaults to true, enabling Sentry Logs when logging APIs or integrations are actively used; set it to false to opt out.

    10.71.0release notes

  • Anthropic client instrumentation now instruments the client in place instead of using a deep proxy.

    10.68.0release notes

  • Dataloader spans now include a cache.key attribute for identifying the associated cache key.

    10.68.0release notes

  • Redis delete operations are captured as cache.remove operations.

    10.68.0release notes

  • Core fetch instrumentation now records the complete request URL.

    10.68.0release notes

  • Pageload and navigation spans now include url attributes, improving URL context in Next.js tracing data.

    10.65.0release notes

  • The Node SDK now uses Sentry's minimal tracer provider by default, reducing overhead when the full OpenTelemetry tracing stack is unnecessary.

    10.64.0release notes

  • Root-span sampling contexts now receive normalizedRequest for sampling decisions.

    10.63.0release notes

  • vercelAiIntegration now supports v7 of the ai package, though v7 is not yet supported on Cloudflare.

    10.62.0release notes

  • AI message data is no longer truncated by default because streamed gen AI spans are not constrained by transaction size limits.

    10.61.0release notes

  • Gen AI spans are streamed by default, preventing them from being dropped when transaction payloads exceed size limits.

    10.61.0release notes

  • Gen AI message truncation is disabled by default when streamed Gen AI spans are enabled.

    10.59.0release notes

  • Streamed spans now use production as the default sentry.environment attribute value.

    10.59.0release notes

  • TwP sampling is deferred by reading trace state from the scope.

    10.59.0release notes

  • The ContextLines integration now uses dataCollection.frameContextLines.

    10.57.0release notes

  • dataCollection.httpBodies now defaults to all valid body types.

    10.57.0release notes

  • Primitive arrays are accepted as attribute values, while arrays with non-primitive elements are dropped; log and metric arrays are sent as actual arrays.

    10.54.0release notes

  • The Next.js project option type now accepts either a string or an array of strings.

    10.54.0release notes

  • Unwanted segments are filtered when span streaming is enabled.

    10.51.0release notes

  • Sentry now sets a global attribute indicating whether Turbopack is being used.

    10.51.0release notes

  • Discarded spans requiring a parent now emit a no_parent_span client outcome.

    10.50.0release notes

  • The google-genai integration no longer emits spans for chats.create.

    10.48.0release notes

  • Aligns Turbopack module metadata injection with webpack behavior, improving consistency for Next.js builds.

    10.43.0release notes

  • The Consola integration extracts the first-parameter object as searchable attributes.

    10.42.0release notes

  • A new page session lifecycle keeps the initial session across soft navigations until a hard refresh.

    10.40.0release notes

  • Capturing an exception with captureUnderscoreErrorException now exposes an event ID.

    10.39.0release notes

  • The Next.js integration now sets the Cloudflare runtime.

    10.39.0release notes

  • DebugID injection is turned off when sourcemaps are explicitly disabled, preventing unwanted instrumentation in that configuration.

    10.38.0release notes

  • Updates the default ignore list used for sourcemaps in Next.js projects.

    10.37.0release notes

  • DSNs can now use IPv6 hosts.

    10.33.0release notes

  • Scope attributes are now applied to metrics while the respective scopes are active; string, number, and boolean values are supported.

    10.33.0release notes

  • The Next.js integration now emits a warning when treeshaking and debug settings conflict.

    10.33.0release notes

  • Tracing and error monitoring now work automatically with Vercel AI SDK v6.

    10.33.0release notes

  • Cookie headers are now parsed into individual cookies.

    10.31.0release notes

  • The span attribute now contains only the GraphQL query string instead of the full JSON request payload.

    10.31.0release notes

  • Now supports GraphQL persisted operations by capturing the operation hash and protocol version as span attributes.

    10.31.0release notes

  • Inline media is stripped from tracing messages.

    10.31.0release notes

  • cacheComponents is now supported on Turbopack builds.

    10.28.0release notes

  • Next.js integrations add detection for Cloudflare's waitUntil capability.

    10.28.0release notes

  • Adds buffering for incoming client events.

    10.27.0release notes

  • Server-side transaction events now include the request URL, providing additional transaction context.

    10.26.0release notes

  • Request string inputs are truncated in the OpenAI integration to limit captured request data.

    10.25.0release notes

  • Spotlight is now included in development bundles, making development-time Spotlight functionality available by default.

    10.25.0release notes

  • The Next.js integration now deletes CSS map files.

    10.24.0release notes

  • Metrics are now enabled by default, although integrations do not automatically emit metrics.

    10.24.0release notes

  • The browser transport buffer is now limited in size.

    10.23.0release notes

  • Server SDK envelope requests now send a user-agent header.

    10.23.0release notes

  • AI integrations now truncate request messages, limiting the size of recorded request data.

    10.22.0release notes

  • Passes requestHook through to OpenTelemetry instrumentation.

    10.22.0release notes

  • Passes responseHook through to OpenTelemetry instrumentation.

    10.22.0release notes

  • Preparation for the Next.js 16 bundler default may affect bundler-related project decisions.

    10.20.0release notes

Tooling 5

  • Immutable browser chunks are now included in uploaded assets, improving source map or asset upload coverage for Next.js builds.

    10.64.0release notes

  • Published packages now include subpath type shims, improving type resolution for subpath imports.

    10.53.1release notes

  • Turbopack loaders now use the not: foreign condition.

    10.41.0release notes

  • Experimental support was added for using thirdPartyErrorFilterIntegration with Turbopack builds in Next.js 16+.

    10.41.0release notes

  • Next.js applications using Turbopack can use native Debug IDs for improved source map resolution and error tracking.

    10.20.0release notes

Fixes and other changes 85

  • HTTP spans named after the request method are detected correctly, improving HTTP span instrumentation.

    10.76.2release notes

  • Resolves the Next.js version relative to the SDK when the current working directory differs.

    10.75.1release notes

  • Sourcemap upload now includes only emitted chunk directories, preventing unrelated directories from being uploaded.

    10.75.0release notes

  • SDK imports no longer crash under jsdom or happy-dom environments.

    10.74.0release notes

  • Auto-instrumentation now supports OpenAI v7, allowing applications using that package version to be instrumented correctly.

    10.72.0release notes

  • Child span tracking is bounded on long-lived spans, preventing unbounded tracking over their lifetime.

    10.71.0release notes

  • Tracing is no longer added to middleware wrappers, preventing unintended tracing behavior.

    10.70.0release notes

  • Fixed a meriyah issue affecting standalone builds in Next.js.

    10.70.0release notes

  • Baggage with the string value undefined is no longer propagated when dynamic sampling context is missing.

    10.68.0release notes

  • The integration no longer causes infinite recursions.

    10.68.0release notes

  • Internal chunk frames are now marked as not in_app, improving frame classification in Next.js events.

    10.67.0release notes

  • Root spans created by Middleware.execute are now handled correctly when Next.js middleware runs on the Node.js runtime.

    10.64.0release notes

  • Inferred fragment attributes no longer retain a leading hash.

    10.63.0release notes

  • Inferred query attributes no longer retain a leading question mark.

    10.63.0release notes

  • Streamed span status messages are serialized to the sentry.status.message attribute.

    10.63.0release notes

  • Browser session envelopes are deferred until the browser is idle.

    10.63.0release notes

  • Trace meta tags are no longer injected when Next.js Cache Components is enabled.

    10.63.0release notes

  • Node runtime no longer fails when tracingChannel is unavailable.

    10.62.0release notes

  • Ensures url.full and http.url have identical values on client HTTP spans.

    10.60.0release notes

  • Avoids directly importing tracingChannel to maintain compatibility with Node v18.

    10.60.0release notes

  • Outgoing HTTP instrumentation no longer crashes when requests use // paths.

    10.59.0release notes

  • Safe random ID context is registered at module load to ensure it is available when needed.

    10.59.0release notes

  • Redirect server actions are marked as ok instead of internal_error.

    10.58.0release notes

  • pinoIntegration is now shimmed on the edge runtime, preventing edge-runtime integration issues.

    10.57.0release notes

  • __SENTRY_SERVER_MODULES__ is read lazily so Turbopack injection is honored.

    10.57.0release notes

  • Correctly parses sampleRate when consistent trace sampling is enabled.

    10.56.0release notes

  • DOMException instances with empty stack traces now receive a synthetic stack trace when attachStacktrace is enabled.

    10.54.0release notes

  • Internal frame detection is corrected for minified browser bundles, improving stack trace processing.

    10.54.0release notes

  • User data is no longer gated when streamed spans are read from scope.

    10.53.1release notes

  • Next.js build modification is skipped when SRI is enabled, preventing incompatible build changes.

    10.52.0release notes

  • Tunnel endpoint matching is narrowed to avoid matching endpoints too broadly.

    10.51.0release notes

  • GraphQL client spans are now enriched correctly when requests use relative URLs.

    10.50.0release notes

  • Outgoing request span attributes are now protected against null httpVersion values.

    10.50.0release notes

  • Implausible Largest Contentful Paint values are now filtered.

    10.50.0release notes

  • Promise rejection handling now records the rejection reason instead of the Promise as originalException.

    10.50.0release notes

  • Correlation handling now works correctly for stateless MCP wrapper transports.

    10.50.0release notes

  • Custom browser tracing setup is skipped for bot user agents.

    10.49.0release notes

  • Turbopack loaders now preserve directive prologues during processing.

    10.49.0release notes

  • MCP tool spans now receive error status when a tool returns a JSON-RPC error response.

    10.48.0release notes

  • Tracing now skips tunnel requests, preventing tunnel traffic from being included in application traces.

    10.45.0release notes

  • Logs the correct lastEventId when an error is thrown during component rendering.

    10.44.0release notes

  • Removes sourceMappingURL comments after source maps are deleted in Turbopack builds.

    10.44.0release notes

  • promiseBuffer is no longer removed entirely.

    10.42.0release notes

  • Trailing slashes are normalized in App Router route parameterization.

    10.40.0release notes

  • The environment from options is now applied when set.

    10.40.0release notes

  • SSR pages now return the correct last event ID.

    10.40.0release notes

  • Session user IDs are now consistently set, and the first soft navigation starts a new session correctly.

    10.40.0release notes

  • When enabled, spans no longer receive the sentry.drop_transaction attribute.

    10.40.0release notes

  • Non-transaction events now receive the parameterized transaction name.

    10.40.0release notes

  • The SENTRY_SERVER_MODULES value is now populated when using Turbopack.

    10.39.0release notes

  • Serverless environments receive fallback ALS runners.

    10.36.0release notes

  • Profiling debug ID matching is corrected.

    10.36.0release notes

  • Fetch options are shallow-cloned to prevent mutation.

    10.35.0release notes

  • IP address detection now finds the correct address regardless of case.

    10.35.0release notes

  • Vercel AI spans are detected by checking for the AI operation id.

    10.35.0release notes

  • Failed client reports no longer produce outcomes.

    10.34.0release notes

  • Client option types now allow explicitly passing undefined.

    10.33.0release notes

  • AI spans now receive operations when only a model ID is available.

    10.31.0release notes

  • Node-cron context is now passed through correctly.

    10.31.0release notes

  • Google GenAI tracing now includes the system prompt and model.

    10.31.0release notes

  • Anthropic AI message spans now include the system message.

    10.29.0release notes

  • Pino integration now supports the msg field, improving log capture for applications using Pino.

    10.29.0release notes

  • Vercel AI spans now include previously missing attributes.

    10.29.0release notes

  • Corrects the return type of beforeSendMetric.

    10.27.0release notes

  • Re-adds the _experiments.enableLogs option.

    10.27.0release notes

  • Fixes local-variable capture for out-of-app stack frames.

    10.27.0release notes

  • Applies maxValueLength when processing error messages.

    10.27.0release notes

  • The ISR route cache now uses an LRU map to manage cached routes.

    10.26.0release notes

  • Meta trace tags are dropped when the rendered page uses ISR.

    10.26.0release notes

  • Middleware files are no longer wrapped when Next.js runs in standalone mode.

    10.26.0release notes

  • Development error symbolication now respects the PORT environment variable.

    10.26.0release notes

  • Session status updates from events with exceptions now consider only the exception mechanism.

    10.25.0release notes

  • Replay ignores background-image when blockAllMedia is enabled.

    10.24.0release notes

  • Exception objects now include all keys instead of truncating them.

    10.24.0release notes

  • The Next.js integration stops accessing synchronous props in its template.

    10.24.0release notes

  • The Next.js proxy template wrapping was updated.

    10.23.0release notes

  • Corrected async types when instrumenting Anthropic's streaming API.

    10.22.0release notes

  • Removed chalk usage in Next.js integration to prevent runtime errors.

    10.22.0release notes

  • Bundler detection in the Next.js integration was updated.

    10.21.0release notes

  • The integration no longer sets the experimental instrumentation hook flag for Next.js 16.

    10.21.0release notes

  • Transaction naming for internationalized routing is now consistent.

    10.21.0release notes

  • Fixes route manifest creation when a basePath is configured.

    10.20.0release notes

  • URL extraction handles async params.

    10.0.0release notes

  • Stackframe calls are updated for Next.js 15.5.

    10.0.0release notes

  • Route handlers now flush events.

    10.0.0release notes

@sentry/vue 943 changes

Breaking changes 34

  • The method was removed; use the openTelemetryInstrumentations option in Sentry.init or a custom Sentry Client instead.

    9.0.0upgrade guide

  • The option was removed. Session tracking is handled by browserSessionIntegration or httpIntegration, and processSessionIntegration replaces automatic per-process sessions in Node.js.

    9.0.0upgrade guide

  • Client classes now have to extend BaseClient.

    9.0.0upgrade guide

  • The hook can no longer drop spans by returning null; use integrations to control which spans are recorded.

    9.0.0upgrade guide

  • The hook now receives root spans as well as child spans, so existing hooks may need to account for the additional input.

    9.0.0upgrade guide

  • Use this integration to enable browser session tracking; remove it to disable session tracking in browser environments.

    9.0.0upgrade guide

  • With attachStacktrace: true in Sentry.init, console messages are now marked handled; set handled: false on the integration to keep sending them as unhandled.

    9.0.0upgrade guide

  • Use captureFeedback instead of captureUserFeedback, and provide the feedback text in the message field rather than comments.

    9.0.0upgrade guide

  • The method was removed; use captureFeedback and change the comments field to message.

    9.0.0upgrade guide

  • Client usages now require BaseClient instances; the abstract Client class was removed and client classes must extend BaseClient.

    9.0.0upgrade guide

  • The integration was removed; use hook options such as beforeSend or beforeSendTransaction to log outgoing events.

    9.0.0upgrade guide

  • SDK code may now use ES2020 features. Runtimes that do not support them may require SDK transpilation.

    9.0.0upgrade guide

  • The option was removed; set tracesSampleRate to 1 or 0 instead.

    9.0.0upgrade guide

  • The experimental_captureRequestError option was removed.

    9.0.0release notes

  • The getCurrentHub API was removed from the SDK.

    9.0.0upgrade guide

  • The getCurrentHubShim API was removed from the SDK.

    9.0.0upgrade guide

  • Use httpIntegration for server session tracking; set trackIncomingRequestsAsSessions to false to disable it.

    9.0.0upgrade guide

  • The Hub API was removed from the SDK.

    9.0.0upgrade guide

  • The previous metrics beta API has been removed; a new Metrics feature is available in the latest SDK versions.

    9.0.0upgrade guide

  • The minimum supported browser versions now include Chrome 80, Edge 80, Safari 14, iOS Safari 14.4, Firefox 74, Opera 67, and Samsung Internet 13.0.

    9.0.0upgrade guide

  • Node.js >=18 is now the minimum supported version.

    9.0.0release notes

  • Use this Sentry.init option or a custom Sentry Client to provide OpenTelemetry instrumentations.

    9.0.0upgrade guide

  • This integration replaces automatic session creation for every Node.js process when autoSessionTracking was true, and is configured by default.

    9.0.0upgrade guide

  • Use this property instead of samplingContext.request; its type differs from request.

    9.0.0upgrade guide

  • The request property was removed from the samplingContext argument to tracesSampler and profilesSampler; use samplingContext.normalizedRequest instead.

    9.0.0upgrade guide

  • The property was removed; object attributes are now available at the top level of samplingContext.

    9.0.0upgrade guide

  • Scope usages now require Scope instances rather than structurally similar values.

    9.0.0upgrade guide

  • The SDK no longer instructs the Sentry backend to automatically infer IP addresses by default; set sendDefaultPii: true to request IP inference.

    9.0.0upgrade guiderelease notes

  • The package is no longer published on the deno.land registry; import it from npm instead.

    9.0.0upgrade guide

  • The package is no longer published; its exports and APIs have moved to @sentry/core, except for APIs explicitly removed in the migration guide.

    9.0.0upgrade guide

  • The integration was removed; use Sentry.setContext() to capture session durations alongside events.

    9.0.0upgrade guide

  • A custom scope passed to startSpan is cloned in v9, so scope changes made through the active scope remain within the callback; modify the custom scope directly to persist changes outside it.

    9.0.0upgrade guide

  • Passing undefined is treated the same as leaving the option undefined, so negative sampling decisions are no longer propagated in this case.

    9.0.0upgrade guide

  • The minimum required TypeScript version is increased to 5.0.4.

    9.0.0upgrade guide

Deprecations 1

  • The package remains published but is deprecated, its API will not be extended, and it will not be published in future major versions.

    9.0.0upgrade guide

New APIs and options 1

  • An option was added to skip requestAnimationFrame for canvas snapshots.

    9.47.0release notes

Behavior and default changes 1

  • Release names no longer rely on the Next.js Build ID.

    9.0.0release notes

Tooling 1

  • The SDK uses the batched devserver symbolication endpoint.

    9.0.0release notes

Fixes and other changes 5

  • Logs no longer suffer flush timeout starvation during continuous logging.

    9.47.1release notes

  • Logs beyond MAX_LOG_BUFFER_SIZE are no longer swallowed.

    9.47.0release notes

  • captureRequestError flushes with waitUntil.

    9.0.0release notes

  • The SDK respects user-provided source map generation settings.

    9.0.0release notes

  • The sourcemaps.disable setting is forwarded directly to the webpack plugin.

    9.0.0release notes

@sentry/vue 846 changes

Breaking changes 35

  • The function was removed in favor of adding an event processor to the global scope.

    8.0.0upgrade guide

  • Use the function-based browser tracing integration instead of constructing BrowserTracing.

    8.0.0release notes

  • Integrations are functions rather than classes; class construction and access through the Integrations.XXX hash are replaced by functional integrations.

    8.0.0upgrade guide

  • Deprecations from the v7 cycle were removed, except for getCurrentHub(), and can no longer be used in v8.

    8.0.0release notes

  • The SDK now requires ES2018 compatibility and support for globalThis; older environments may need transpilation and polyfills.

    8.0.0upgrade guide

  • Metrics APIs no longer require enabling the metrics aggregator through this experimental option.

    8.0.0upgrade guide

  • The SDK requires the fetch API because makeFetchTransport is the only available transport.

    8.0.0upgrade guide

  • The property now removes the specified number of frames from the parsed stack, rather than lines from the stack string.

    8.0.0upgrade guide

  • Use this function in place of the removed spanStatusfromHttpCode function.

    8.0.0upgrade guide

  • The XHR transport was removed; only makeFetchTransport is available, so the environment must provide fetch.

    8.0.0upgrade guide

  • The @sentry/migr8 migration codemod requires Node 18 or later.

    8.0.0upgrade guide

  • The minimum supported Node.js version is 14.8.0.

    8.0.0release notes

  • Full support for ESM-based Node.js apps requires Node.js 18.19.0 or higher.

    8.0.0release notes

  • The Offline integration was removed in favor of the offline transport wrapper.

    8.0.0upgrade guide

  • Import and initialize the SDK before any other import so auto-instrumentation works.

    8.0.0release notes

  • The package was removed and will no longer be published; pluggable integrations moved to @sentry/browser as functions.

    8.0.0upgrade guide

  • The package is no longer required; import Replay methods directly from the SDK and use its functional integration.

    8.0.0upgrade guide

  • The top-level function was removed; use Sentry.getCurrentScope() to access and mutate the current scope.

    8.0.0upgrade guide

  • Add an event processor to the global scope using this API in place of addGlobalEventProcessor.

    8.0.0upgrade guide

  • Replay integration is now functional instead of class-based.

    8.0.0upgrade guide

  • The export was removed and has no replacement API.

    8.0.0upgrade guide

  • The Severity enum was removed; use the SeverityLevel type directly.

    8.0.0upgrade guide

  • SDK packages no longer export the Span class, which is not intended for direct user use.

    8.0.0upgrade guide

  • The revamped custom tracing instrumentation API removes span.startChild.

    8.0.0upgrade guide

  • The function was removed in favor of getSpanStatusFromHttpCode.

    8.0.0upgrade guide

  • The revamped custom tracing instrumentation API removes startTransaction.

    8.0.0upgrade guide

  • In browsers, when unset, tracing headers are attached to same-origin outgoing requests rather than targets matching the previous localhost and relative-URL defaults.

    8.0.0upgrade guide

  • Configured entries are now matched against the full outgoing request URL instead of only the request argument.

    8.0.0upgrade guide

  • The callback receives name and attributes directly instead of transactionContext; attributes reflect span-creation time and may omit later-set values.

    8.0.0upgrade guide

  • The option was removed in favor of tracePropagationTargets, which is set in Sentry.init() or custom Client options.

    8.0.0upgrade guide

  • The Transaction integration was removed from @sentry/integrations and has no replacement API.

    8.0.0upgrade guide

  • The Next.js SDK no longer supports this option; configure Webpack and Next.js to down-compile the SDK if older browsers must be supported.

    8.0.0release notes

  • The send method must return a promise of TransportMakeRequestResponse; void is no longer allowed.

    8.0.0upgrade guide

  • The Replay option now defaults to an empty array, so set it explicitly to use it.

    8.0.0upgrade guide

  • The Replay option now defaults to an empty array, so set it explicitly to use it.

    8.0.0upgrade guide

Deprecations 2

  • getCurrentHub remains available for now but is deprecated and will be removed in the next major version in favor of the new Scope API.

    8.0.0upgrade guide

  • Hub remains available for now but is deprecated and will be removed in the next major version in favor of the new Scope API.

    8.0.0upgrade guide

New APIs and options 1

  • Use this utility to check whether Sentry was initialized, rather than relying on getClient().

    8.0.0upgrade guide

Behavior and default changes 4

  • The SDK now filters gmo errors and Facebook mobile errors.

    8.55.1release notes

  • The integration now examines error.cause by default.

    8.0.0upgrade guide

  • After Sentry.init() has been called, getClient() always returns a client; use Sentry.isInitialized() to check initialization.

    8.0.0upgrade guide

  • Browser metrics APIs no longer require adding this integration to the integrations array.

    8.0.0upgrade guide

Tooling 1

  • Run the migration codemod to automatically update many deprecated SDK usages; it requires Node 18 or later.

    8.0.0upgrade guide

Fixes and other changes 3

  • The install script again builds binaries from source, restoring successful installation behavior for profiling-related packages.

    8.55.2release notes

  • Performance measure spans now always have a positive duration.

    8.55.1release notes

  • The performance monitoring and tracing API has been streamlined.

    8.0.0release notes

@sentry/vue 72 changes

Breaking changes 1

  • The Integrations.BrowserTracing export was removed from @sentry/nextjs; import BrowserTracing from @sentry/nextjs directly.

    7.0.0release notes

Performance 1

  • The webpack plugin and CLI binary detection were changed, which should reduce bundle size of NextJS applications.

    7.0.0release notes

@sentry/vue 63 changes

Breaking changes 1

  • Session tracking is enabled by default for SDKs that support sending session data; set autoSessionTracking to false during SDK initialization to opt out.

    6.0.0release notes

New APIs and options 1

  • Set autoSessionTracking to false during SDK initialization to opt out of session tracking.

    6.0.0release notes

Behavior and default changes 1

@sentry/vue 532 changes

Breaking changes 20

  • The utility is removed in favor of Object.assign.

    5.0.0release notes

  • The browser beacon transport is removed.

    5.0.0release notes

  • BrowserBackend is removed from the default export.

    5.0.0release notes

  • The Dedupe integration becomes optional and is no longer enabled by default.

    5.0.0release notes

  • Mechanism is moved to Exception.

    5.0.0release notes

  • Events created from exceptions no longer have a top-level message attribute.

    5.0.0release notes

  • The utility is removed in favor of native includes.

    5.0.0release notes

  • The install function is removed from the integration interface.

    5.0.0release notes

  • The utility is removed in favor of Array.isArray.

    5.0.0release notes

  • The utility is removed in favor of checking typeof === 'function'.

    5.0.0release notes

  • The utility is removed in favor of Number.isNaN.

    5.0.0release notes

  • The utility is removed in favor of checking === void 0.

    5.0.0release notes

  • The utility is renamed from serializeKeysToEventMessage.

    5.0.0release notes

  • Default client fingerprinting for messages is removed.

    5.0.0release notes

  • The utility is renamed from safeNormalize and its internals are rewritten.

    5.0.0release notes

  • The utility is renamed from limitObjectDepthToSize and its internals are rewritten.

    5.0.0release notes

  • The SDK information integration is removed.

    5.0.0release notes

  • The transport function is renamed from captureEvent to sendEvent and receives an Event instead of stringified data.

    5.0.0release notes

  • Pluggable integrations, including extraErrorData, are extracted into a separate package.

    5.0.0release notes

  • The serialize, deserialize, clone, and serializeObject functions are removed.

    5.0.0release notes

New APIs and options 7

  • A new hub method is introduced to clear breadcrumbs.

    5.0.0release notes

  • A utility to identify synthetic events is introduced.

    5.0.0release notes

  • This option adjusts the maximum string length for values; its default is 250.

    5.0.0release notes

  • A package is introduced with functions to attach opentracing data to Sentry Events.

    5.0.0release notes

  • A new hub method is introduced to set extras.

    5.0.0release notes

  • A new hub method is introduced to set tags.

    5.0.0release notes

  • A synthetic field is added to Mechanism in exception.

    5.0.0release notes

Behavior and default changes 3

  • The close method disables the client once it has been flushed.

    5.0.0release notes

  • ESM builds use the es6 target instead of esnext.

    5.0.0release notes

  • The module field is exposed as the entry point for ESM builds.

    5.0.0release notes

Fixes and other changes 2