chore(deps): bump @sentry/node from 7.57.0 to 7.64.0

[dependabot]

Bumps @sentry/node from 7.57.0 to 7.64.0.

Release notes

Sourced from @​sentry/node's releases.

7.64.0

• feat(core): Add setMeasurement export (#8791)
• fix(nextjs): Check for existence of default export when wrapping pages (#8794)
• fix(nextjs): Ensure imports are valid relative paths (#8799)
• fix(nextjs): Only re-export default export if it exists (#8800)

Bundle size 📦

Path	Size
@​sentry/browser (incl. Tracing, Replay) - Webpack (gzipped)	75.12 KB
@​sentry/browser (incl. Tracing) - Webpack (gzipped)	31.14 KB
@​sentry/browser - Webpack (gzipped)	21.81 KB
@​sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (gzipped)	69.73 KB
@​sentry/browser (incl. Tracing) - ES6 CDN Bundle (gzipped)	28.18 KB
@​sentry/browser - ES6 CDN Bundle (gzipped)	20.18 KB
@​sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (minified & uncompressed)	219.89 KB
@​sentry/browser (incl. Tracing) - ES6 CDN Bundle (minified & uncompressed)	84.78 KB
@​sentry/browser - ES6 CDN Bundle (minified & uncompressed)	59.86 KB
@​sentry/browser (incl. Tracing) - ES5 CDN Bundle (gzipped)	31.04 KB
@​sentry/react (incl. Tracing, Replay) - Webpack (gzipped)	65.3 KB
@​sentry/react - Webpack (gzipped)	21.84 KB
@​sentry/nextjs Client (incl. Tracing, Replay) - Webpack (gzipped)	92.93 KB
@​sentry/nextjs Client - Webpack (gzipped)	50.66 KB

7.64.0-alpha.0

Important Changes

• feat(replay): Upgrade to rrweb2.0

This should be fully backwards compatible with previously recorded replays. Only breaking change is that we will not be masking aria-label by default. This is to better support searching by clicks. Another issue is there is about a 13% bundle size increase, however this comes with improved performance and improved replay fidelity especially in regards to web components.

Bundle size 📦

Path	Size
@​sentry/browser (incl. Tracing, Replay) - Webpack (gzipped)	83.73 KB
@​sentry/browser (incl. Tracing) - Webpack (gzipped)	31.15 KB
@​sentry/browser - Webpack (gzipped)	21.82 KB
@​sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (gzipped)	78.12 KB
@​sentry/browser (incl. Tracing) - ES6 CDN Bundle (gzipped)	28.2 KB
@​sentry/browser - ES6 CDN Bundle (gzipped)	20.19 KB
@​sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (minified & uncompressed)	251.54 KB
@​sentry/browser (incl. Tracing) - ES6 CDN Bundle (minified & uncompressed)	84.79 KB
@​sentry/browser - ES6 CDN Bundle (minified & uncompressed)	59.87 KB
@​sentry/browser (incl. Tracing) - ES5 CDN Bundle (gzipped)	31.06 KB
@​sentry/react (incl. Tracing, Replay) - Webpack (gzipped)	73.92 KB
@​sentry/react - Webpack (gzipped)	21.85 KB
@​sentry/nextjs Client (incl. Tracing, Replay) - Webpack (gzipped)	101.61 KB
@​sentry/nextjs Client - Webpack (gzipped)	50.66 KB

... (truncated)

Changelog

Sourced from @​sentry/node's changelog.

7.64.0

• feat(core): Add setMeasurement export (#8791)
• fix(nextjs): Check for existence of default export when wrapping pages (#8794)
• fix(nextjs): Ensure imports are valid relative paths (#8799)
• fix(nextjs): Only re-export default export if it exists (#8800)

7.63.0

• build(deps): bump @​opentelemetry/instrumentation from 0.41.0 to 0.41.2
• feat(eventbuilder): Export exceptionFromError for use in hybrid SDKs (#8766)
• feat(node-experimental): Re-export from node (#8786)
• feat(tracing): Add db connection attributes for mysql spans (#8775)
• feat(tracing): Add db connection attributes for postgres spans (#8778)
• feat(tracing): Improve data collection for mongodb spans (#8774)
• fix(nextjs): Execute sentry config independently of autoInstrumentServerFunctions and autoInstrumentAppDirectory (#8781)
• fix(replay): Ensure we do not flush if flush took too long (#8784)
• fix(replay): Ensure we do not try to flush when we force stop replay (#8783)
• fix(replay): Fix hasCheckout handling (#8782)
• fix(replay): Handle multiple clicks in a short time (#8773)
• ref(replay): Skip events being added too long after initial segment (#8768)

7.62.0

Important Changes

• feat(integrations): Add ContextLines integration for html-embedded JS stack frames (#8699)

This release adds the ContextLines integration as an optional integration for the Browser SDKs to @sentry/integrations.

This integration adds source code from inline JavaScript of the current page's HTML (e.g. JS in <script> tags) to stack traces of captured errors. It can't collect source code from assets referenced by your HTML (e.g. <script src="..." />).

The ContextLines integration is useful when you have inline JS code in HTML pages that can't be accessed by Sentry's backend, for example, due to a login-protected page.

import { ContextLines } from "@sentry/integrations";
Sentry.init({
// ...
integrations: [
new ContextLines({
// The number of lines to collect before and after each stack frame's line number
// Defaults to 7
frameContextLines: 7,
}),
],
});

... (truncated)

Commits

• e01d8f8 release: 7.64.0
• 5a8e33b Merge pull request #8808 from getsentry/prepare-release/7.64.0
• 81fbc01 meta(changelog): Update changelog for 7.64.0
• 6e83a6b fix(nextjs): Only re-export default export if it exists (#8800)
• 2cd6ea5 feat(core): Add setMeasurement export (#8791)
• 7bba7eb fix(nextjs): Check for existence of default export when wrapping pages (#8794)
• e259aa7 fix(nextjs): Ensure imports are valid relative paths (#8799)
• 797d906 Merge pull request #8789 from getsentry/master
• 7ac0000 Merge branch 'release/7.63.0'
• 6346e53 feat(tracing): Add setName method on spans (#8725)
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[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 / 12 versions between 7.57.0 and 7.64.0 checked

[supalarry]

another try

[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 / 12 versions between 7.57.0 and 7.64.0 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).

[supalarry]

another try

[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).

[supalarry]

another try

[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. If your application relies on short replays, you may need to adjust your configurations.

[dependabot]

Superseded by #96.