build(deps): bump @sentry/nextjs from 10.46.0 to 11.0.0

[dependabot]

Bumps @sentry/nextjs from 10.46.0 to 11.0.0.

Release notes

Sourced from @​sentry/nextjs's releases.

11.0.0

Version 11.0.0 marks a major release of the Sentry JavaScript SDKs containing breaking changes. The goal of this release is to be better compatible with OpenTelemetry, make our integrations work across Node.js, Cloudflare, Bun and Deno through run-time and build-time instrumentation, and make span streaming and more permissive data collection the default.

How To Upgrade

Please carefully read through the migration guide in the Sentry docs on how to upgrade from version 10 to version 11. Make sure to select your specific platform/framework in the top left corner: https://docs.sentry.io/platforms/javascript/migration/v10-to-v11/

A comprehensive migration guide outlining all changes can be found within the Sentry JavaScript SDK Repository: https://github.com/getsentry/sentry-javascript/blob/develop/MIGRATION.md

Breaking Changes

All SDKs

• feat: Remove support for initialising via --require (#22513)
• feat!: Rename deprecated http.* span attributes (#23574)
• feat!: Rename deprecated net. span attributes (#23301)
• feat!: Replace skipOpenTelemetrySetup with enableOpenTelemetrySetup (#23199)
• feat!: Replace the deprecated http.target span attribute (#23575)
• feat!: Require Node >=20.19.0 as minimum supported version (#22558)
• feat!: Use handler span op for terminal request handlers (#22871)
• feat!: Use middleware span op for web-server middleware (#22852)
• feat(frameworks)!: Use function op for framework functions (#23047)
• feat(node/cloudflare)!: Remove deprecated honoIntegration (#22480)
• feat(v11): Drop TypeScript 3.8 support (#18604)

AI integrations

• feat(langchain): Emit gen_ai.pipeline.name instead of langchain.chain.name (#23740)
• ref(anthropic)!: Move Anthropic AI integration to @sentry/server-utils (#22954)
• ref(google-genai)!: Move Google GenAI integration to @sentry/server-utils (#22959)
• ref(langchain)!: Move LangChain and LangGraph integrations to @sentry/server-utils (#22962)
• ref(langgraph)!: Drop gen_ai.create_agent spans (#22840)
• ref(openai)!: Move OpenAI AI integration to @sentry/server-utils (#22953)
• ref(vercel-ai)!: Move Vercel AI integration to @sentry/server-utils (#22964)
• ref(workers-ai)!: Move Workers AI integration to @sentry/server-utils (#22960)

@​sentry/angular

• feat(angular,ember,sveltekit)!: Use router span op for frontend routers (#23086)
• feat(angular)!: Use ui.mount and function span ops for tracing decorators (#22667)

@​sentry/astro

• feat(astro)!: Drop support for Astro 3 (#22683)
• feat(astro)!: Enable orchestrion instrumentation on Cloudflare Workers (#23003)
• feat(astro)!: Remove deprecated sourceMapsUploadOptions build option (#23630)
• feat(astro)!: Remove unstable_sentryVitePluginOptions (#23370)
• ref(astro)!: Migrate import hook to makeOrchestrionLoader (#22861)
• ref(astro)!: Remove deprecated release/debug conflict workaround from BuildTimeOptionsBase (#23270)

... (truncated)

Changelog

Sourced from @​sentry/nextjs's changelog.

11.0.0

Version 11.0.0 marks a major release of the Sentry JavaScript SDKs containing breaking changes. The goal of this release is to be better compatible with OpenTelemetry, make our integrations work across Node.js, Cloudflare, Bun and Deno through run-time and build-time instrumentation, and make span streaming and more permissive data collection the default.

How To Upgrade

Please carefully read through the migration guide in the Sentry docs on how to upgrade from version 10 to version 11. Make sure to select your specific platform/framework in the top left corner: https://docs.sentry.io/platforms/javascript/migration/v10-to-v11/

A comprehensive migration guide outlining all changes can be found within the Sentry JavaScript SDK Repository: https://github.com/getsentry/sentry-javascript/blob/develop/MIGRATION.md

Breaking Changes

All SDKs

• feat: Remove support for initialising via --require (#22513)
• feat!: Rename deprecated http.* span attributes (#23574)
• feat!: Rename deprecated net. span attributes (#23301)
• feat!: Replace skipOpenTelemetrySetup with enableOpenTelemetrySetup (#23199)
• feat!: Replace the deprecated http.target span attribute (#23575)
• feat!: Require Node >=20.19.0 as minimum supported version (#22558)
• feat!: Use handler span op for terminal request handlers (#22871)
• feat!: Use middleware span op for web-server middleware (#22852)
• feat(frameworks)!: Use function op for framework functions (#23047)
• feat(node/cloudflare)!: Remove deprecated honoIntegration (#22480)
• feat(v11): Drop TypeScript 3.8 support (#18604)

AI integrations

• feat(langchain): Emit gen_ai.pipeline.name instead of langchain.chain.name (#23740)
• ref(anthropic)!: Move Anthropic AI integration to @sentry/server-utils (#22954)
• ref(google-genai)!: Move Google GenAI integration to @sentry/server-utils (#22959)
• ref(langchain)!: Move LangChain and LangGraph integrations to @sentry/server-utils (#22962)
• ref(langgraph)!: Drop gen_ai.create_agent spans (#22840)
• ref(openai)!: Move OpenAI AI integration to @sentry/server-utils (#22953)
• ref(vercel-ai)!: Move Vercel AI integration to @sentry/server-utils (#22964)
• ref(workers-ai)!: Move Workers AI integration to @sentry/server-utils (#22960)

@​sentry/angular

• feat(angular,ember,sveltekit)!: Use router span op for frontend routers (#23086)
• feat(angular)!: Use ui.mount and function span ops for tracing decorators (#22667)

@​sentry/astro

• feat(astro)!: Drop support for Astro 3 (#22683)
• feat(astro)!: Enable orchestrion instrumentation on Cloudflare Workers (#23003)
• feat(astro)!: Remove deprecated sourceMapsUploadOptions build option (#23630)
• feat(astro)!: Remove unstable_sentryVitePluginOptions (#23370)
• ref(astro)!: Migrate import hook to makeOrchestrionLoader (#22861)

... (truncated)

Commits

• 3e02c87 release: 11.0.0
• fe07bdf Merge pull request #24620 from getsentry/prepare-release/11.0.0
• ed38fe7 meta(changelog): Update changelog for 11.0.0
• ea27349 docs: Fix Solid, SolidStart, and NestJS README snippets (#24571)
• 84027a1 fix(tanstackstart-react): Reject non-POST requests to the managed tunnel rout...
• 6a99951 feat(tanstackstart-react): Emit low-cardinality names for function spans (#...
• 3fdf506 chore: Add external contributor to CHANGELOG.md (#24616)
• bf7b9b2 fix(cloudflare): Bind pass-through Queue producer methods to the binding (#24...
• 1960dad fix(server-utils): Stop the orchestrion Vite plugin from adding an empty ssr ...
• e281d82 chore: Remove CLAUDE.md symlink (#24524)
• Additional commits viewable in compare view

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
betterman	Ready	Preview	Sep 29, 2026 5:32am UTC

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: cf197873-b207-432f-9fc2-06a8a5adcc2b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[greptile-apps]

Confidence Score: 4/5

[High risk] Updates error tracking library to a major version.

The PR appears safe to merge, with a non-blocking gap in validation of enabled Sentry error reporting.

Findings

1.  Enabled error reporting goes unchecked ▶

Fix with agent prompt

### Issue 1
nextjs/package.json:16
The CI build runs without `NEXT_PUBLIC_SENTRY_DSN`, so all four Sentry initializers set `enabled: false`. It cannot check whether this major upgrade preserves error reporting when Sentry is enabled, including the `captureRequestError` hook. A focused enabled-path check would catch an integration regression before deployment.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

The PR upgrades the production Next.js application from Sentry 10.46.0 to 11.0.0 and refreshes its locked dependency graph.

• The configured build runtimes meet the new Sentry engine requirement.
• The enabled error-reporting path needs a focused check; the current CI build exercises it only with Sentry disabled.

_{Reviews (1) · Last reviewed commit: "build(deps): bump @sentry/nextjs from 10..."}