feat(nextjs): Add `sourcemaps.filesToDeleteAfterUpload` as a top-level option by chargome · Pull Request #19280 · getsentry/sentry-javascript

chargome · 2026-02-11T11:24:35Z

Adds sourcemaps.filesToDeleteAfterUpload to the Next.js SDK's SentryBuildOptions type, allowing users to specify custom glob patterns for
source map deletion after upload.
When set, this option overrides the default deletion patterns computed by deleteSourcemapsAfterUpload, giving users fine-grained control — including the ability to target server-side source maps if desired.

closes#19235

linear · 2026-02-11T11:24:39Z

JS-1665 `deleteSourcemapsAfterUpload: true` does not delete .next/server/** source maps

github-actions · 2026-02-11T11:38:13Z

Codecov Results 📊

Generated by Codecov Action

cursor · 2026-02-12T09:57:27Z

+
+ if (sentryBuildOptions.debug && userFilesToDeleteAfterUpload !== undefined) {
+ // eslint-disable-next-line no-console
+ console.debug('[@sentry/nextjs] Skipping auto-deletion of source maps as user has provided filesToDeleteAfterUpload:', userFilesToDeleteAfterUpload);


Debug log misleadingly implies deletion is skipped entirely
Low Severity
The debug log message says "Skipping auto-deletion of source maps as user has provided filesToDeleteAfterUpload" which implies deletion is being skipped. In reality, the user's custom filesToDeleteAfterUpload patterns will be used to delete files — it's only the auto-computed patterns that are skipped. A user debugging with debug: true could misinterpret this as "no deletion is happening" when files are indeed being deleted using their custom patterns. The log was specifically requested to help users understand what patterns are being used, but it focuses on what's skipped rather than what's happening.

github-actions · 2026-02-12T10:02:07Z

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	9,005	-	9,512	-5%
GET With Sentry	1,700	19%	1,616	+5%
GET With Sentry (error only)	6,130	68%	6,033	+2%
POST Baseline	1,152	-	1,197	-4%
POST With Sentry	561	49%	590	-5%
POST With Sentry (error only)	1,044	91%	1,051	-1%
MYSQL Baseline	3,269	-	3,335	-2%
MYSQL With Sentry	436	13%	464	-6%
MYSQL With Sentry (error only)	2,624	80%	2,689	-2%

View base workflow run

…ue-does-not-delete-nextserver-source

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

cursor · 2026-02-13T08:15:58Z

+ buildTool,
+ deleteSourcemapsAfterUpload,
+ useRunAfterProductionCompileHook,
+ );


User patterns bypass deleteSourcemapsAfterUpload: false guard
Medium Severity
When filesToDeleteAfterUpload is provided, it completely bypasses the deleteSourcemapsAfterUpload check. If a user sets deleteSourcemapsAfterUpload: false alongside filesToDeleteAfterUpload, source maps will still be deleted — contradicting the user's explicit opt-out. The deleteSourcemapsAfterUpload: false setting is expected to act as a master toggle preventing all deletion.

ref getsentry/sentry-javascript#19235 ref getsentry/sentry-javascript#19280 --------- Co-authored-by: Alex Krawiec <alex.krawiec@sentry.io>

chargome · 2026-02-11T11:24:35Z

Adds sourcemaps.filesToDeleteAfterUpload to the Next.js SDK's SentryBuildOptions type, allowing users to specify custom glob patterns for
source map deletion after upload.
When set, this option overrides the default deletion patterns computed by deleteSourcemapsAfterUpload, giving users fine-grained control — including the ability to target server-side source maps if desired.

closes#19235

linear · 2026-02-11T11:24:39Z

JS-1665 `deleteSourcemapsAfterUpload: true` does not delete .next/server/** source maps

github-actions · 2026-02-11T11:38:13Z

Codecov Results 📊

Generated by Codecov Action

cursor · 2026-02-12T09:57:27Z

+
+ if (sentryBuildOptions.debug && userFilesToDeleteAfterUpload !== undefined) {
+ // eslint-disable-next-line no-console
+ console.debug('[@sentry/nextjs] Skipping auto-deletion of source maps as user has provided filesToDeleteAfterUpload:', userFilesToDeleteAfterUpload);


Debug log misleadingly implies deletion is skipped entirely
Low Severity
The debug log message says "Skipping auto-deletion of source maps as user has provided filesToDeleteAfterUpload" which implies deletion is being skipped. In reality, the user's custom filesToDeleteAfterUpload patterns will be used to delete files — it's only the auto-computed patterns that are skipped. A user debugging with debug: true could misinterpret this as "no deletion is happening" when files are indeed being deleted using their custom patterns. The log was specifically requested to help users understand what patterns are being used, but it focuses on what's skipped rather than what's happening.

github-actions · 2026-02-12T10:02:07Z

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	9,005	-	9,512	-5%
GET With Sentry	1,700	19%	1,616	+5%
GET With Sentry (error only)	6,130	68%	6,033	+2%
POST Baseline	1,152	-	1,197	-4%
POST With Sentry	561	49%	590	-5%
POST With Sentry (error only)	1,044	91%	1,051	-1%
MYSQL Baseline	3,269	-	3,335	-2%
MYSQL With Sentry	436	13%	464	-6%
MYSQL With Sentry (error only)	2,624	80%	2,689	-2%

View base workflow run

…ue-does-not-delete-nextserver-source

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

cursor · 2026-02-13T08:15:58Z

+ buildTool,
+ deleteSourcemapsAfterUpload,
+ useRunAfterProductionCompileHook,
+ );


User patterns bypass deleteSourcemapsAfterUpload: false guard
Medium Severity
When filesToDeleteAfterUpload is provided, it completely bypasses the deleteSourcemapsAfterUpload check. If a user sets deleteSourcemapsAfterUpload: false alongside filesToDeleteAfterUpload, source maps will still be deleted — contradicting the user's explicit opt-out. The deleteSourcemapsAfterUpload: false setting is expected to act as a master toggle preventing all deletion.

ref getsentry/sentry-javascript#19235 ref getsentry/sentry-javascript#19280 --------- Co-authored-by: Alex Krawiec <alex.krawiec@sentry.io>

chargome · 2026-02-11T11:24:35Z

Adds sourcemaps.filesToDeleteAfterUpload to the Next.js SDK's SentryBuildOptions type, allowing users to specify custom glob patterns for
source map deletion after upload.
When set, this option overrides the default deletion patterns computed by deleteSourcemapsAfterUpload, giving users fine-grained control — including the ability to target server-side source maps if desired.

closes#19235

linear · 2026-02-11T11:24:39Z

JS-1665 `deleteSourcemapsAfterUpload: true` does not delete .next/server/** source maps

github-actions · 2026-02-11T11:38:13Z

Codecov Results 📊

Generated by Codecov Action

cursor · 2026-02-12T09:57:27Z

+
+ if (sentryBuildOptions.debug && userFilesToDeleteAfterUpload !== undefined) {
+ // eslint-disable-next-line no-console
+ console.debug('[@sentry/nextjs] Skipping auto-deletion of source maps as user has provided filesToDeleteAfterUpload:', userFilesToDeleteAfterUpload);


Debug log misleadingly implies deletion is skipped entirely
Low Severity
The debug log message says "Skipping auto-deletion of source maps as user has provided filesToDeleteAfterUpload" which implies deletion is being skipped. In reality, the user's custom filesToDeleteAfterUpload patterns will be used to delete files — it's only the auto-computed patterns that are skipped. A user debugging with debug: true could misinterpret this as "no deletion is happening" when files are indeed being deleted using their custom patterns. The log was specifically requested to help users understand what patterns are being used, but it focuses on what's skipped rather than what's happening.

github-actions · 2026-02-12T10:02:07Z

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	9,005	-	9,512	-5%
GET With Sentry	1,700	19%	1,616	+5%
GET With Sentry (error only)	6,130	68%	6,033	+2%
POST Baseline	1,152	-	1,197	-4%
POST With Sentry	561	49%	590	-5%
POST With Sentry (error only)	1,044	91%	1,051	-1%
MYSQL Baseline	3,269	-	3,335	-2%
MYSQL With Sentry	436	13%	464	-6%
MYSQL With Sentry (error only)	2,624	80%	2,689	-2%

View base workflow run

…ue-does-not-delete-nextserver-source

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

cursor · 2026-02-13T08:15:58Z

+ buildTool,
+ deleteSourcemapsAfterUpload,
+ useRunAfterProductionCompileHook,
+ );


User patterns bypass deleteSourcemapsAfterUpload: false guard
Medium Severity
When filesToDeleteAfterUpload is provided, it completely bypasses the deleteSourcemapsAfterUpload check. If a user sets deleteSourcemapsAfterUpload: false alongside filesToDeleteAfterUpload, source maps will still be deleted — contradicting the user's explicit opt-out. The deleteSourcemapsAfterUpload: false setting is expected to act as a master toggle preventing all deletion.

ref getsentry/sentry-javascript#19235 ref getsentry/sentry-javascript#19280 --------- Co-authored-by: Alex Krawiec <alex.krawiec@sentry.io>

chargome · 2026-02-11T11:24:35Z

Adds sourcemaps.filesToDeleteAfterUpload to the Next.js SDK's SentryBuildOptions type, allowing users to specify custom glob patterns for
source map deletion after upload.
When set, this option overrides the default deletion patterns computed by deleteSourcemapsAfterUpload, giving users fine-grained control — including the ability to target server-side source maps if desired.

closes#19235

linear · 2026-02-11T11:24:39Z

JS-1665 `deleteSourcemapsAfterUpload: true` does not delete .next/server/** source maps

github-actions · 2026-02-11T11:38:13Z

Codecov Results 📊

Generated by Codecov Action

cursor · 2026-02-12T09:57:27Z

+
+ if (sentryBuildOptions.debug && userFilesToDeleteAfterUpload !== undefined) {
+ // eslint-disable-next-line no-console
+ console.debug('[@sentry/nextjs] Skipping auto-deletion of source maps as user has provided filesToDeleteAfterUpload:', userFilesToDeleteAfterUpload);


Debug log misleadingly implies deletion is skipped entirely
Low Severity
The debug log message says "Skipping auto-deletion of source maps as user has provided filesToDeleteAfterUpload" which implies deletion is being skipped. In reality, the user's custom filesToDeleteAfterUpload patterns will be used to delete files — it's only the auto-computed patterns that are skipped. A user debugging with debug: true could misinterpret this as "no deletion is happening" when files are indeed being deleted using their custom patterns. The log was specifically requested to help users understand what patterns are being used, but it focuses on what's skipped rather than what's happening.

github-actions · 2026-02-12T10:02:07Z

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	9,005	-	9,512	-5%
GET With Sentry	1,700	19%	1,616	+5%
GET With Sentry (error only)	6,130	68%	6,033	+2%
POST Baseline	1,152	-	1,197	-4%
POST With Sentry	561	49%	590	-5%
POST With Sentry (error only)	1,044	91%	1,051	-1%
MYSQL Baseline	3,269	-	3,335	-2%
MYSQL With Sentry	436	13%	464	-6%
MYSQL With Sentry (error only)	2,624	80%	2,689	-2%

View base workflow run

…ue-does-not-delete-nextserver-source

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

cursor · 2026-02-13T08:15:58Z

+ buildTool,
+ deleteSourcemapsAfterUpload,
+ useRunAfterProductionCompileHook,
+ );


User patterns bypass deleteSourcemapsAfterUpload: false guard
Medium Severity
When filesToDeleteAfterUpload is provided, it completely bypasses the deleteSourcemapsAfterUpload check. If a user sets deleteSourcemapsAfterUpload: false alongside filesToDeleteAfterUpload, source maps will still be deleted — contradicting the user's explicit opt-out. The deleteSourcemapsAfterUpload: false setting is expected to act as a master toggle preventing all deletion.

ref getsentry/sentry-javascript#19235 ref getsentry/sentry-javascript#19280 --------- Co-authored-by: Alex Krawiec <alex.krawiec@sentry.io>

chargome · 2026-02-11T11:24:35Z

Adds sourcemaps.filesToDeleteAfterUpload to the Next.js SDK's SentryBuildOptions type, allowing users to specify custom glob patterns for
source map deletion after upload.
When set, this option overrides the default deletion patterns computed by deleteSourcemapsAfterUpload, giving users fine-grained control — including the ability to target server-side source maps if desired.

closes#19235

linear · 2026-02-11T11:24:39Z

JS-1665 `deleteSourcemapsAfterUpload: true` does not delete .next/server/** source maps

github-actions · 2026-02-11T11:38:13Z

Codecov Results 📊

Generated by Codecov Action

cursor · 2026-02-12T09:57:27Z

+
+ if (sentryBuildOptions.debug && userFilesToDeleteAfterUpload !== undefined) {
+ // eslint-disable-next-line no-console
+ console.debug('[@sentry/nextjs] Skipping auto-deletion of source maps as user has provided filesToDeleteAfterUpload:', userFilesToDeleteAfterUpload);


Debug log misleadingly implies deletion is skipped entirely
Low Severity
The debug log message says "Skipping auto-deletion of source maps as user has provided filesToDeleteAfterUpload" which implies deletion is being skipped. In reality, the user's custom filesToDeleteAfterUpload patterns will be used to delete files — it's only the auto-computed patterns that are skipped. A user debugging with debug: true could misinterpret this as "no deletion is happening" when files are indeed being deleted using their custom patterns. The log was specifically requested to help users understand what patterns are being used, but it focuses on what's skipped rather than what's happening.

github-actions · 2026-02-12T10:02:07Z

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	9,005	-	9,512	-5%
GET With Sentry	1,700	19%	1,616	+5%
GET With Sentry (error only)	6,130	68%	6,033	+2%
POST Baseline	1,152	-	1,197	-4%
POST With Sentry	561	49%	590	-5%
POST With Sentry (error only)	1,044	91%	1,051	-1%
MYSQL Baseline	3,269	-	3,335	-2%
MYSQL With Sentry	436	13%	464	-6%
MYSQL With Sentry (error only)	2,624	80%	2,689	-2%

View base workflow run

…ue-does-not-delete-nextserver-source

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

cursor · 2026-02-13T08:15:58Z

+ buildTool,
+ deleteSourcemapsAfterUpload,
+ useRunAfterProductionCompileHook,
+ );


User patterns bypass deleteSourcemapsAfterUpload: false guard
Medium Severity
When filesToDeleteAfterUpload is provided, it completely bypasses the deleteSourcemapsAfterUpload check. If a user sets deleteSourcemapsAfterUpload: false alongside filesToDeleteAfterUpload, source maps will still be deleted — contradicting the user's explicit opt-out. The deleteSourcemapsAfterUpload: false setting is expected to act as a master toggle preventing all deletion.

ref getsentry/sentry-javascript#19235 ref getsentry/sentry-javascript#19280 --------- Co-authored-by: Alex Krawiec <alex.krawiec@sentry.io>

chargome · 2026-02-11T11:24:35Z

Adds sourcemaps.filesToDeleteAfterUpload to the Next.js SDK's SentryBuildOptions type, allowing users to specify custom glob patterns for
source map deletion after upload.
When set, this option overrides the default deletion patterns computed by deleteSourcemapsAfterUpload, giving users fine-grained control — including the ability to target server-side source maps if desired.

closes#19235

linear · 2026-02-11T11:24:39Z

JS-1665 `deleteSourcemapsAfterUpload: true` does not delete .next/server/** source maps

github-actions · 2026-02-11T11:38:13Z

Codecov Results 📊

Generated by Codecov Action

cursor · 2026-02-12T09:57:27Z

+
+ if (sentryBuildOptions.debug && userFilesToDeleteAfterUpload !== undefined) {
+ // eslint-disable-next-line no-console
+ console.debug('[@sentry/nextjs] Skipping auto-deletion of source maps as user has provided filesToDeleteAfterUpload:', userFilesToDeleteAfterUpload);


Debug log misleadingly implies deletion is skipped entirely
Low Severity
The debug log message says "Skipping auto-deletion of source maps as user has provided filesToDeleteAfterUpload" which implies deletion is being skipped. In reality, the user's custom filesToDeleteAfterUpload patterns will be used to delete files — it's only the auto-computed patterns that are skipped. A user debugging with debug: true could misinterpret this as "no deletion is happening" when files are indeed being deleted using their custom patterns. The log was specifically requested to help users understand what patterns are being used, but it focuses on what's skipped rather than what's happening.

github-actions · 2026-02-12T10:02:07Z

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	9,005	-	9,512	-5%
GET With Sentry	1,700	19%	1,616	+5%
GET With Sentry (error only)	6,130	68%	6,033	+2%
POST Baseline	1,152	-	1,197	-4%
POST With Sentry	561	49%	590	-5%
POST With Sentry (error only)	1,044	91%	1,051	-1%
MYSQL Baseline	3,269	-	3,335	-2%
MYSQL With Sentry	436	13%	464	-6%
MYSQL With Sentry (error only)	2,624	80%	2,689	-2%

View base workflow run

…ue-does-not-delete-nextserver-source

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

cursor · 2026-02-13T08:15:58Z

+ buildTool,
+ deleteSourcemapsAfterUpload,
+ useRunAfterProductionCompileHook,
+ );


User patterns bypass deleteSourcemapsAfterUpload: false guard
Medium Severity
When filesToDeleteAfterUpload is provided, it completely bypasses the deleteSourcemapsAfterUpload check. If a user sets deleteSourcemapsAfterUpload: false alongside filesToDeleteAfterUpload, source maps will still be deleted — contradicting the user's explicit opt-out. The deleteSourcemapsAfterUpload: false setting is expected to act as a master toggle preventing all deletion.

ref getsentry/sentry-javascript#19235 ref getsentry/sentry-javascript#19280 --------- Co-authored-by: Alex Krawiec <alex.krawiec@sentry.io>

chargome · 2026-02-11T11:24:35Z

Adds sourcemaps.filesToDeleteAfterUpload to the Next.js SDK's SentryBuildOptions type, allowing users to specify custom glob patterns for
source map deletion after upload.
When set, this option overrides the default deletion patterns computed by deleteSourcemapsAfterUpload, giving users fine-grained control — including the ability to target server-side source maps if desired.

closes#19235

linear · 2026-02-11T11:24:39Z

JS-1665 `deleteSourcemapsAfterUpload: true` does not delete .next/server/** source maps

github-actions · 2026-02-11T11:38:13Z

Codecov Results 📊

Generated by Codecov Action

cursor · 2026-02-12T09:57:27Z

+
+ if (sentryBuildOptions.debug && userFilesToDeleteAfterUpload !== undefined) {
+ // eslint-disable-next-line no-console
+ console.debug('[@sentry/nextjs] Skipping auto-deletion of source maps as user has provided filesToDeleteAfterUpload:', userFilesToDeleteAfterUpload);


Debug log misleadingly implies deletion is skipped entirely
Low Severity
The debug log message says "Skipping auto-deletion of source maps as user has provided filesToDeleteAfterUpload" which implies deletion is being skipped. In reality, the user's custom filesToDeleteAfterUpload patterns will be used to delete files — it's only the auto-computed patterns that are skipped. A user debugging with debug: true could misinterpret this as "no deletion is happening" when files are indeed being deleted using their custom patterns. The log was specifically requested to help users understand what patterns are being used, but it focuses on what's skipped rather than what's happening.

github-actions · 2026-02-12T10:02:07Z

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	9,005	-	9,512	-5%
GET With Sentry	1,700	19%	1,616	+5%
GET With Sentry (error only)	6,130	68%	6,033	+2%
POST Baseline	1,152	-	1,197	-4%
POST With Sentry	561	49%	590	-5%
POST With Sentry (error only)	1,044	91%	1,051	-1%
MYSQL Baseline	3,269	-	3,335	-2%
MYSQL With Sentry	436	13%	464	-6%
MYSQL With Sentry (error only)	2,624	80%	2,689	-2%

View base workflow run

…ue-does-not-delete-nextserver-source

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

cursor · 2026-02-13T08:15:58Z

+ buildTool,
+ deleteSourcemapsAfterUpload,
+ useRunAfterProductionCompileHook,
+ );


User patterns bypass deleteSourcemapsAfterUpload: false guard
Medium Severity
When filesToDeleteAfterUpload is provided, it completely bypasses the deleteSourcemapsAfterUpload check. If a user sets deleteSourcemapsAfterUpload: false alongside filesToDeleteAfterUpload, source maps will still be deleted — contradicting the user's explicit opt-out. The deleteSourcemapsAfterUpload: false setting is expected to act as a master toggle preventing all deletion.

ref getsentry/sentry-javascript#19235 ref getsentry/sentry-javascript#19280 --------- Co-authored-by: Alex Krawiec <alex.krawiec@sentry.io>

chargome · 2026-02-11T11:24:35Z

Adds sourcemaps.filesToDeleteAfterUpload to the Next.js SDK's SentryBuildOptions type, allowing users to specify custom glob patterns for
source map deletion after upload.
When set, this option overrides the default deletion patterns computed by deleteSourcemapsAfterUpload, giving users fine-grained control — including the ability to target server-side source maps if desired.

closes#19235

linear · 2026-02-11T11:24:39Z

JS-1665 `deleteSourcemapsAfterUpload: true` does not delete .next/server/** source maps

github-actions · 2026-02-11T11:38:13Z

Codecov Results 📊

Generated by Codecov Action

cursor · 2026-02-12T09:57:27Z

+
+ if (sentryBuildOptions.debug && userFilesToDeleteAfterUpload !== undefined) {
+ // eslint-disable-next-line no-console
+ console.debug('[@sentry/nextjs] Skipping auto-deletion of source maps as user has provided filesToDeleteAfterUpload:', userFilesToDeleteAfterUpload);


Debug log misleadingly implies deletion is skipped entirely
Low Severity
The debug log message says "Skipping auto-deletion of source maps as user has provided filesToDeleteAfterUpload" which implies deletion is being skipped. In reality, the user's custom filesToDeleteAfterUpload patterns will be used to delete files — it's only the auto-computed patterns that are skipped. A user debugging with debug: true could misinterpret this as "no deletion is happening" when files are indeed being deleted using their custom patterns. The log was specifically requested to help users understand what patterns are being used, but it focuses on what's skipped rather than what's happening.

github-actions · 2026-02-12T10:02:07Z

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	9,005	-	9,512	-5%
GET With Sentry	1,700	19%	1,616	+5%
GET With Sentry (error only)	6,130	68%	6,033	+2%
POST Baseline	1,152	-	1,197	-4%
POST With Sentry	561	49%	590	-5%
POST With Sentry (error only)	1,044	91%	1,051	-1%
MYSQL Baseline	3,269	-	3,335	-2%
MYSQL With Sentry	436	13%	464	-6%
MYSQL With Sentry (error only)	2,624	80%	2,689	-2%

View base workflow run

…ue-does-not-delete-nextserver-source

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

cursor · 2026-02-13T08:15:58Z

+ buildTool,
+ deleteSourcemapsAfterUpload,
+ useRunAfterProductionCompileHook,
+ );


User patterns bypass deleteSourcemapsAfterUpload: false guard
Medium Severity
When filesToDeleteAfterUpload is provided, it completely bypasses the deleteSourcemapsAfterUpload check. If a user sets deleteSourcemapsAfterUpload: false alongside filesToDeleteAfterUpload, source maps will still be deleted — contradicting the user's explicit opt-out. The deleteSourcemapsAfterUpload: false setting is expected to act as a master toggle preventing all deletion.

ref getsentry/sentry-javascript#19235 ref getsentry/sentry-javascript#19280 --------- Co-authored-by: Alex Krawiec <alex.krawiec@sentry.io>

add top level option
40fcaa4

chargome self-assigned this Feb 11, 2026

chargome mentioned this pull request Feb 11, 2026
docs(js): Update build api docs for nextjs source maps getsentry/sentry-docs#16353
Merged

format
4be70b2

cursorBot reviewed Feb 11, 2026
View reviewed changes

Comment threadpackages/nextjs/test/config/getBuildPluginOptions.test.ts

chargome requested review from logaretm and s1gr1d February 12, 2026 08:37

chargome mentioned this pull request Feb 12, 2026
deleteSourcemapsAfterUpload: true does not delete .next/server/** source maps #19235
Closed
3 tasks

s1gr1d approved these changes Feb 12, 2026
View reviewed changes

Comment threadpackages/nextjs/src/config/types.ts
Comment threadpackages/nextjs/src/config/getBuildPluginOptions.ts

add debug log
669cef4

cursorBot reviewed Feb 12, 2026
View reviewed changes

.
0c63b57

logaretm approved these changes Feb 12, 2026
View reviewed changes

Merge branch 'develop' into cg/JS-1665/deletesourcemapsafterupload-tr…
957e123
…ue-does-not-delete-nextserver-source

chargome enabled auto-merge (squash) February 13, 2026 08:12

cursorBot reviewed Feb 13, 2026
View reviewed changes

chargome merged commit eb4382c into developFeb 13, 2026
68 checks passed

chargome deleted the cg/JS-1665/deletesourcemapsafterupload-true-does-not-delete-nextserver-source branch February 13, 2026 08:30

logaretm mentioned this pull request Feb 20, 2026
meta(changelog): Update changelog for 10.40.0 #19459
Closed

add top level option
40fcaa4

chargome self-assigned this Feb 11, 2026

chargome mentioned this pull request Feb 11, 2026
docs(js): Update build api docs for nextjs source maps getsentry/sentry-docs#16353
Merged

format
4be70b2

cursorBot reviewed Feb 11, 2026
View reviewed changes

Comment threadpackages/nextjs/test/config/getBuildPluginOptions.test.ts

chargome requested review from logaretm and s1gr1d February 12, 2026 08:37

chargome mentioned this pull request Feb 12, 2026
deleteSourcemapsAfterUpload: true does not delete .next/server/** source maps #19235
Closed
3 tasks

s1gr1d approved these changes Feb 12, 2026
View reviewed changes

Comment threadpackages/nextjs/src/config/types.ts
Comment threadpackages/nextjs/src/config/getBuildPluginOptions.ts

add debug log
669cef4

cursorBot reviewed Feb 12, 2026
View reviewed changes

.
0c63b57

logaretm approved these changes Feb 12, 2026
View reviewed changes

Merge branch 'develop' into cg/JS-1665/deletesourcemapsafterupload-tr…
957e123
…ue-does-not-delete-nextserver-source

chargome enabled auto-merge (squash) February 13, 2026 08:12

cursorBot reviewed Feb 13, 2026
View reviewed changes

chargome merged commit eb4382c into developFeb 13, 2026
68 checks passed

chargome deleted the cg/JS-1665/deletesourcemapsafterupload-true-does-not-delete-nextserver-source branch February 13, 2026 08:30

logaretm mentioned this pull request Feb 20, 2026
meta(changelog): Update changelog for 10.40.0 #19459
Closed

add top level option
40fcaa4

chargome self-assigned this Feb 11, 2026

chargome mentioned this pull request Feb 11, 2026
docs(js): Update build api docs for nextjs source maps getsentry/sentry-docs#16353
Merged

format
4be70b2

cursorBot reviewed Feb 11, 2026
View reviewed changes

Comment threadpackages/nextjs/test/config/getBuildPluginOptions.test.ts

chargome requested review from logaretm and s1gr1d February 12, 2026 08:37

chargome mentioned this pull request Feb 12, 2026
deleteSourcemapsAfterUpload: true does not delete .next/server/** source maps #19235
Closed
3 tasks

s1gr1d approved these changes Feb 12, 2026
View reviewed changes

Comment threadpackages/nextjs/src/config/types.ts
Comment threadpackages/nextjs/src/config/getBuildPluginOptions.ts

add debug log
669cef4

cursorBot reviewed Feb 12, 2026
View reviewed changes

.
0c63b57

logaretm approved these changes Feb 12, 2026
View reviewed changes

Merge branch 'develop' into cg/JS-1665/deletesourcemapsafterupload-tr…
957e123
…ue-does-not-delete-nextserver-source

chargome enabled auto-merge (squash) February 13, 2026 08:12

cursorBot reviewed Feb 13, 2026
View reviewed changes

chargome merged commit eb4382c into developFeb 13, 2026
68 checks passed

chargome deleted the cg/JS-1665/deletesourcemapsafterupload-true-does-not-delete-nextserver-source branch February 13, 2026 08:30

logaretm mentioned this pull request Feb 20, 2026
meta(changelog): Update changelog for 10.40.0 #19459
Closed

add top level option
40fcaa4

chargome self-assigned this Feb 11, 2026

chargome mentioned this pull request Feb 11, 2026
docs(js): Update build api docs for nextjs source maps getsentry/sentry-docs#16353
Merged

format
4be70b2

cursorBot reviewed Feb 11, 2026
View reviewed changes

Comment threadpackages/nextjs/test/config/getBuildPluginOptions.test.ts

chargome requested review from logaretm and s1gr1d February 12, 2026 08:37

chargome mentioned this pull request Feb 12, 2026
deleteSourcemapsAfterUpload: true does not delete .next/server/** source maps #19235
Closed
3 tasks

s1gr1d approved these changes Feb 12, 2026
View reviewed changes

Comment threadpackages/nextjs/src/config/types.ts
Comment threadpackages/nextjs/src/config/getBuildPluginOptions.ts

add debug log
669cef4

cursorBot reviewed Feb 12, 2026
View reviewed changes

.
0c63b57

logaretm approved these changes Feb 12, 2026
View reviewed changes

Merge branch 'develop' into cg/JS-1665/deletesourcemapsafterupload-tr…
957e123
…ue-does-not-delete-nextserver-source

chargome enabled auto-merge (squash) February 13, 2026 08:12

cursorBot reviewed Feb 13, 2026
View reviewed changes

chargome merged commit eb4382c into developFeb 13, 2026
68 checks passed

chargome deleted the cg/JS-1665/deletesourcemapsafterupload-true-does-not-delete-nextserver-source branch February 13, 2026 08:30

logaretm mentioned this pull request Feb 20, 2026
meta(changelog): Update changelog for 10.40.0 #19459
Closed

add top level option
40fcaa4

chargome self-assigned this Feb 11, 2026

chargome mentioned this pull request Feb 11, 2026
docs(js): Update build api docs for nextjs source maps getsentry/sentry-docs#16353
Merged

format
4be70b2

cursorBot reviewed Feb 11, 2026
View reviewed changes

Comment threadpackages/nextjs/test/config/getBuildPluginOptions.test.ts

chargome requested review from logaretm and s1gr1d February 12, 2026 08:37

chargome mentioned this pull request Feb 12, 2026
deleteSourcemapsAfterUpload: true does not delete .next/server/** source maps #19235
Closed
3 tasks

s1gr1d approved these changes Feb 12, 2026
View reviewed changes

Comment threadpackages/nextjs/src/config/types.ts
Comment threadpackages/nextjs/src/config/getBuildPluginOptions.ts

add debug log
669cef4

cursorBot reviewed Feb 12, 2026
View reviewed changes

.
0c63b57

logaretm approved these changes Feb 12, 2026
View reviewed changes

Merge branch 'develop' into cg/JS-1665/deletesourcemapsafterupload-tr…
957e123
…ue-does-not-delete-nextserver-source

chargome enabled auto-merge (squash) February 13, 2026 08:12

cursorBot reviewed Feb 13, 2026
View reviewed changes

chargome merged commit eb4382c into developFeb 13, 2026
68 checks passed

chargome deleted the cg/JS-1665/deletesourcemapsafterupload-true-does-not-delete-nextserver-source branch February 13, 2026 08:30

logaretm mentioned this pull request Feb 20, 2026
meta(changelog): Update changelog for 10.40.0 #19459
Closed

add top level option
40fcaa4

chargome self-assigned this Feb 11, 2026

chargome mentioned this pull request Feb 11, 2026
docs(js): Update build api docs for nextjs source maps getsentry/sentry-docs#16353
Merged

format
4be70b2

cursorBot reviewed Feb 11, 2026
View reviewed changes

Comment threadpackages/nextjs/test/config/getBuildPluginOptions.test.ts

chargome requested review from logaretm and s1gr1d February 12, 2026 08:37

chargome mentioned this pull request Feb 12, 2026
deleteSourcemapsAfterUpload: true does not delete .next/server/** source maps #19235
Closed
3 tasks

s1gr1d approved these changes Feb 12, 2026
View reviewed changes

Comment threadpackages/nextjs/src/config/types.ts
Comment threadpackages/nextjs/src/config/getBuildPluginOptions.ts

add debug log
669cef4

cursorBot reviewed Feb 12, 2026
View reviewed changes

.
0c63b57

logaretm approved these changes Feb 12, 2026
View reviewed changes

Merge branch 'develop' into cg/JS-1665/deletesourcemapsafterupload-tr…
957e123
…ue-does-not-delete-nextserver-source

chargome enabled auto-merge (squash) February 13, 2026 08:12

cursorBot reviewed Feb 13, 2026
View reviewed changes

chargome merged commit eb4382c into developFeb 13, 2026
68 checks passed

chargome deleted the cg/JS-1665/deletesourcemapsafterupload-true-does-not-delete-nextserver-source branch February 13, 2026 08:30

logaretm mentioned this pull request Feb 20, 2026
meta(changelog): Update changelog for 10.40.0 #19459
Closed

add top level option
40fcaa4

chargome self-assigned this Feb 11, 2026

chargome mentioned this pull request Feb 11, 2026
docs(js): Update build api docs for nextjs source maps getsentry/sentry-docs#16353
Merged

format
4be70b2

cursorBot reviewed Feb 11, 2026
View reviewed changes

Comment threadpackages/nextjs/test/config/getBuildPluginOptions.test.ts

chargome requested review from logaretm and s1gr1d February 12, 2026 08:37

chargome mentioned this pull request Feb 12, 2026
deleteSourcemapsAfterUpload: true does not delete .next/server/** source maps #19235
Closed
3 tasks

s1gr1d approved these changes Feb 12, 2026
View reviewed changes

Comment threadpackages/nextjs/src/config/types.ts
Comment threadpackages/nextjs/src/config/getBuildPluginOptions.ts

add debug log
669cef4

cursorBot reviewed Feb 12, 2026
View reviewed changes

.
0c63b57

logaretm approved these changes Feb 12, 2026
View reviewed changes

Merge branch 'develop' into cg/JS-1665/deletesourcemapsafterupload-tr…
957e123
…ue-does-not-delete-nextserver-source

chargome enabled auto-merge (squash) February 13, 2026 08:12

cursorBot reviewed Feb 13, 2026
View reviewed changes

chargome merged commit eb4382c into developFeb 13, 2026
68 checks passed

chargome deleted the cg/JS-1665/deletesourcemapsafterupload-true-does-not-delete-nextserver-source branch February 13, 2026 08:30

logaretm mentioned this pull request Feb 20, 2026
meta(changelog): Update changelog for 10.40.0 #19459
Closed

add top level option
40fcaa4

chargome self-assigned this Feb 11, 2026

chargome mentioned this pull request Feb 11, 2026
docs(js): Update build api docs for nextjs source maps getsentry/sentry-docs#16353
Merged

format
4be70b2

cursorBot reviewed Feb 11, 2026
View reviewed changes

Comment threadpackages/nextjs/test/config/getBuildPluginOptions.test.ts

chargome requested review from logaretm and s1gr1d February 12, 2026 08:37

chargome mentioned this pull request Feb 12, 2026
deleteSourcemapsAfterUpload: true does not delete .next/server/** source maps #19235
Closed
3 tasks

s1gr1d approved these changes Feb 12, 2026
View reviewed changes

Comment threadpackages/nextjs/src/config/types.ts
Comment threadpackages/nextjs/src/config/getBuildPluginOptions.ts

add debug log
669cef4

cursorBot reviewed Feb 12, 2026
View reviewed changes

.
0c63b57

logaretm approved these changes Feb 12, 2026
View reviewed changes

Merge branch 'develop' into cg/JS-1665/deletesourcemapsafterupload-tr…
957e123
…ue-does-not-delete-nextserver-source

chargome enabled auto-merge (squash) February 13, 2026 08:12

cursorBot reviewed Feb 13, 2026
View reviewed changes

chargome merged commit eb4382c into developFeb 13, 2026
68 checks passed

chargome deleted the cg/JS-1665/deletesourcemapsafterupload-true-does-not-delete-nextserver-source branch February 13, 2026 08:30

logaretm mentioned this pull request Feb 20, 2026
meta(changelog): Update changelog for 10.40.0 #19459
Closed

Uh oh!

Uh oh!

Conversation

chargome commented Feb 11, 2026

Uh oh!

linearBot commented Feb 11, 2026

Uh oh!

Uh oh!

github-actionsBot commented Feb 11, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Results 📊

Uh oh!

Uh oh!

Uh oh!

cursorBotFeb 12, 2026

Choose a reason for hiding this comment

Debug log misleadingly implies deletion is skipped entirely

Uh oh!

github-actionsBot commented Feb 12, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

node-overhead report 🧳

Uh oh!

cursorBot left a comment

Choose a reason for hiding this comment

Uh oh!

cursorBotFeb 13, 2026

Choose a reason for hiding this comment

User patterns bypass deleteSourcemapsAfterUpload: false guard

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Uh oh!

Conversation

chargome commented Feb 11, 2026

Uh oh!

linearBot commented Feb 11, 2026

Uh oh!

Uh oh!

github-actionsBot commented Feb 11, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Results 📊

Uh oh!

Uh oh!

Uh oh!

cursorBotFeb 12, 2026

Choose a reason for hiding this comment

Debug log misleadingly implies deletion is skipped entirely

Uh oh!

github-actionsBot commented Feb 12, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

node-overhead report 🧳

Uh oh!

cursorBot left a comment

Choose a reason for hiding this comment

Uh oh!

cursorBotFeb 13, 2026

Choose a reason for hiding this comment

User patterns bypass deleteSourcemapsAfterUpload: false guard

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Uh oh!

Conversation

chargome commented Feb 11, 2026

github-actionsBot commented Feb 11, 2026•
edited
Loading

github-actionsBot commented Feb 12, 2026•
edited
Loading

User patterns bypass `deleteSourcemapsAfterUpload: false` guard

github-actionsBot commented Feb 11, 2026•
edited
Loading

github-actionsBot commented Feb 12, 2026•
edited
Loading

User patterns bypass `deleteSourcemapsAfterUpload: false` guard

github-actionsBot commented Feb 11, 2026•
edited
Loading

github-actionsBot commented Feb 12, 2026•
edited
Loading

User patterns bypass `deleteSourcemapsAfterUpload: false` guard

github-actionsBot commented Feb 11, 2026•
edited
Loading