Bump @sentry/browser from 7.120.0 to 8.42.0

[dependabot]

Bumps @sentry/browser from 7.120.0 to 8.42.0.

Release notes

Sourced from @​sentry/browser's releases.

8.42.0

Important Changes

• feat(react): React Router v7 support (library) (#14513)

  This release adds support for React Router v7 (library mode). Check out the docs on how to set up the integration: Sentry React Router v7 Integration Docs

Deprecations

• feat: Warn about source-map generation (#14533)

  In the next major version of the SDK we will change how source maps are generated when the SDK is added to an application. Currently, the implementation varies a lot between different SDKs and can be difficult to understand. Moving forward, our goal is to turn on source maps for every framework, unless we detect that they are explicitly turned off. Additionally, if we end up enabling source maps, we will emit a log message that we did so.

  With this particular release, we are emitting warnings that source map generation will change in the future and we print instructions on how to prepare for the next major.

• feat(nuxt): Deprecate tracingOptions in favor of vueIntegration (#14530)

  Currently it is possible to configure tracing options in two places in the Sentry Nuxt SDK:

  • In Sentry.init()
  • Inside tracingOptions in Sentry.init()

  For tree-shaking purposes and alignment with the Vue SDK, it is now recommended to instead use the newly exported vueIntegration() and its tracingOptions option to configure tracing options in the Nuxt SDK:

  // sentry.client.config.ts
  import * as Sentry from '@sentry/nuxt';
  Sentry.init({
  // ...
  integrations: [
  Sentry.vueIntegration({
  tracingOptions: {
  trackComponents: true,
  },
  }),
  ],
  });

Other Changes

• feat(browser-utils): Update web-vitals to v4.2.4 (#14439)
• feat(nuxt): Expose vueIntegration (#14526)
• fix(feedback): Handle css correctly in screenshot mode (#14535)

... (truncated)

Changelog

Sourced from @​sentry/browser's changelog.

8.42.0

Important Changes

• feat(react): React Router v7 support (library) (#14513)

  This release adds support for React Router v7 (library mode). Check out the docs on how to set up the integration: Sentry React Router v7 Integration Docs

Deprecations

• feat: Warn about source-map generation (#14533)

  In the next major version of the SDK we will change how source maps are generated when the SDK is added to an application. Currently, the implementation varies a lot between different SDKs and can be difficult to understand. Moving forward, our goal is to turn on source maps for every framework, unless we detect that they are explicitly turned off. Additionally, if we end up enabling source maps, we will emit a log message that we did so.

  With this particular release, we are emitting warnings that source map generation will change in the future and we print instructions on how to prepare for the next major.

• feat(nuxt): Deprecate tracingOptions in favor of vueIntegration (#14530)

  Currently it is possible to configure tracing options in two places in the Sentry Nuxt SDK:

  • In Sentry.init()
  • Inside tracingOptions in Sentry.init()

  For tree-shaking purposes and alignment with the Vue SDK, it is now recommended to instead use the newly exported vueIntegration() and its tracingOptions option to configure tracing options in the Nuxt SDK:

  // sentry.client.config.ts
  import * as Sentry from '@sentry/nuxt';
  Sentry.init({
  // ...
  integrations: [
  Sentry.vueIntegration({
  tracingOptions: {
  trackComponents: true,
  },
  }),
  ],
  });

Other Changes

• feat(browser-utils): Update web-vitals to v4.2.4 (#14439)
• feat(nuxt): Expose vueIntegration (#14526)
• fix(feedback): Handle css correctly in screenshot mode (#14535)

... (truncated)

Commits

• faa64d0 release: 8.42.0
• da3a72c Merge pull request #14538 from getsentry/prepare-release/8.42.0
• e695a5e meta(changelog): Update changelog for 8.42.0
• 0b349eb ci(deps): Bump codecov/codecov-action from 4 to 5 (#14537)
• 146bafc feat(nuxt): Deprecate tracingOptions in favor of vueIntegration (#14530)
• 87b789c feat(browser-utils): Update web-vitals to v4.2.4 (#14439)
• 9b9ec77 feat(nuxt): Expose vueIntegration (#14526)
• 44477df fix(feeback): Handle css correctly in screenshot mode (#14535)
• 3fdab04 feat: Warn about source-map generation (#14533)
• e17bd91 chore: Dedupe @sentry/core imports (#14529)
• 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)

[coveralls]

coverage: 56.659% (-0.05%) from 56.705%
when pulling 1a1d8d7 on dependabot/npm_and_yarn/sentry/browser-8.42.0
into 39a09e8 on master.

[shaunanoordin]

Are you kidding me Dependabot? We've been through this before.

• You tried bumping v7 to v8 previously in Bump @sentry/browser from 7.100.1 to 8.36.0 #7206
• I foolishly approved this PR, not realising that despite the passing tests, it broke the website.
• We reverted to v7 in Revert "Bump @sentry/browser from 7.100.1 to 8.36.0" #7209
• And then I had to manually update to the latest version of v7 in [Security] Update @sentry/browser to 7.120.0 #7220

Let's not do this again, there's no reason to jump to v8 at the moment.

[shaunanoordin]

@dependabot ignore this major version

[dependabot]

OK, I won't notify you about version 8.x.x again, unless you re-open this PR.