@@ -19,7 +19,7 @@ changes:
1919
2020- There is now automated performance instrumentation for Express, Fastify, Nest.js and Koa. You can remove any
2121 performance and request isolation code you previously wrote manually for these frameworks.
22- - All performance instrumenttion is enabled by default, and will only take effect if the instrumented package is used.
22+ - All performance instrumention is enabled by default, and will only take effect if the instrumented package is used.
2323 You don't need to use ` autoDiscoverNodePerformanceMonitoringIntegrations() ` anymore.
2424- You need to ensure to call ` Sentry.init() ` _ before_ you import any other packages. Otherwise, the packages cannot be
2525 instrumented:
@@ -121,11 +121,14 @@ configuration options.
121121
122122### Other Changes
123123
124+ - feat: Ensure ` withActiveSpan ` is exported everywhere (#10878 )
124125- feat: Allow passing ` null ` to ` withActiveSpan ` (#10717 )
125126- feat: Implement new Async Context Strategy (#10647 )
126127- feat: Remove ` hub ` from global, ` hub.run ` & hub utilities (#10718 )
127128- feat: Update default trace propagation targets logic in the browser (#10621 )
129+ - feat: Ignore ResizeObserver and undefined error (#10845 )
128130- feat(browser): Export ` getIsolationScope ` and ` getGlobalScope ` (#10658 )
131+ - feat(browser): Prevent initialization in browser extensions (#10844 )
129132- feat(core): Add metric summaries to spans (#10554 )
130133- feat(core): Decouple metrics aggregation from client (#10628 )
131134- feat(core): Lookup client on current scope, not hub (#10635 )
@@ -210,6 +213,8 @@ We have also removed or updated a variety of deprecated APIs.
210213- feat(v8/node): Remove deepReadDirSync export (#10564 )
211214- feat(v8/node): Remove deprecated anr methods (#10562 )
212215- feat(v8/node): Remove getModuleFromFilename export (#10754 )
216+ - feat(core): Remove deprecated props from ` Span ` interface (#10854 )
217+ - fix(v8): Remove deprecated tracing config (#10870 )
213218- ref: Make ` setupOnce ` optional in integrations (#10729 )
214219- ref: Migrate transaction source from metadata to attributes (#10674 )
215220- ref: Refactor remaining ` makeMain ` usage (#10713 )
@@ -224,6 +229,53 @@ We have also removed or updated a variety of deprecated APIs.
224229- ref: Remove usage of span tags (#10808 )
225230- ref: Remove user segment (#10575 )
226231
232+ ## 7.105.0
233+
234+ ### Important Changes
235+
236+ - ** feat: Ensure ` withActiveSpan ` is exported everywhere (#10877 )**
237+
238+ You can use the ` withActiveSpan ` method to ensure a certain span is the active span in a given callback. This can be
239+ used to create a span as a child of a specific span with the ` startSpan ` API methods:
240+
241+ ``` js
242+ const parentSpan = Sentry .startInactiveSpan ({ name: ' parent' });
243+ if (parentSpan) {
244+ withActiveSpan (parentSpan, () => {
245+ // This will be a direct child of parentSpan
246+ const childSpan = Sentry .startInactiveSpan ({ name: ' child' });
247+ });
248+ }
249+ ```
250+
251+ ## 7.104.0
252+
253+ ### Important Changes
254+
255+ - ** feat(performance): create Interaction standalone spans on inp events (#10709 )**
256+
257+ This release adds support for the INP web vital. This is currently only supported for Saas Sentry, and product support
258+ is released with the upcoming ` 24.3.0 ` release of self-hosted.
259+
260+ To opt-in to this feature, you can use the ` enableInp ` option in the ` browserTracingIntegration ` :
261+
262+ ``` js
263+ Sentry .init ({
264+ integrations: [
265+ Sentry .browserTracingIntegration ({
266+ enableInp: true ,
267+ });
268+ ]
269+ })
270+ ```
271+
272+ ### Other Changes
273+
274+ - feat(feedback): Flush replays when feedback form opens (#10567 )
275+ - feat(profiling-node): Expose ` nodeProfilingIntegration ` (#10864 )
276+ - fix(profiling-node): Fix dependencies to point to current versions (#10861 )
277+ - fix(replay): Add ` errorHandler ` for replayCanvas integration (#10796 )
278+
227279## 7.103.0
228280
229281### Important Changes
0 commit comments