Bump the sentry group with 3 updates

[dependabot]

Bumps the sentry group with 3 updates: @sentry/browser, @sentry/react and @sentry/types.

Updates @sentry/browser from 9.8.0 to 9.9.0

Release notes

Sourced from @​sentry/browser's releases.

9.9.0

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)

... (truncated)

Changelog

Sourced from @​sentry/browser's changelog.

9.9.0

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

... (truncated)

Commits

• 43c4c83 release: 9.9.0
• 80e19f2 Merge pull request #15791 from getsentry/prepare-release/9.9.0
• bb358cf meta: Update changelog for 9.9.0
• 0cf8ec2 feat(browser): Attach host as part of error message to "Failed to fetch" erro...
• 79ff8f2 fix(nuxt): Delete no longer needed Nitro 'close' hook (#15790)
• 006479c ref(nextjs): Fix Next.js vercel-edge runtime package information (#15789)
• 57f04e0 ref: Remove some usages of dropUndefinedKeys() (#15781)
• 50d2514 feat(node): Add fastify shouldHandleError (#15771)
• ba5993c feat(core): Add parseStringToURL method (#15768)
• e55b8ee feat(browser): Add logger.X methods to browser SDK (#15763)
• Additional commits viewable in compare view

Updates @sentry/react from 9.8.0 to 9.9.0

Release notes

Sourced from @​sentry/react's releases.

9.9.0

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)

... (truncated)

Changelog

Sourced from @​sentry/react's changelog.

9.9.0

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

... (truncated)

Commits

• 43c4c83 release: 9.9.0
• 80e19f2 Merge pull request #15791 from getsentry/prepare-release/9.9.0
• bb358cf meta: Update changelog for 9.9.0
• 0cf8ec2 feat(browser): Attach host as part of error message to "Failed to fetch" erro...
• 79ff8f2 fix(nuxt): Delete no longer needed Nitro 'close' hook (#15790)
• 006479c ref(nextjs): Fix Next.js vercel-edge runtime package information (#15789)
• 57f04e0 ref: Remove some usages of dropUndefinedKeys() (#15781)
• 50d2514 feat(node): Add fastify shouldHandleError (#15771)
• ba5993c feat(core): Add parseStringToURL method (#15768)
• e55b8ee feat(browser): Add logger.X methods to browser SDK (#15763)
• Additional commits viewable in compare view

Updates @sentry/types from 9.8.0 to 9.9.0

Release notes

Sourced from @​sentry/types's releases.

9.9.0

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)

... (truncated)

Changelog

Sourced from @​sentry/types's changelog.

9.9.0

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

... (truncated)

Commits

• 43c4c83 release: 9.9.0
• 80e19f2 Merge pull request #15791 from getsentry/prepare-release/9.9.0
• bb358cf meta: Update changelog for 9.9.0
• 0cf8ec2 feat(browser): Attach host as part of error message to "Failed to fetch" erro...
• 79ff8f2 fix(nuxt): Delete no longer needed Nitro 'close' hook (#15790)
• 006479c ref(nextjs): Fix Next.js vercel-edge runtime package information (#15789)
• 57f04e0 ref: Remove some usages of dropUndefinedKeys() (#15781)
• 50d2514 feat(node): Add fastify shouldHandleError (#15771)
• ba5993c feat(core): Add parseStringToURL method (#15768)
• e55b8ee feat(browser): Add logger.X methods to browser SDK (#15763)
• 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Looks like these dependencies are no longer updatable, so this is no longer needed.