From 9d70e760d2a7fae058d128c069f21dcfd5c671c3 Mon Sep 17 00:00:00 2001 From: Lukas Stracke Date: Tue, 8 Nov 2022 09:28:58 +0100 Subject: [PATCH 1/4] meta: Update changelog for 7.18.0 --- CHANGELOG.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 30cefa4c2307..bfcdf826b0ef 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,6 +4,25 @@ - "You miss 100 percent of the chances you don't take. — Wayne Gretzky" — Michael Scott +## 7.18.0 + +This release adds the `beforeSendTransaction` callback to all JS SDKs, letting you make changes or drop transactions before they're sent to Sentry. This callback works identically to `beforeSend`, just for transactions. + +Furthermore, this release adds the `shouldCreateSpanForRequest` option to the Node SDK and the `tracePropagationTargets` option to the Browser SDK, providing fine grained control over which outgoing Http requests should be represented as a span in an ongoing transaction and which requests should be traced by Sentry. + +This release also marks the starting point of adding support for OpenTelemetry to the Node SDK, by adding the `instrumenter` option to the Node SDK's init options. + +- feat(core): Add `beforeSendTransaction` (#6121) +- feat(core): Add `instrumenter` option to `ClientOptions` (#6128) +- feat(node): Add option to `OnUncaughtException` integration that allows mimicking native uncaught error exit behaviour (#6137) +- feat(node): Add `shouldCreateSpanForRequest` option (#6055) +- feat(otel): Add extract functionality to SentryPropagator (#6115) +- feat(tracing): Add `tracePropagationTargets` option to browser routing instrumentation (#6080) +- fix(nextjs): Allow `onUncaughtException` integration to remain excluded (#6148) +- fix(nextjs): Do not exit process when errors bubble up while additional `uncaughtException`-handlers are registered (#6138) +- fix(remix): Prevent capturing pending promises as exceptions. (#6129) +- ref(core): Pre-`beforeSendTransaction` cleanup (#6135) + ## 7.17.4 - fix(aws): Move relay to port 5333 to avoid collisions (#6093) From 522518e3667b038a56855c0c3b98459a9ee8963a Mon Sep 17 00:00:00 2001 From: Lukas Stracke Date: Tue, 8 Nov 2022 09:33:45 +0100 Subject: [PATCH 2/4] remove otel items --- CHANGELOG.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index bfcdf826b0ef..224177a25a0b 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -10,13 +10,9 @@ This release adds the `beforeSendTransaction` callback to all JS SDKs, letting y Furthermore, this release adds the `shouldCreateSpanForRequest` option to the Node SDK and the `tracePropagationTargets` option to the Browser SDK, providing fine grained control over which outgoing Http requests should be represented as a span in an ongoing transaction and which requests should be traced by Sentry. -This release also marks the starting point of adding support for OpenTelemetry to the Node SDK, by adding the `instrumenter` option to the Node SDK's init options. - - feat(core): Add `beforeSendTransaction` (#6121) -- feat(core): Add `instrumenter` option to `ClientOptions` (#6128) - feat(node): Add option to `OnUncaughtException` integration that allows mimicking native uncaught error exit behaviour (#6137) - feat(node): Add `shouldCreateSpanForRequest` option (#6055) -- feat(otel): Add extract functionality to SentryPropagator (#6115) - feat(tracing): Add `tracePropagationTargets` option to browser routing instrumentation (#6080) - fix(nextjs): Allow `onUncaughtException` integration to remain excluded (#6148) - fix(nextjs): Do not exit process when errors bubble up while additional `uncaughtException`-handlers are registered (#6138) From 1a4adffa0f1123374f0b51387879349b1c3fc93f Mon Sep 17 00:00:00 2001 From: Lukas Stracke Date: Tue, 8 Nov 2022 09:44:59 +0100 Subject: [PATCH 3/4] Update CHANGELOG.md Co-authored-by: Katie Byers --- CHANGELOG.md | 1 - 1 file changed, 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 224177a25a0b..74dffa2505ea 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -17,7 +17,6 @@ Furthermore, this release adds the `shouldCreateSpanForRequest` option to the No - fix(nextjs): Allow `onUncaughtException` integration to remain excluded (#6148) - fix(nextjs): Do not exit process when errors bubble up while additional `uncaughtException`-handlers are registered (#6138) - fix(remix): Prevent capturing pending promises as exceptions. (#6129) -- ref(core): Pre-`beforeSendTransaction` cleanup (#6135) ## 7.17.4 From f6f1ec59879b4e472b4ee5c664be7a11fec08de0 Mon Sep 17 00:00:00 2001 From: Lukas Stracke Date: Tue, 8 Nov 2022 09:53:57 +0100 Subject: [PATCH 4/4] apply further review suggestions --- CHANGELOG.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 74dffa2505ea..b32a9ae8b9d1 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -6,13 +6,10 @@ ## 7.18.0 -This release adds the `beforeSendTransaction` callback to all JS SDKs, letting you make changes or drop transactions before they're sent to Sentry. This callback works identically to `beforeSend`, just for transactions. - -Furthermore, this release adds the `shouldCreateSpanForRequest` option to the Node SDK and the `tracePropagationTargets` option to the Browser SDK, providing fine grained control over which outgoing Http requests should be represented as a span in an ongoing transaction and which requests should be traced by Sentry. +This release adds the `beforeSendTransaction` callback to all JS SDKs, letting you make changes to or drop transactions before they're sent to Sentry. This callback works identically to `beforeSend`, just for transactions. - feat(core): Add `beforeSendTransaction` (#6121) - feat(node): Add option to `OnUncaughtException` integration that allows mimicking native uncaught error exit behaviour (#6137) -- feat(node): Add `shouldCreateSpanForRequest` option (#6055) - feat(tracing): Add `tracePropagationTargets` option to browser routing instrumentation (#6080) - fix(nextjs): Allow `onUncaughtException` integration to remain excluded (#6148) - fix(nextjs): Do not exit process when errors bubble up while additional `uncaughtException`-handlers are registered (#6138)