dependabot npm(deps): bump @sentry/node from 7.57.0 to 7.58.0
Bumps @sentry/node from 7.57.0 to 7.58.0.
Release notes
Sourced from @sentry/node
's releases.
7.58.0
Important Changes
- Performance Monitoring not required for Distributed Tracing
This release adds support for distributed tracing without requiring performance monitoring to be active on the JavaScript SDKs (browser and node). This means even if there is no sampled transaction/span, the SDK will still propagate traces to downstream services. Distributed Tracing can be configured with the
tracePropagationTargets
option, which controls what requests to attach thesentry-trace
andbaggage
HTTP headers to (which is what propagates tracing information).Sentry.init({ tracePropagationTargets: ["third-party-site.com", /^https:\/\/yourserver\.io\/api/], });
feat(tracing): Add tracing without performance to browser and client Sveltekit (#8458)
feat(node): Add tracing without performance to Node http integration (#8450)
feat(node): Add tracing without performance to Node Undici (#8449)
feat(node): Populate propagation context using env variables (#8422)
feat(core): Support
AggregateErrors
inLinkedErrors
integration (#8463)This release adds support for
AggregateErrors
. AggregateErrors are considered as Exception Groups by Sentry, and will be visualized and grouped differently. See the Exception Groups Changelog Post for more details.Exception Group support requires Self-Hosted Sentry version 23.5.1 or newer.
- feat(replay): Add a new option
networkDetailDenyUrls
(#8439)This release adds a new option
networkDetailDenyUrls
to theReplay
integration. This option allows you to specify a list of URLs that should not be captured by theReplay
integration, which can be used alongside the existingnetworkDetailAllowUrls
for finely grained control of which URLs should have network details captured.Sentry.init({ integrations: [ new Sentry.Integrations.Replay({ networkDetailDenyUrls: [/^http:\/\/example.com\/test$/], }), ], });
Other Changes
- feat(core): Add helpers to get module metadata from injected code (#8438)
- feat(core): Add sampling decision to trace envelope header (#8483)
- feat(node): Add trace context to checkin (#8503)
- feat(node): Export
getModule
for Electron SDK (#8488)- feat(types): Allow
user.id
to be a number (#8330)- fix(browser): Set anonymous
crossorigin
attribute on report dialog (#8424)- fix(nextjs): Ignore
tunnelRoute
when doing static exports (#8471)- fix(nextjs): Use
basePath
option fortunnelRoute
(#8454)- fix(node): Apply source context to linked errors even when it is uncached (#8453)
- fix(node): report errorMiddleware errors as unhandled (#8048)
... (truncated)
Changelog
Sourced from @sentry/node
's changelog.
7.58.0
Important Changes
- Performance Monitoring not required for Distributed Tracing
This release adds support for distributed tracing without requiring performance monitoring to be active on the JavaScript SDKs (browser and node). This means even if there is no sampled transaction/span, the SDK will still propagate traces to downstream services. Distributed Tracing can be configured with the
tracePropagationTargets
option, which controls what requests to attach thesentry-trace
andbaggage
HTTP headers to (which is what propagates tracing information).Sentry.init({ tracePropagationTargets: ["third-party-site.com", /^https:\/\/yourserver\.io\/api/], });
feat(tracing): Add tracing without performance to browser and client Sveltekit (#8458)
feat(node): Add tracing without performance to Node http integration (#8450)
feat(node): Add tracing without performance to Node Undici (#8449)
feat(node): Populate propagation context using env variables (#8422)
feat(core): Support
AggregateErrors
inLinkedErrors
integration (#8463)This release adds support for
AggregateErrors
. AggregateErrors are considered as Exception Groups by Sentry, and will be visualized and grouped differently. See the Exception Groups Changelog Post for more details.Exception Group support requires Self-Hosted Sentry version 23.5.1 or newer.
- feat(replay): Add a new option
networkDetailDenyUrls
(#8439)This release adds a new option
networkDetailDenyUrls
to theReplay
integration. This option allows you to specify a list of URLs that should not be captured by theReplay
integration, which can be used alongside the existingnetworkDetailAllowUrls
for finely grained control of which URLs should have network details captured.Sentry.init({ integrations: [ new Sentry.Integrations.Replay({ networkDetailDenyUrls: [/^http:\/\/example.com\/test$/], }), ], });
Other Changes
- feat(core): Add helpers to get module metadata from injected code (#8438)
- feat(core): Add sampling decision to trace envelope header (#8483)
- feat(node): Add trace context to checkin (#8503)
- feat(node): Export
getModule
for Electron SDK (#8488)- feat(types): Allow
user.id
to be a number (#8330)- fix(browser): Set anonymous
crossorigin
attribute on report dialog (#8424)- fix(nextjs): Ignore
tunnelRoute
when doing static exports (#8471)- fix(nextjs): Use
basePath
option fortunnelRoute
(#8454)- fix(node): Apply source context to linked errors even when it is uncached (#8453)
... (truncated)
Commits
-
cfcba5f
release: 7.58.0 -
3012f77
Merge pull request #8480 from getsentry/prepare-release/7.58.0 -
7e9fb01
meta(changelog): Update changelog for 7.58.0 -
6e4e805
feat(core): Add sampling decision to trace envelope header (#8483) -
9b58519
fix(remix): Add explicit@sentry/node
exports. (#8509) -
f0afc37
feat(node): Add trace context to checkin (#8503) -
1167436
test(remix): Skip flaky firefox integration tests (#8506) -
87bdcba
meta: Don't gitignore.d.ts
files (#8472) -
130e4a3
feat(types): Allowuser.id
to be a number (#8330) -
428e531
chore(node): Removetest.only
usage in context lines (#8485) - Additional commits viewable in compare view