build(deps): bump @sentry/browser from 10.7.0 to 10.8.0

[dependabot]

Bumps @sentry/browser from 10.7.0 to 10.8.0.

Release notes

Sourced from @​sentry/browser's releases.

10.8.0

Important Changes

• feat(sveltekit): Add Compatibility for builtin SvelteKit Tracing (#17423)

  This release makes the @sentry/sveltekit SDK compatible with SvelteKit's native observability support introduced in SvelteKit version 2.31.0. If you enable both, instrumentation and tracing, the SDK will now initialize early enough to set up additional instrumentation like database queries and it will pick up spans emitted from SvelteKit.

  We will follow up with docs how to set up the SDK soon. For now, If you're on SvelteKit version 2.31.0 or newer, you can easily opt into the new feature:

  1. Enable experimental tracing and instrumentation support in svelte.config.js:

  2. Move your Sentry.init() call from src/hooks.server.(js|ts) to the new instrumentation.server.(js|ts) file:

     // instrumentation.server.ts
     import * as Sentry from '@sentry/sveltekit';
     Sentry.init({
     dsn: '...',
     // rest of your config
     });

     The rest of your Sentry config in hooks.server.ts (sentryHandle and handleErrorWithSentry) should stay the same.

  If you prefer to stay on the hooks-file based config for now, the SDK will continue to work as previously.

  Thanks to the Svelte team and @​elliott-with-the-longest-name-on-github for implementing observability support and for reviewing our PR!

Other Changes

• fix(react): Avoid multiple name updates on navigation spans (#17438)

• test(profiling): Add tests for current state of profiling (#17470)

Bundle size 📦

Path	Size
@​sentry/browser	23.59 KB
@​sentry/browser - with treeshaking flags	22.2 KB
@​sentry/browser (incl. Tracing)	38.94 KB
@​sentry/browser (incl. Tracing, Replay)	76.4 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags	66.43 KB

... (truncated)

Changelog

Sourced from @​sentry/browser's changelog.

10.8.0

Important Changes

• feat(sveltekit): Add Compatibility for builtin SvelteKit Tracing (#17423)

  This release makes the @sentry/sveltekit SDK compatible with SvelteKit's native observability support introduced in SvelteKit version 2.31.0. If you enable both, instrumentation and tracing, the SDK will now initialize early enough to set up additional instrumentation like database queries and it will pick up spans emitted from SvelteKit.

  We will follow up with docs how to set up the SDK soon. For now, If you're on SvelteKit version 2.31.0 or newer, you can easily opt into the new feature:

  1. Enable experimental tracing and instrumentation support in svelte.config.js:

  2. Move your Sentry.init() call from src/hooks.server.(js|ts) to the new instrumentation.server.(js|ts) file:

     // instrumentation.server.ts
     import * as Sentry from '@sentry/sveltekit';
     Sentry.init({
     dsn: '...',
     // rest of your config
     });

     The rest of your Sentry config in hooks.server.ts (sentryHandle and handleErrorWithSentry) should stay the same.

  If you prefer to stay on the hooks-file based config for now, the SDK will continue to work as previously.

  Thanks to the Svelte team and @​elliott-with-the-longest-name-on-github for implementing observability support and for reviewing our PR!

Other Changes

• fix(react): Avoid multiple name updates on navigation spans (#17438)

• test(profiling): Add tests for current state of profiling (#17470)

Commits

• bd8458e release: 10.8.0
• dbdddc8 Merge pull request #17481 from getsentry/prepare-release/10.8.0
• f5d4bd6 meta(changelog): Update changelog for 10.8.0
• dfdc3b0 test(profiling): Add tests for current state of profiling (#17470)
• 895b385 fix(react): Avoid multiple name updates on navigation spans (#17438)
• e6e20d8 feat(sveltekit): Add Compatibility for builtin SvelteKit Tracing (#17423)
• 7e24422 Merge pull request #17472 from getsentry/master
• 27e97b0 Merge branch 'release/10.7.0'
• See full diff 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 will merge this PR once CI passes on it, as requested by @openhpi-bot.

---

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)

[openhpi-bot]

@dependabot merge