chore(deps): Bump @sentry/nextjs from 10.74.0 to 11.4.0 in /js

[dependabot]

Bumps @sentry/nextjs from 10.74.0 to 11.4.0.

Release notes

Sourced from @​sentry/nextjs's releases.

11.4.0

• feat(sveltekit): Support stable SvelteKit 3 (#25009)
• fix(remix): Match the Remix 3.0.0 package versions (#25008)

Bundle size 📦

Path	Size
@​sentry/browser	28.82 KB
@​sentry/browser - with treeshaking flags	27.03 KB
@​sentry/browser - with treeshaking flags tracing without tracing	26.93 KB
@​sentry/browser (incl. Tracing)	50.24 KB
@​sentry/browser (incl. Tracing + Span Streaming)	50.26 KB
@​sentry/browser (incl. Tracing, Profiling)	53.18 KB
@​sentry/browser (incl. Tracing, Replay)	88.91 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags	78.15 KB
@​sentry/browser (incl. Tracing, Replay with Canvas)	93.5 KB
@​sentry/browser (incl. Tracing, Replay, Feedback)	106.16 KB
@​sentry/browser (incl. Feedback)	45.94 KB
@​sentry/browser (incl. sendFeedback)	33.76 KB
@​sentry/browser (incl. FeedbackAsync)	38.75 KB
@​sentry/browser (incl. Metrics)	29.82 KB
@​sentry/browser (incl. Logs)	30.1 KB
@​sentry/browser (incl. Metrics & Logs)	30.74 KB
@​sentry/react	30.63 KB
@​sentry/react (incl. Tracing)	52.54 KB
@​sentry/vue	36.63 KB
@​sentry/vue (incl. Tracing)	53.06 KB
@​sentry/svelte	28.86 KB
@​sentry/remix (Remix 3 client bundle)	54.47 KB
CDN Bundle	30.49 KB
CDN Bundle (incl. Tracing)	50.76 KB
CDN Bundle (incl. Logs, Metrics)	32.68 KB
CDN Bundle (incl. Tracing, Logs, Metrics)	52.65 KB
CDN Bundle (incl. Replay, Logs, Metrics)	72.47 KB
CDN Bundle (incl. Tracing, Replay)	87.46 KB
CDN Bundle (incl. Tracing, Replay, Logs, Metrics)	89.39 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	93.48 KB
CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics)	95.42 KB
CDN Bundle - uncompressed	89.98 KB
CDN Bundle (incl. Tracing) - uncompressed	150.87 KB
CDN Bundle (incl. Logs, Metrics) - uncompressed	96.4 KB
CDN Bundle (incl. Tracing, Logs, Metrics) - uncompressed	156.69 KB
CDN Bundle (incl. Replay, Logs, Metrics) - uncompressed	222.93 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	267.8 KB
CDN Bundle (incl. Tracing, Replay, Logs, Metrics) - uncompressed	273.6 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	281.18 KB
CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics) - uncompressed	286.97 KB
@​sentry/nextjs (client)	55 KB
@​sentry/sveltekit (client)	50.65 KB

... (truncated)

Changelog

Sourced from @​sentry/nextjs's changelog.

11.4.0

• feat(sveltekit): Support stable SvelteKit 3 (#25009)
• fix(remix): Match the Remix 3.0.0 package versions (#25008)

11.3.0

Important Changes

• Remix 3 support (alpha, may break in minor releases)

  • feat(remix): Add Remix 3 browser SDK with a bundled client entry (#24802)
  • feat(remix): Add source map upload for Remix 3 (#24943)
  • feat(remix): Capture Remix 3 component render errors (#24873)
  • feat(remix): Complete Remix 3 server error handling (#24878)
  • feat(remix): Inject debug IDs through the Remix 3 asset server (#24761)
  • feat(remix): Run the orchestrion transform on Remix 3 browser modules (#24894)

• feat(nextjs): Add cache_origin span links to use cache hit spans (#24821)

  A cache.get span for a "use cache" hit now carries a span link (sentry.link.type: 'cache_origin') to the cache.put span of the request that filled the cache entry, connecting the trace that reads a cached value to the trace that produced it.

• fix(cloudflare): Don't treat DO constructor work as incoming RPC calls (#24829)

  Durable Object constructors now run in their own isolation scope. When work that the constructor starts, for example a blockConcurrencyWhile callback, calls a method of the instance, that call is no longer treated as an incoming RPC call, so an error the instance catches itself is no longer reported as unhandled. As a result, Sentry.setTag(), setUser() and setContext() in a constructor now apply only to that constructor work. They no longer reach later fetch, RPC or alarm invocations, because the scope they used to write to is shared by every Durable Object and handler in the isolate. Use initialScope for static data, and set per-instance data in each handler.

• fix(effect)!: Change peerDependency to v4 and fix currentSpan (#24940)

  @sentry/effect now requires a stable Effect v4 release. Effect v4 beta and release candidate versions are no longer supported. @sentry/effect is in alpha, so this ships in a minor release.

Other Changes

• feat(astro): Register astro route provider (#23792)
• feat(cloudflare): Trace TypeSafe Jev calls in Workers AI as evaluate spans (#24833)
• feat(core): Add route provider API for parameterized route resolution (#23551)
• feat(deps): bump devalue from 5.9.2 to 5.9.4 (#24964)
• feat(effect): Add opt-in for external span parents and isolate root spans (#23900)
• feat(nextjs): Register nextjs route provider (#23552)
• feat(nuxt): Register nuxt route provider (#23794)
• feat(remix): Register remix route provider (#23791)
• feat(vue): Register Vue route provider (#23793)
• fix(bundler-plugins): Keep debug IDs on Vite source maps after the preload rewrite (#24920)
• fix(bundler-plugins): Stabilize debug IDs for Rolldown and Vite 8 builds (#24919)
• fix(cloudflare): Skip binding instrumentation work when spans are not sent (#24655)
• fix(core, node, bun, deno): Align server span client address with event IP (#24767)
• fix(hono): Return the existing client on repeated init in Bun and Deno (#24520)
• fix(nitro): Capture errors only through the Nitro error hook (#24952)
• fix(profiling-node): Send profile chunks with client.sendEnvelope (#24896)
• fix(react-router): Avoid duplicating Vite config arrays (#24930)
• fix(react-router): Resolve the Cloudflare entry in Workers and skip trace meta tags in prerendered pages (#24866)

... (truncated)

Commits

• 7f13c61 release: 11.4.0
• fb73adb Merge pull request #25010 from getsentry/prepare-release/11.4.0
• de3fb96 meta(changelog): Update changelog for 11.4.0
• 4f0fd84 feat(sveltekit): Support stable SvelteKit 3 (#25009)
• ba4db28 fix(remix): Match the Remix 3.0.0 package versions (#25008)
• c8738fb Merge pull request #24991 from getsentry/master
• 5f88a0b Merge commit '1e82c8f33488bc54364d343a7c5ab33ed9056f39'
• 1e82c8f release: 11.3.0
• 481c43c Merge pull request #24987 from getsentry/prepare-release/11.3.0
• 1c7308d meta(changelog): Update changelog for 11.3.0
• 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 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)

[iamcxa]

@dependabot[bot] Automated review of the @sentry/nextjs 10.74.0 → 11.4.0 bump.

Verification Summary

Check	Result
pnpm install --frozen-lockfile	pass
pnpm type:check	clean
pnpm lint	clean
pnpm test	pass
pnpm run build	pass

Findings

• MEDIUM — this bump leaves two Sentry majors in the OSS app. Only @sentry/nextjs moves to v11. @sentry/react stays at ^10.74.0, and so does the @datarecce/ui peer range ^10.0.0. The lockfile now holds both @sentry/core@10.74.0 and @sentry/core@11.4.0 (see inline comment).

Notes

• The new transitive sentry@0.45.0 package comes from @sentry/bundler-plugins@11.4.0, which is Sentry's own package. It has no install scripts in the lockfile.
• The OSS app has no Sentry.init or withSentryConfig, so the runtime impact today is limited to the captureException calls in app/error.tsx and app/global-error.tsx.

The event is COMMENT rather than APPROVE because of the version-alignment finding above. Suggest closing this PR and doing the v11 migration in the next recce-dev:address-dependabot consolidation, with @sentry/react and the @datarecce/ui peer range updated together.

[iamcxa]

MEDIUM — mixed Sentry SDK majors. @sentry/nextjs moves to ^11.4.0, but @sentry/react on the next line stays at ^10.74.0. js/packages/ui/package.json also still declares the peer "@sentry/react": "^10.0.0". As a result, the lockfile now resolves both @sentry/core@10.74.0 and @sentry/core@11.4.0.

Sentry requires every @sentry/* package to be on the same version. Each major keeps its own versioned global carrier. If a client is ever initialized through @sentry/nextjs v11, captureException calls from @sentry/react v10 will not reach it. Those calls come from ErrorBoundary.tsx and useInlineProfileDistribution.ts in @datarecce/ui, and they would be dropped silently. The two copies also add bundle weight.

Suggested fix: bump @sentry/react to ^11.4.0 in the same change. Widen the @datarecce/ui peer range to ^10.0.0 || ^11.0.0, or move it to v11 only. Then check the v11 migration notes for the ErrorBoundary/FallbackRender APIs.