fix(deps): update sentry-javascript monorepo to v9.9.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@sentry/browser (source)	9.7.0 -> 9.9.0
@sentry/node (source)	9.7.0 -> 9.9.0
@sentry/vue (source)	9.7.0 -> 9.9.0

---

Release Notes

getsentry/sentry-javascript (@​sentry/browser)

v9.9.0

Compare Source

Important Changes

• feat(nextjs): Support instrumentation-client.ts (#​15705)

  Next.js recently added a feature to support client-side (browser) instrumentation via the experimental.clientInstrumentationHook flag and the instrumentation-client.ts file.

  To be forwards compatible, the Sentry Next.js SDK will now pick up instrumentation-client.ts files even on older Next.js versions and add them to your client bundles.
  It is suggested that you either rename your sentry.client.config.ts file to instrumentation-client.ts, or if you already happen to have a instrumentation-client.ts file move the contents of sentry.client.config.ts to instrumentation-client.ts.

• feat(browser): Add previous_trace span links (#​15569)

  The @sentry/browser SDK and SDKs based on @sentry/browser now emits a link from the first root span of a newly started trace to the root span of a previously started trace. You can control this feature via an option in browserTracingIntegration():

  Sentry.init({
    dsn: 'your-dsn-here'
    integrations: [
      Sentry.browserTracingIntegration({
        // Available settings:
        // - 'in-memory' (default): Stores previous trace information in memory
        // - 'session-storage': Stores previous trace information in the browser's `sessionStorage`
        // - 'off': Disable storing and sending previous trace information
        linkPreviousTrace: 'in-memory',
      }),
    ],
  });

• feat(browser): Add logger.X methods to browser SDK (#​15763)

  For Sentry's upcoming logging product, the SDK now supports sending logs via dedicated

  Sentry.init({
    dsn: 'your-dsn-here',
    _experiments: {
      enableLogs: true, // This is required to use the logging features
    },
  });
  
  Sentry.logger.info('This is a trace message', { userId: 123 });
  // See PR for better documentation

  Please note that the logs product is still in early access. See the link above for more information.

Other Changes

• feat(browser): Attach host as part of error message to "Failed to fetch" errors (#​15729)
• feat(core): Add parseStringToURL method (#​15768)
• feat(core): Optimize dropUndefinedKeys (#​15760)
• feat(node): Add fastify shouldHandleError (#​15771)
• fix(nuxt): Delete no longer needed Nitro 'close' hook (#​15790)
• perf(nestjs): Remove usage of addNonEnumerableProperty (#​15766)
• ref: Avoid some usage of dropUndefinedKeys() (#​15757)
• ref: Remove some usages of dropUndefinedKeys() (#​15781)
• ref(nextjs): Fix Next.js vercel-edge runtime package information (#​15789)

v9.8.0

Compare Source

• feat(node): Implement new continuous profiling API spec (#​15635)
• feat(profiling): Add platform to chunk envelope (#​15758)
• feat(react): Export captureReactException method (#​15746)
• fix(node): Check for res.end before passing to Proxy (#​15776)
• perf(core): Add short-circuits to eventFilters integration (#​15752)
• perf(node): Short circuit flushing on Vercel only for Vercel (#​15734)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

---

• Branch has one or more failed status checks