build(deps): bump @sentry/node from 7.57.0 to 7.61.1

[dependabot]

Bumps @sentry/node from 7.57.0 to 7.61.1.

Release notes

Sourced from @​sentry/node's releases.

7.61.1

• feat(nextjs): Add AsyncLocalStorage async context strategy to edge SDK (#8720)
• fix(core): Filter internal API frames for synthetic frames (#8710)
• fix(integrations): Capture exception if any arg to console method is an error (#8671)
• fix(node-experimental): Update auto integration lookup & readme (#8690)
• fix(node): Add availablility check on current hub to Node ContextLines integration (#8715)
• fix(replay): Ensure buffer sessions end after capturing an error (#8713)
• fix(replay): Ensure buffer->session switch is reliable (#8712)
• fix(replay): Ensure we debounce flush if replay too short (#8716)
• fix(replay): Improve capture of errorIds/traceIds (#8678)
• fix(tracing): Set correct parent span id on fetch sentry-trace header (#8687)
• fix(utils): Avoid pre_context and context_line overlap if frame lineno is out of bounds (#8722)
• ref(replay): Improve status logging (#8709)
• ref(nextjs): Allow withSentryConfig to accept async config function (#8721)

Bundle size 📦

Path	Size
@​sentry/browser (incl. Tracing, Replay) - Webpack (gzipped)	74.85 KB
@​sentry/browser (incl. Tracing) - Webpack (gzipped)	31.11 KB
@​sentry/browser - Webpack (gzipped)	21.81 KB
@​sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (gzipped)	69.53 KB
@​sentry/browser (incl. Tracing) - ES6 CDN Bundle (gzipped)	28.14 KB
@​sentry/browser - ES6 CDN Bundle (gzipped)	20.15 KB
@​sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (minified & uncompressed)	219.03 KB
@​sentry/browser (incl. Tracing) - ES6 CDN Bundle (minified & uncompressed)	84.63 KB
@​sentry/browser - ES6 CDN Bundle (minified & uncompressed)	59.8 KB
@​sentry/browser (incl. Tracing) - ES5 CDN Bundle (gzipped)	30.43 KB
@​sentry/react (incl. Tracing, Replay) - Webpack (gzipped)	65.06 KB
@​sentry/react - Webpack (gzipped)	21.84 KB
@​sentry/nextjs Client (incl. Tracing, Replay) - Webpack (gzipped)	92.65 KB
@​sentry/nextjs Client - Webpack (gzipped)	50.61 KB

7.61.0

Important Changes

• feat(node-experimental): Add @sentry/node-experimental package as MVP for POTEL (#8609)

This introduces a new, experimental package, @sentry/node-experimental. This is a variant of the Node SDK which uses OpenTelemetry under the hood for performance instrumentation.

Note that this package is very much WIP, considered unstable and may change at any time. No SemVer guarantees apply whatsoever. Still, if you're brave enough you can give it a try. Read more about @​sentry/node-experimental

Other Changes

• fix(node): Don't set extra baggage headers (#8657)
• fix(tracing): Trim idle transaction spans if they exceed final timeout (#8653)

... (truncated)

Changelog

Sourced from @​sentry/node's changelog.

7.61.1

• feat(nextjs): Add AsyncLocalStorage async context strategy to edge SDK (#8720)
• fix(core): Filter internal API frames for synthetic frames (#8710)
• fix(integrations): Capture exception if any arg to console method is an error (#8671)
• fix(node-experimental): Update auto integration lookup & readme (#8690)
• fix(node): Add availablility check on current hub to Node ContextLines integration (#8715)
• fix(replay): Ensure buffer sessions end after capturing an error (#8713)
• fix(replay): Ensure buffer->session switch is reliable (#8712)
• fix(replay): Ensure we debounce flush if replay too short (#8716)
• fix(replay): Improve capture of errorIds/traceIds (#8678)
• fix(tracing): Set correct parent span id on fetch sentry-trace header (#8687)
• fix(utils): Avoid pre_context and context_line overlap if frame lineno is out of bounds (#8722)
• ref(replay): Improve status logging (#8709)
• ref(nextjs): Allow withSentryConfig to accept async config function (#8721)

7.61.0

Important Changes

• feat(node-experimental): Add @sentry/node-experimental package as MVP for POTEL (#8609)

This introduces a new, experimental package, @sentry/node-experimental. This is a variant of the Node SDK which uses OpenTelemetry under the hood for performance instrumentation.

Note that this package is very much WIP, considered unstable and may change at any time. No SemVer guarantees apply whatsoever. Still, if you're brave enough you can give it a try. Read more about @​sentry/node-experimental

Other Changes

• fix(node): Don't set extra baggage headers (#8657)
• fix(tracing): Trim idle transaction spans if they exceed final timeout (#8653)

7.60.1

• fix(nextjs): Match folder paths with trailing separator (#8615)
• fix(replay): Ignore clicks with shift pressed (#8648)
• fix(replay): Use session.started for min/max duration check (#8617)

7.60.0

Important Changes

• feat(replay): Ensure min/max duration when flushing (#8596)

We will not send replays that are 1h) replays. You can optionally configure the min. replay duration (defaults to 5s):

</tr></table> 

... (truncated)

Commits

• 6e8dd40 release: 7.61.1
• d9f07bc Merge pull request #8730 from getsentry/prepare-release/7.61.1
• 99e3479 Revert "build(release): Add statusProvider context check for craft (#8685) ...
• 8c6ea3f Merge pull request #8726 from getsentry/prepare-release/7.61.1
• 754b082 meta: Update CHANGELOG for 7.61.1
• b5f55a3 fix(replay): Ensure we debounce flush if replay too short (#8716)
• e586397 fix(replay): Ensure buffer->session switch is reliable (#8712)
• 2748691 fix(replay): Ensure buffer sessions end after capturing an error (#8713)
• 60c1081 ref(replay): Improve status logging (#8709)
• 85effab fix(utils): Avoid pre_context and context_line overlap if frame lineno is...
• 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)

[dependabot]

Superseded by #49.

[adaptly-bot-dev]

ℹ️  Breaking Changes in the Dependency's Changelog. Check breaking changes and run /adaptly go to continue checking next versions.

Package: @sentry/node
Version: 7.58.0

 Breaking changes

1: 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({
-   tracesSampleRate: 0,
- });

+ Sentry.init({
+   tracePropagationTargets: ["third-party-site.com", /^https:\/\/yourserver\.io\/api/],
+ });

2: Support AggregateErrors in LinkedErrors integration

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.

3: Add a new option networkDetailDenyUrls

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$/],
    }),
  ],
});

1 / 9 versions between 7.57.0 and 7.61.1 checked

[adaptly-bot-dev]

ℹ️  Breaking Changes in the Dependency's Changelog. Check breaking changes and run /adaptly go to continue checking next versions.

Package: @sentry/node
Version: 7.60.0

 Breaking changes

1: feat(replay): Ensure min/max duration when flushing (#8596)

Replays that are less than 5 seconds long will no longer be sent. Added safeguards to avoid overly long replays (>1 hour).

6 / 9 versions between 7.57.0 and 7.61.1 checked

[adaptly-bot-dev]

⚠️   @sentry/node@7.58.0

 Breaking changes

1: 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({
-   tracesSampleRate: 0,
- });

+ Sentry.init({
+   tracePropagationTargets: ["third-party-site.com", /^https:\/\/yourserver\.io\/api/],
+ });

2: Support AggregateErrors in LinkedErrors integration

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.

3: Add a new option networkDetailDenyUrls

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$/],
    }),
  ],
});

1 / 9 versions between 7.57.0 and 7.61.1 checked

[adaptly-bot-dev]

⚠️   @sentry/node@7.60.0

 Breaking changes

1: feat(replay): Ensure min/max duration when flushing (#8596)

Replays that are less than 5 seconds long will no longer be sent. Added safeguards to avoid overly long replays (>1 hour).

6 / 9 versions between 7.57.0 and 7.61.1 checked

[adaptly-bot-dev]

⚠️  @sentry/node@7.58.0

 Breaking changes

1: 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({
-   tracesSampleRate: 0,
- });

+ Sentry.init({
+   tracePropagationTargets: ["third-party-site.com", /^https:\/\/yourserver\.io\/api/],
+ });

2: Support AggregateErrors in LinkedErrors integration

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.

3: Add a new option networkDetailDenyUrls

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$/],
    }),
  ],
});

[adaptly-bot-dev]

⚠️  @sentry/node@7.60.0

 Breaking changes

1: feat(replay): Ensure min/max duration when flushing (#8596)

Replays that are less than 5 seconds long will no longer be sent. Added safeguards to avoid overly long replays (>1 hour).

[adaptly-bot-dev]

⚠️  @sentry/node@7.60.0

 Breaking changes

1: feat(replay): Ensure min/max duration when flushing (#8596)

The package will no longer send replays that are less than 5 seconds long. You can configure the minimum replay duration, which defaults to 5 seconds and is capped at 15 seconds max. If your application relies on very short replays, you may need to adjust your replay settings or the way you handle replays.