chore(deps): bump @sentry/node from 7.46.0 to 7.58.0

[dependabot]

Bumps @sentry/node from 7.46.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 the sentry-trace and baggage 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 in LinkedErrors 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 the Replay integration. This option allows you to specify a list of URLs that should not be captured by the Replay integration, which can be used alongside the existing networkDetailAllowUrls 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 for tunnelRoute (#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 the sentry-trace and baggage 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 in LinkedErrors 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 the Replay integration. This option allows you to specify a list of URLs that should not be captured by the Replay integration, which can be used alongside the existing networkDetailAllowUrls 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 for tunnelRoute (#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): Allow user.id to be a number (#8330)
• 428e531 chore(node): Remove test.only usage in context lines (#8485)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

yarn.lock changes

Click to toggle table visibility

Name	Status	Previous	Current
@sentry-internal/tracing		7.46.0	7.58.0
@sentry/core		7.46.0	7.58.0
@sentry/node		7.46.0	7.58.0
@sentry/types		7.46.0	7.58.0
@sentry/utils		7.46.0	7.58.0
tslib		2.5.0	2.6.0

[dependabot]

Superseded by #1716.