chore(deps): bump @sentry/react from 7.48.0 to 7.50.0 in /ui

[dependabot[bot]]

Bumps @sentry/react from 7.48.0 to 7.50.0.

Release notes

Sourced from @​sentry/react's releases.

7.50.0

Important Changes

• doc(sveltekit): Promote the SDK to beta state (#7976)
  • feat(sveltekit): Convert sentryHandle to a factory function (#7975)

With this release, the Sveltekit SDK (@​sentry/sveltekit) is promoted to Beta. This means that we do not expect any more breaking changes.

The final breaking change is that sentryHandle is now a function. So in order to update to 7.50.0, you have to update your hooks.server.js file:

// hooks.server.js
// Old:
export const handle = sentryHandle;
// New:
export const handle = sentryHandle();

• feat(replay): Allow to configure URLs to capture network bodies/headers (#7953)

You can now capture request/response bodies & headers of network requests in Replay. You have to define an allowlist of URLs you want to capture additional information for:

new Replay({
  networkDetailAllowUrls: ['https://sentry.io/api'],
});

By default, we will capture request/response bodies, as well as the request/response headers content-type, content-length and accept. You can configure this with some additional configuration:

new Replay({
  networkDetailAllowUrls: ['https://sentry.io/api'],
  // opt-out of capturing bodies
  networkCaptureBodies: false,
  // These headers are captured _in addition to_ the default headers
  networkRequestHeaders: ['X-Custom-Header'],
  networkResponseHeaders: ['X-Custom-Header', 'X-Custom-Header-2']
});

Note that bodies will be truncated to a max length of ~150k characters.

- feat(replay): Changes of sampling behavior & public API

• feat(replay): Change the behavior of error-based sampling (#7768)

... (truncated)

Changelog

Sourced from @​sentry/react's changelog.

7.50.0

Important Changes

• doc(sveltekit): Promote the SDK to beta state (#7976)
  • feat(sveltekit): Convert sentryHandle to a factory function (#7975)

With this release, the Sveltekit SDK (@​sentry/sveltekit) is promoted to Beta. This means that we do not expect any more breaking changes.

The final breaking change is that sentryHandle is now a function. So in order to update to 7.50.0, you have to update your hooks.server.js file:

// hooks.server.js
// Old:
export const handle = sentryHandle;
// New:
export const handle = sentryHandle();

• feat(replay): Allow to configure URLs to capture network bodies/headers (#7953)

You can now capture request/response bodies & headers of network requests in Replay. You have to define an allowlist of URLs you want to capture additional information for:

new Replay({
  networkDetailAllowUrls: ['https://sentry.io/api'],
});

By default, we will capture request/response bodies, as well as the request/response headers content-type, content-length and accept. You can configure this with some additional configuration:

new Replay({
  networkDetailAllowUrls: ['https://sentry.io/api'],
  // opt-out of capturing bodies
  networkCaptureBodies: false,
  // These headers are captured _in addition to_ the default headers
  networkRequestHeaders: ['X-Custom-Header'],
  networkResponseHeaders: ['X-Custom-Header', 'X-Custom-Header-2']
});

Note that bodies will be truncated to a max length of ~150k characters.

- feat(replay): Changes of sampling behavior & public API

... (truncated)

Commits

• d91bbf2 release: 7.50.0
• f3bfe11 Merge pull request #7966 from getsentry/prepare-release/7.50.0
• da799e9 meta(changelog): Update Changelog for 7.50.0
• 54d588e doc(sveltekit): Promote the SDK to beta state (#7976)
• ec1a441 test: Fix flaky replay DSC test (#7973)
• 5f9b9ce feat(sveltekit): Convert sentryHandle to a factory function (#7975)
• 619c4b0 Revert "doc(sveltekit): Promote the SDK to beta state (#7874)" (#7974)
• a5b9284 feat(replay): Change the behavior of error-based sampling (#7768)
• 1683caf feat(node): Make Undici a default integration. (#7967)
• d1b09c6 ref(core): Update multiplexed transport to default to errors only (#7964)
• 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[bot]]

Superseded by #164.