@@ -375,7 +375,7 @@ To make sure these integrations work properly you'll have to change how you
375375### General
376376
377377Removed top-level exports: ` tracingOrigins ` , ` MetricsAggregator ` , ` metricsAggregatorIntegration ` , ` Severity ` ,
378- ` Sentry.configureScope ` , ` Span ` , ` spanStatusfromHttpCode ` , ` makeMain ` , ` lastEventId ` , ` pushScope ` , ` popScope ` ,
378+ ` Sentry.configureScope ` , ` Span ` , ` spanStatusfromHttpCode ` , ` makeMain ` , ` pushScope ` , ` popScope ` ,
379379` addGlobalEventProcessor ` , ` timestampWithMs ` , ` addExtensionMethods ` , ` addGlobalEventProcessor ` , ` getActiveTransaction `
380380
381381Removed ` @sentry/utils ` exports: ` timestampWithMs ` , ` addOrUpdateIntegration ` , ` tracingContextFromHeaders ` , ` walk `
@@ -389,7 +389,6 @@ Removed `@sentry/utils` exports: `timestampWithMs`, `addOrUpdateIntegration`, `t
389389- [ Removal of ` Span ` class export from SDK packages] ( ./MIGRATION.md#removal-of-span-class-export-from-sdk-packages )
390390- [ Removal of ` spanStatusfromHttpCode ` in favour of ` getSpanStatusFromHttpCode ` ] ( ./MIGRATION.md#removal-of-spanstatusfromhttpcode-in-favour-of-getspanstatusfromhttpcode )
391391- [ Removal of ` addGlobalEventProcessor ` in favour of ` addEventProcessor ` ] ( ./MIGRATION.md#removal-of-addglobaleventprocessor-in-favour-of-addeventprocessor )
392- - [ Removal of ` lastEventId() ` method] ( ./MIGRATION.md#deprecate-lasteventid )
393392- [ Remove ` void ` from transport return types] ( ./MIGRATION.md#remove-void-from-transport-return-types )
394393- [ Remove ` addGlobalEventProcessor ` in favor of ` addEventProcessor ` ] ( ./MIGRATION.md#remove-addglobaleventprocessor-in-favor-of-addeventprocessor )
395394
@@ -568,10 +567,6 @@ Sentry.getGlobalScope().addEventProcessor(event => {
568567});
569568```
570569
571- #### Removal of ` lastEventId() ` method
572-
573- The ` lastEventId ` function has been removed. See [ below] ( ./MIGRATION.md#deprecate-lasteventid ) for more details.
574-
575570#### Removal of ` void ` from transport return types
576571
577572The ` send ` method on the ` Transport ` interface now always requires a ` TransportMakeRequestResponse ` to be returned in
@@ -1576,7 +1571,7 @@ If you are using the `Hub` right now, see the following table on how to migrate
15761571| captureException() | ` Sentry.captureException() ` |
15771572| captureMessage() | ` Sentry.captureMessage() ` |
15781573| captureEvent() | ` Sentry.captureEvent() ` |
1579- | lastEventId() | REMOVED - Use event processors or beforeSend instead |
1574+ | lastEventId() | ` Sentry.lastEventId() ` |
15801575| addBreadcrumb() | ` Sentry.addBreadcrumb() ` |
15811576| setUser() | ` Sentry.setUser() ` |
15821577| setTags() | ` Sentry.setTags() ` |
@@ -1697,35 +1692,6 @@ app.get('/your-route', req => {
16971692});
16981693```
16991694
1700- ## Deprecate ` Sentry.lastEventId() ` and ` hub.lastEventId() `
1701-
1702- ` Sentry.lastEventId() ` sometimes causes race conditions, so we are deprecating it in favour of the ` beforeSend `
1703- callback.
1704-
1705- ``` js
1706- // Before
1707- Sentry .init ({
1708- beforeSend (event , hint ) {
1709- const lastCapturedEventId = Sentry .lastEventId ();
1710-
1711- // Do something with `lastCapturedEventId` here
1712-
1713- return event ;
1714- },
1715- });
1716-
1717- // After
1718- Sentry .init ({
1719- beforeSend (event , hint ) {
1720- const lastCapturedEventId = event .event_id ;
1721-
1722- // Do something with `lastCapturedEventId` here
1723-
1724- return event ;
1725- },
1726- });
1727- ```
1728-
17291695## Deprecated fields on ` Span ` and ` Transaction `
17301696
17311697In v8, the Span class is heavily reworked. The following properties & methods are thus deprecated:
@@ -1793,25 +1759,6 @@ Instead, import this directly from `@sentry/utils`.
17931759Generally, in most cases you should probably use ` continueTrace ` instead, which abstracts this away from you and handles
17941760scope propagation for you.
17951761
1796- ## Deprecate ` lastEventId() `
1797-
1798- Instead, if you need the ID of a recently captured event, we recommend using ` beforeSend ` instead:
1799-
1800- ``` ts
1801- import * as Sentry from ' @sentry/browser' ;
1802-
1803- Sentry .init ({
1804- dsn: ' __DSN__' ,
1805- beforeSend(event , hint ) {
1806- const lastCapturedEventId = event .event_id ;
1807-
1808- // Do something with `lastCapturedEventId` here
1809-
1810- return event ;
1811- },
1812- });
1813- ```
1814-
18151762## Deprecate ` timestampWithMs ` export - #7878
18161763
18171764The ` timestampWithMs ` util is deprecated in favor of using ` timestampInSeconds ` .
0 commit comments