7.105.0

Important Changes

• feat: Ensure withActiveSpan is exported everywhere (#10877)

You can use the withActiveSpan method to ensure a certain span is the active span in a given callback. This can be used to create a span as a child of a specific span with the startSpan API methods:

const parentSpan = Sentry.startInactiveSpan({ name: 'parent' });
if (parentSpan) {
  withActiveSpan(parentSpan, () => {
    // This will be a direct child of parentSpan
    const childSpan = Sentry.startInactiveSpan({ name: 'child' });
  });
}

7.104.0

Important Changes

• feat(performance): create Interaction standalone spans on inp events (#10709)

This release adds support for the INP web vital. This is currently only supported for Saas Sentry, and product support is released with the upcoming 24.3.0 release of self-hosted.

To opt-in to this feature, you can use the enableInp option in the browserTracingIntegration:

Sentry.init({
  integrations: [
    Sentry.browserTracingIntegration({
      enableInp: true,
    });
  ]
})

Other Changes

• feat(feedback): Flush replays when feedback form opens (#10567)
• feat(profiling-node): Expose nodeProfilingIntegration (#10864)
• fix(profiling-node): Fix dependencies to point to current versions (#10861)
• fix(replay): Add errorHandler for replayCanvas integration (#10796)

7.103.0

Important Changes

• feat(core): Allow to pass forceTransaction to startSpan() APIs (#10819)

You can now pass forceTransaction: true to startSpan(), startSpanManual() and startInactiveSpan(). This allows you to start a span that you want to be a transaction, if possible. Under the hood, the SDK will connect this span to the running active span (if there is one), but still send the new span as a transaction to the Sentry backend, if possible, ensuring it shows up as a transaction throughout the system.

Please note that setting this to true does not guarantee that this will be sent as a transaction, but that the SDK will try to do so. You can enable this flag if this span is important to you and you want to ensure that you can see it in the Sentry UI.

Other Changes

• fix: Make breadcrumbs option optional in WinterCGFetch integration (#10792)

7.102.1

• fix(performance): Fixes latest route name and source for interactions not updating properly on navigation (#10702)
• fix(tracing): Guard against missing window.location (#10659)
• ref: Make span types more robust (#10660)
• ref(remix): Make @remix-run/router a dependency (v7) (#10779)

7.102.0

• fix: Export session API (#10712)
• fix(core): Fix scope capturing via captureContext function (#10737)

7.101.1

In version 7.101.0 the @sentry/hub package was missing due to a publishing issue. This release contains the package again.

• fix(nextjs): Remove webpack:// prefix more broadly from source map sources field (#10641)

7.101.0

• feat: Export semantic attribute keys from SDK packages (#10637)
• feat(core): Add metric summaries to spans (#10554)
• feat(core): Deprecate the Hub constructor (#10584)
• feat(core): Make custom tracing methods return spans & set default op (#10633)
• feat(replay): Add getReplay utility function (#10510)
• fix(angular-ivy): Add exports field to package.json (#10569)
• fix(sveltekit): Avoid capturing Http 4xx errors on the client (#10571)
• fix(sveltekit): Properly await sourcemaps flattening (#10602)

7.100.1

This release contains build fixes for profiling-node.

• build(profiling-node): make sure debug build plugin is used #10534
• build: Only run profiling e2e test if bindings have changed #10542
• fix(feedback): Replay breadcrumb for feedback events was incorrect #10536

7.100.0

Important Changes

Deprecations

This release includes some deprecations. For more details please look at our migration guide.

The deprecation most likely to affect you is the one of BrowserTracing. Instead of new BrowserTracing(), you should now use browserTracingIntegration(), which will also handle framework-specific instrumentation out of the box for you - no need to pass a custom routingInstrumentation anymore. For @sentry/react, we expose dedicated integrations for the different react-router versions:

• reactRouterV6BrowserTracingIntegration()
• reactRouterV5BrowserTracingIntegration()
• reactRouterV4BrowserTracingIntegration()
• reactRouterV3BrowserTracingIntegration()

See the migration guide for details.

• feat(angular): Export custom browserTracingIntegration() (#10353)
• feat(browser): Deprecate BrowserTracing integration (#10493)
• feat(browser): Export browserProfilingIntegration (#10438)
• feat(bun): Export bunServerIntegration() (#10439)
• feat(nextjs): Add browserTracingIntegration (#10397)
• feat(react): Add reactRouterV3BrowserTracingIntegration for react router v3 (#10489)
• feat(react): Add reactRouterV4/V5BrowserTracingIntegration for react router v4 & v5 (#10488)
• feat(react): Add reactRouterV6BrowserTracingIntegration for react router v6 & v6.4 (#10491)
• feat(remix): Add custom browserTracingIntegration (#10442)
• feat(node): Expose functional integrations to replace classes (#10356)
• feat(vercel-edge): Replace WinterCGFetch with winterCGFetchIntegration (#10436)
• feat: Deprecate non-callback based continueTrace (#10301)
• feat(vue): Deprecate new VueIntegration() (#10440)
• feat(vue): Implement vue browserTracingIntegration() (#10477)
• feat(sveltekit): Add custom browserTracingIntegration() (#10450)

Profiling Node

@sentry/profiling-node has been ported into the monorepo. Future development for it will happen here!

• pkg(profiling-node): port profiling-node repo to monorepo (#10151)

Other Changes

• feat: Export setHttpStatus from all packages (#10475)
• feat(bundles): Add pluggable integrations on CDN to Sentry namespace (#10452)
• feat(core): Pass name & attributes to tracesSampler (#10426)
• feat(feedback): Add system-ui to start of font family (#10464)
• feat(node-experimental): Add koa integration (#10451)
• feat(node-experimental): Update opentelemetry packages (#10456)
• feat(node-experimental): Update tracing integrations to functional style (#10443)
• feat(replay): Bump rrweb to 2.10.0 (#10445)
• feat(replay): Enforce masking of credit card fields (#10472)
• feat(utils): Add propagationContextFromHeaders (#10313)
• fix: Make startSpan, startSpanManual and startInactiveSpan pick up the scopes at time of creation instead of termination (#10492)
• fix(feedback): Fix logo color when colorScheme is "system" (#10465)
• fix(nextjs): Do not report redirects and notFound calls as errors in server actions (#10474)
• fix(nextjs): Fix navigation tracing on app router (#10502)
• fix(nextjs): Apply server action data to correct isolation scope (#10514)
• fix(node): Use normal require call to import Undici (#10388)
• ref(nextjs): Remove internally used deprecated APIs (#10453)
• ref(vue): use startInactiveSpan in tracing mixin (#10406)

7.99.0

Important Changes

Deprecations

This release includes some deprecations for span related methods and integrations in our Deno SDK, @sentry/deno. For more details please look at our migration guide.

• feat(core): Deprecate Span.setHttpStatus in favor of setHttpStatus (#10268)
• feat(core): Deprecate spanStatusfromHttpCode in favour of getSpanStatusFromHttpCode (#10361)
• feat(core): Deprecate StartSpanOptions.origin in favour of passing attribute (#10274)
• feat(deno): Expose functional integrations to replace classes (#10355)

Other Changes

• feat(bun): Add missing @sentry/node re-exports (#10396)
• feat(core): Add afterAllSetup hook for integrations (#10345)
• feat(core): Ensure startSpan() can handle spans that require parent (#10386)
• feat(core): Read propagation context off scopes in startSpan APIs (#10300)
• feat(remix): Export missing @sentry/node functions (#10385, #10391)
• feat(serverless): Add missing @sentry/node re-exports (#10390)
• feat(sveltekit): Add more missing @sentry/node re-exports (#10392)
• feat(tracing): Export proper type for browser tracing (#10411)
• feat(tracing): Expose new browserTracingIntegration (#10351)
• fix: Ensure afterAllSetup is called when using addIntegration() (#10372)
• fix(core): Export spanToTraceContext function from span utils (#10364)
• fix(core): Make FunctionToString integration use SETUP_CLIENTS weakmap (#10358)
• fix(deno): Call function if client is not setup (#10354)
• fix(react): Fix attachReduxState option (#10381)
• fix(spotlight): Use unpatched http.request (#10369)
• fix(tracing): Only create request span if there is active span (#10375)
• ref: Read propagation context off of scope and isolation scope when propagating and applying trace context (#10297)

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