Bump @sentry/browser from 7.113.0 to 8.27.0

[dependabot]

Bumps @sentry/browser from 7.113.0 to 8.27.0.

Release notes

Sourced from @​sentry/browser's releases.

8.27.0

Important Changes

• fix(nestjs): Exception filters in main app module are not being executed (#13278)

  With this release nestjs error monitoring is no longer automatically set up after adding the SentryModule to your application, which led to issues in certain scenarios. You will now have to either add the SentryGlobalFilter to your main module providers or decorate the catch() method in your existing global exception filters with the newly released @WithSentry() decorator. See the docs for more details.

Other Changes

• feat: Add options for passing nonces to feedback integration (#13347)
• feat: Add support for SENTRY_SPOTLIGHT env var in Node (#13325)
• feat(deps): bump @​prisma/instrumentation from 5.17.0 to 5.18.0 (#13327)
• feat(feedback): Improve error message for 403 errors (#13441)
• fix(deno): Don't rely on Deno.permissions.querySync (#13378)
• fix(replay): Ensure we publish replay CDN bundles (#13437)

Work in this release was contributed by @​charpeni. Thank you for your contribution!

8.26.0

Important Changes

• feat(node): Add fsInstrumentation (#13291)

  This release adds fsIntegration, an integration that instruments the fs API to the Sentry Node SDK. The integration creates spans with naming patterns of fs.readFile, fs.unlink, and so on.

  This integration is not enabled by default and needs to be registered in your Sentry.init call. You can configure via options whether to include path arguments or error messages as span attributes when an fs call fails:

  Sentry.init({
    integrations: [
      Sentry.fsIntegration({
        recordFilePaths: true,
        recordErrorMessagesAsSpanAttributes: true,
      }),
    ],
  });

  WARNING: This integration may add significant overhead to your application. Especially in scenarios with a lot of file I/O, like for example when running a framework dev server, including this integration can massively slow down your application.

Other Changes

... (truncated)

Changelog

Sourced from @​sentry/browser's changelog.

8.27.0

Important Changes

• fix(nestjs): Exception filters in main app module are not being executed (#13278)

  With this release nestjs error monitoring is no longer automatically set up after adding the SentryModule to your application, which led to issues in certain scenarios. You will now have to either add the SentryGlobalFilter to your main module providers or decorate the catch() method in your existing global exception filters with the newly released @WithSentry() decorator. See the docs for more details.

Other Changes

• feat: Add options for passing nonces to feedback integration (#13347)
• feat: Add support for SENTRY_SPOTLIGHT env var in Node (#13325)
• feat(deps): bump @​prisma/instrumentation from 5.17.0 to 5.18.0 (#13327)
• feat(feedback): Improve error message for 403 errors (#13441)
• fix(deno): Don't rely on Deno.permissions.querySync (#13378)
• fix(replay): Ensure we publish replay CDN bundles (#13437)

Work in this release was contributed by @​charpeni. Thank you for your contribution!

8.26.0

Important Changes

• feat(node): Add fsInstrumentation (#13291)

  This release adds fsIntegration, an integration that instruments the fs API to the Sentry Node SDK. The integration creates spans with naming patterns of fs.readFile, fs.unlink, and so on.

  This integration is not enabled by default and needs to be registered in your Sentry.init call. You can configure via options whether to include path arguments or error messages as span attributes when an fs call fails:

  Sentry.init({
    integrations: [
      Sentry.fsIntegration({
        recordFilePaths: true,
        recordErrorMessagesAsSpanAttributes: true,
      }),
    ],
  });

  WARNING: This integration may add significant overhead to your application. Especially in scenarios with a lot of file I/O, like for example when running a framework dev server, including this integration can massively slow down your application.

... (truncated)

Commits

• 66a6316 release: 8.27.0
• 706ebd3 Merge pull request #13474 from getsentry/prepare-release/8.27.0
• b0180be Merge branch 'master' into prepare-release/8.27.0
• 205f127 meta: Update CHANGELOG for 8.27.0
• ea847d1 ci: Don't fail profiling bindings job on cache miss (#13464)
• 5b9d3bb ci: Always run build on develop branch (#13404)
• 195482c ci: Stabilize CI dependency cache key (#13401)
• 6cb6999 test: Fix flaky csp test (#13376)
• 80a116b fix(replay): Ensure we publish replay CDN bundles (#13437)
• e6861cf feat(feedback): Improve error message for 403 errors (#13441)
• 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)

┆Issue is synchronized with this Jira Story

[dependabot]

Superseded by #12813.