Bump @sentry/react from 10.5.0 to 10.9.0

[dependabot]

Bumps @sentry/react from 10.5.0 to 10.9.0.

Release notes

Sourced from @​sentry/react's releases.

10.9.0

Important Changes

• feat(node): Update httpIntegration handling of incoming requests (#17371)

This version updates the handling of the Node SDK of incoming requests. Instead of relying on @​opentelemetry/instrumentation-http, we now handle incoming request instrumentation internally, ensuring that we can optimize performance as much as possible and avoid interop problems.

This change should not affect you, unless you're relying on very in-depth implementation details. Importantly, this also drops the _experimentalConfig option of the integration - this will no longer do anything. Finally, you can still pass instrumentation.{requestHook,responseHook,applyCustomAttributesOnSpan} options, but they are deprecated and will be removed in v11. Instead, you can use the new incomingRequestSpanHook configuration option if you want to adjust the incoming request span.

Other Changes

• feat(browser): Add replay.feedback CDN bundle (#17496)
• feat(browser): Export sendFeedback from CDN bundles (#17495)
• fix(astro): Ensure span name from beforeStartSpan isn't overwritten (#17500)
• fix(browser): Ensure source is set correctly when updating span name in-place in beforeStartSpan (#17501)
• fix(core): Only set template attributes on logs if parameters exist (#17480)
• fix(nextjs): Fix parameterization for root catchall routes (#17489)
• fix(node-core): Shut down OTel TraceProvider when calling Sentry.close() (#17499)

• chore: Add changelog script back to package.json (#17517)
• chore: Ensure prettier is run on all files (#17497)
• chore: Ignore prettier commit for git blame (#17498)
• chore: Remove experimental from Nuxt SDK package description (#17483)
• ci: Capture overhead in node app (#17420)
• ci: Ensure we fail on cancelled jobs (#17506)
• ci(deps): bump actions/checkout from 4 to 5 (#17505)
• ci(deps): bump actions/create-github-app-token from 2.0.6 to 2.1.1 (#17504)
• test(aws): Improve reliability on CI (#17502)

Bundle size 📦

Path	Size
@​sentry/browser	23.59 KB
@​sentry/browser - with treeshaking flags	22.2 KB
@​sentry/browser (incl. Tracing)	38.93 KB
@​sentry/browser (incl. Tracing, Replay)	76.4 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags	66.43 KB
@​sentry/browser (incl. Tracing, Replay with Canvas)	80.97 KB
@​sentry/browser (incl. Tracing, Replay, Feedback)	92.81 KB
@​sentry/browser (incl. Feedback)	39.88 KB
@​sentry/browser (incl. sendFeedback)	28.13 KB
@​sentry/browser (incl. FeedbackAsync)	32.92 KB
@​sentry/react	25.27 KB

... (truncated)

Changelog

Sourced from @​sentry/react's changelog.

10.9.0

Important Changes

• feat(node): Update httpIntegration handling of incoming requests (#17371)

This version updates the handling of the Node SDK of incoming requests. Instead of relying on @​opentelemetry/instrumentation-http, we now handle incoming request instrumentation internally, ensuring that we can optimize performance as much as possible and avoid interop problems.

This change should not affect you, unless you're relying on very in-depth implementation details. Importantly, this also drops the _experimentalConfig option of the integration - this will no longer do anything. Finally, you can still pass instrumentation.{requestHook,responseHook,applyCustomAttributesOnSpan} options, but they are deprecated and will be removed in v11. Instead, you can use the new incomingRequestSpanHook configuration option if you want to adjust the incoming request span.

Other Changes

• feat(browser): Add replay.feedback CDN bundle (#17496)
• feat(browser): Export sendFeedback from CDN bundles (#17495)
• fix(astro): Ensure span name from beforeStartSpan isn't overwritten (#17500)
• fix(browser): Ensure source is set correctly when updating span name in-place in beforeStartSpan (#17501)
• fix(core): Only set template attributes on logs if parameters exist (#17480)
• fix(nextjs): Fix parameterization for root catchall routes (#17489)
• fix(node-core): Shut down OTel TraceProvider when calling Sentry.close() (#17499)

• chore: Add changelog script back to package.json (#17517)
• chore: Ensure prettier is run on all files (#17497)
• chore: Ignore prettier commit for git blame (#17498)
• chore: Remove experimental from Nuxt SDK package description (#17483)
• ci: Capture overhead in node app (#17420)
• ci: Ensure we fail on cancelled jobs (#17506)
• ci(deps): bump actions/checkout from 4 to 5 (#17505)
• ci(deps): bump actions/create-github-app-token from 2.0.6 to 2.1.1 (#17504)
• test(aws): Improve reliability on CI (#17502)

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:

... (truncated)

Commits

• 417cf57 release: 10.9.0
• 143510b meta(changelog): Update changelog for 10.9.0 (#17518)
• 10b5928 meta(changelog): Update changelog for 10.9.0
• 14eba56 chore: Add changelog script back to package.json (#17517)
• 84243e6 feat(node): Update httpIntegration handling of incoming requests (#17371)
• 12528ec ci(deps): bump actions/checkout from 4 to 5 (#17505)
• dcbe98d ci(deps): bump actions/create-github-app-token from 2.0.6 to 2.1.1 (#17504)
• 94b268d ci: Capture overhead in node app (#17420)
• d269f1c ci: Ensure we fail on cancelled jobs (#17506)
• 1df660b fix(browser): Ensure source is set correctly when updating span name in-place...
• 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)

[dependabot]

Superseded by #823.