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

[dependabot]

Bumps @sentry/node from 7.57.0 to 7.63.0.

Release notes

Sourced from @​sentry/node's releases.

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)

Bundle size 📦

Path	Size
@​sentry/browser (incl. Tracing, Replay) - Webpack (gzipped)	75.1 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.71 KB
@​sentry/browser (incl. Tracing) - ES6 CDN Bundle (gzipped)	28.16 KB
@​sentry/browser - ES6 CDN Bundle (gzipped)	20.18 KB
@​sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (minified & uncompressed)	219.8 KB
@​sentry/browser (incl. Tracing) - ES6 CDN Bundle (minified & uncompressed)	84.69 KB
@​sentry/browser - ES6 CDN Bundle (minified & uncompressed)	59.86 KB
@​sentry/browser (incl. Tracing) - ES5 CDN Bundle (gzipped)	31.03 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.92 KB
@​sentry/nextjs Client - Webpack (gzipped)	50.64 KB

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({
// ...
</tr></table>

... (truncated)

Changelog

Sourced from @​sentry/node's changelog.

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

Other Changes

• fix(nextjs): Make all wrappers isomorphic and available in all runtimes (#8743)
• fix(replay): Cancel debounce when replay is too short/long (#8742)
• fix(utils): dirname and basename should handle Windows paths (#8737)
• ref: Hoist flush, close, and lastEventId into @sentry/core (#8731)
• ref(node): Don't call JSON.stringify on prisma client when logging (#8745)

... (truncated)

Commits

• f3cd633 release: 7.63.0
• 30da5c3 Merge pull request #8788 from getsentry/prepare-release/7.63.0
• 3439d39 meta(changelog): Update changelog for 7.63.0
• fc7344f fix(replay): Ensure we do not try to flush when we force stop replay (#8783)
• ad0cb9b feat(node-experimental): Re-export from node (#8786)
• 12932e0 feat(tracing): Add db connection attributes for postgres spans (#8778)
• 8f5922d feat(tracing): Add db connection attributes for mysql spans (#8775)
• fdd17e7 feat(tracing): Improve data collection for mongodb spans (#8774)
• 0bade5d fix(replay): Ensure we do not flush if flush took too long (#8784)
• da1b592 fix(replay): Fix hasCheckout handling (#8782)
• 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)

[supalarry]

/adaptly go

[adaptly-bot]

ℹ️  Breaking Changes in the Dependency's Changelog

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 to the Replay integration

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.63.0 checked

[adaptly-bot]

💥 Error

Please, try again. Also, make sure that this development branch has the latest code from the parent branch by either rebasing or merging the parent branch into this branch.

If that did not help, please, report us the Error code: 35

[dependabot]

Superseded by #72.

[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 / 11 versions between 7.57.0 and 7.63.0 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 / 11 versions between 7.57.0 and 7.63.0 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 / 11 versions between 7.57.0 and 7.63.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).

6 / 11 versions between 7.57.0 and 7.63.0 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 replay feature will no longer send replays that are less than 5 seconds long. This is a breaking change if your application relies on short replays. You can configure the minimum replay duration, but it is capped at 15 seconds maximum. Refactor your code as follows if needed:

- new Replay({})
+ new Replay({ minReplayDuration: 10000 }) // in ms