@sentry/nextjs breaking changes
Every breaking API change we have recorded in @sentry/nextjs on npm: 101 breaking changes in 5 versions. Below are its newest 5 versions, removals and renames first, each with its source.
Newest change September 23, 2026

On this page
11.0.0
- Removed
Safari 14 is no longer supported. Safari 15 or higher is required. github.com - Removed
Older TypeScript versions may not be compatible. Also down-leveled types are no longer emitted. github.com - Removed
Older Deno versions are no longer supported. Upgrade Deno to 2.8.3 or later. github.com - Removed
Minimum supported React version is now 17. github.com - Removed
Minimum supported version of @remix-run/node is now v2. github.com - Removed
Use --import to load the instrument file instead of --require. github.com - Removed
Minimum supported Next.js version is now 14. github.com - Removed
Node.js 18 is no longer supported. Upgrade Node.js to 20.19.0 or later before upgrading the SDK. github.com - Removed
_experiments.enableLogs
Logs are enabled by default, so you can omit the option. Use top-level enableLogs: false to opt out. github.com - Removed
--require
Load your instrument file with --import instead of --require. github.com
And 76 more in this version.
11.0.0-rc.0
- Removed
Deprecated build-time configuration options were removed. Move any remaining uses to their current replacements. github.com - Removed
Projects on Next.js 13 are no longer supported. Upgrade Next.js before updating the SDK. github.com - Removed
The SDK no longer supports older Node.js versions. Upgrade Node.js to 20.19.0 or later. github.com - Removed
config:SentryBuildOptions.unstable_sentryWebpackPluginOptions
The unstable_sentryWebpackPluginOptions option is removed. Stop passing it to withSentryConfig. npmjs.com - Removed
enableMetrics
The enableMetrics option is removed. Delete it from your configuration. github.com - Removed
sendDefaultPii
The sendDefaultPii option is removed. Configure data collection through the dataCollection option instead. github.com - Removed
withSentryConfig
withSentryConfig is now imported from @sentry/nextjs/config instead of the package root. npmjs.com - Behavior changed
The default environment and deploy names no longer carry the vercel- prefix. Update any filters or alerts that depend on it. github.com - Behavior changed
Next.js middleware spans now use the middleware span op. Update any span queries that match the old op. github.com - Behavior changed
Build-time orchestrion instrumentation is now auto-wired, which changes how the build instruments code. github.com
And 2 more in this version.
10.73.0
- Signature changed
withSentryConfig
Was function withSentryConfig<C>(nextConfig?: C, sentryBuildOptions?: SentryBuildOptions): C; now const withSentryConfig: typeof configSdk.withSentryConfig. npmjs.com
10.72.0
- Behavior changed
Errors your code catches are no longer sent to Sentry as unhandled crashes. Uncaught errors still reach Sentry's global error handlers and are captured as unhandled. github.com
10.71.0
- Default changed
enableLogs
The enableLogs client option now defaults to true. Nothing is captured unless you call the Sentry.logger APIs or add a log-forwarding integration; set enableLogs: false to opt out. github.com
Check your code
These are the changes. To see which of them reach your code, scan a public repository, or have your coding agent call check_code with your manifest or lockfile over MCP. The API reads every change in every version, not only the newest. On Team and up, a fix pull request opens for the changes that reach a connected repository. Nothing merges or deploys.

Put your code on continuous management.
Scan a public repository now, or give your agent one line.
See how out of date your code is.
Tell your agent what changed since it was trained.
claude mcp add --transport http since https://api.since.dev/mcp