fix(nextjs): Set parameterized transaction name for non-transaction events by chargome · Pull Request #19316 · getsentry/sentry-javascript

chargome · 2026-02-13T09:48:21Z

Calls to Sentry.captureException() inside a Next.js App Router route handler, lead to unparameterized transaction names

This happens because non-transaction events read their transaction from the isolation scope's transactionName, which is set to the raw URL by httpServerIntegration. On turbopack, the webpack wrapping loader doesn't run, so wrapRouteHandlerWithSentry (which sets the parameterized name on the current scope) is never called.
The fix updates handleOnSpanStart to also set the parameterized route on the isolation scope when hoisting the next.route attribute to the root span. This ensures manually captured events get the parameterized route regardless of bundler.
Adds E2E tests for route handler errors (throw), captureException, and captureMessage with parameterized routes in the nextjs-16 test app.

closes#19312

github-actions · 2026-02-13T09:57:22Z

Codecov Results 📊

Generated by Codecov Action

github-actions · 2026-02-13T09:57:22Z

Codecov Results 📊

✅ Patch coverage is 100.00%. Project has 14 uncovered lines.
✅ Project coverage is 83.13%. Comparing base (base) to head (head).

Files with missing lines (2)

File	Patch %	Lines
`mute.js`	79.10%	⚠️ 14 Missing and 7 partials
`etoa.js`	100.00%	⚠️ 1 partials

Coverage diff

@@ Coverage Diff @@## main #PR +/-##
==========================================
+ Coverage 60.31% 83.13% +22.82%
==========================================
Files 756 2 -754
Lines 41847 83 -41764
Branches 7996 57 -7939
==========================================
+ Hits 25248 69 -25179- Misses 16599 14 -16585- Partials 82 8 -74

Generated by Codecov Action

andreiborza

LGTM

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-13T12:08:04Z

+ handled: false,
+ type: 'auto.function.nextjs.on_request_error',
+ });
+ }


Test uses conditional instead of separate test cases
Low Severity
The test at line 69 uses if (process.env.TEST_ENV === 'development') to conditionally run assertions for nextjs context and mechanism. Per the project review rules, conditionals within a single test case are discouraged — the recommendation is to split the test into separate test cases for each environment path. This ensures both paths are always visible in test results and avoids silently skipping assertions.
^{Triggered by project rule: PR Review Guidelines for Cursor Bot}

chargome · 2026-02-13T09:48:21Z

Calls to Sentry.captureException() inside a Next.js App Router route handler, lead to unparameterized transaction names

This happens because non-transaction events read their transaction from the isolation scope's transactionName, which is set to the raw URL by httpServerIntegration. On turbopack, the webpack wrapping loader doesn't run, so wrapRouteHandlerWithSentry (which sets the parameterized name on the current scope) is never called.
The fix updates handleOnSpanStart to also set the parameterized route on the isolation scope when hoisting the next.route attribute to the root span. This ensures manually captured events get the parameterized route regardless of bundler.
Adds E2E tests for route handler errors (throw), captureException, and captureMessage with parameterized routes in the nextjs-16 test app.

closes#19312

github-actions · 2026-02-13T09:57:22Z

Codecov Results 📊

Generated by Codecov Action

github-actions · 2026-02-13T09:57:22Z

Codecov Results 📊

✅ Patch coverage is 100.00%. Project has 14 uncovered lines.
✅ Project coverage is 83.13%. Comparing base (base) to head (head).

Files with missing lines (2)

File	Patch %	Lines
`mute.js`	79.10%	⚠️ 14 Missing and 7 partials
`etoa.js`	100.00%	⚠️ 1 partials

Coverage diff

@@ Coverage Diff @@## main #PR +/-##
==========================================
+ Coverage 60.31% 83.13% +22.82%
==========================================
Files 756 2 -754
Lines 41847 83 -41764
Branches 7996 57 -7939
==========================================
+ Hits 25248 69 -25179- Misses 16599 14 -16585- Partials 82 8 -74

Generated by Codecov Action

andreiborza

LGTM

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-13T12:08:04Z

+ handled: false,
+ type: 'auto.function.nextjs.on_request_error',
+ });
+ }


Test uses conditional instead of separate test cases
Low Severity
The test at line 69 uses if (process.env.TEST_ENV === 'development') to conditionally run assertions for nextjs context and mechanism. Per the project review rules, conditionals within a single test case are discouraged — the recommendation is to split the test into separate test cases for each environment path. This ensures both paths are always visible in test results and avoids silently skipping assertions.
^{Triggered by project rule: PR Review Guidelines for Cursor Bot}

chargome · 2026-02-13T09:48:21Z

Calls to Sentry.captureException() inside a Next.js App Router route handler, lead to unparameterized transaction names

This happens because non-transaction events read their transaction from the isolation scope's transactionName, which is set to the raw URL by httpServerIntegration. On turbopack, the webpack wrapping loader doesn't run, so wrapRouteHandlerWithSentry (which sets the parameterized name on the current scope) is never called.
The fix updates handleOnSpanStart to also set the parameterized route on the isolation scope when hoisting the next.route attribute to the root span. This ensures manually captured events get the parameterized route regardless of bundler.
Adds E2E tests for route handler errors (throw), captureException, and captureMessage with parameterized routes in the nextjs-16 test app.

closes#19312

github-actions · 2026-02-13T09:57:22Z

Codecov Results 📊

Generated by Codecov Action

github-actions · 2026-02-13T09:57:22Z

Codecov Results 📊

✅ Patch coverage is 100.00%. Project has 14 uncovered lines.
✅ Project coverage is 83.13%. Comparing base (base) to head (head).

Files with missing lines (2)

File	Patch %	Lines
`mute.js`	79.10%	⚠️ 14 Missing and 7 partials
`etoa.js`	100.00%	⚠️ 1 partials

Coverage diff

@@ Coverage Diff @@## main #PR +/-##
==========================================
+ Coverage 60.31% 83.13% +22.82%
==========================================
Files 756 2 -754
Lines 41847 83 -41764
Branches 7996 57 -7939
==========================================
+ Hits 25248 69 -25179- Misses 16599 14 -16585- Partials 82 8 -74

Generated by Codecov Action

andreiborza

LGTM

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-13T12:08:04Z

+ handled: false,
+ type: 'auto.function.nextjs.on_request_error',
+ });
+ }


Test uses conditional instead of separate test cases
Low Severity
The test at line 69 uses if (process.env.TEST_ENV === 'development') to conditionally run assertions for nextjs context and mechanism. Per the project review rules, conditionals within a single test case are discouraged — the recommendation is to split the test into separate test cases for each environment path. This ensures both paths are always visible in test results and avoids silently skipping assertions.
^{Triggered by project rule: PR Review Guidelines for Cursor Bot}

chargome · 2026-02-13T09:48:21Z

Calls to Sentry.captureException() inside a Next.js App Router route handler, lead to unparameterized transaction names

This happens because non-transaction events read their transaction from the isolation scope's transactionName, which is set to the raw URL by httpServerIntegration. On turbopack, the webpack wrapping loader doesn't run, so wrapRouteHandlerWithSentry (which sets the parameterized name on the current scope) is never called.
The fix updates handleOnSpanStart to also set the parameterized route on the isolation scope when hoisting the next.route attribute to the root span. This ensures manually captured events get the parameterized route regardless of bundler.
Adds E2E tests for route handler errors (throw), captureException, and captureMessage with parameterized routes in the nextjs-16 test app.

closes#19312

github-actions · 2026-02-13T09:57:22Z

Codecov Results 📊

Generated by Codecov Action

github-actions · 2026-02-13T09:57:22Z

Codecov Results 📊

✅ Patch coverage is 100.00%. Project has 14 uncovered lines.
✅ Project coverage is 83.13%. Comparing base (base) to head (head).

Files with missing lines (2)

File	Patch %	Lines
`mute.js`	79.10%	⚠️ 14 Missing and 7 partials
`etoa.js`	100.00%	⚠️ 1 partials

Coverage diff

@@ Coverage Diff @@## main #PR +/-##
==========================================
+ Coverage 60.31% 83.13% +22.82%
==========================================
Files 756 2 -754
Lines 41847 83 -41764
Branches 7996 57 -7939
==========================================
+ Hits 25248 69 -25179- Misses 16599 14 -16585- Partials 82 8 -74

Generated by Codecov Action

andreiborza

LGTM

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-13T12:08:04Z

+ handled: false,
+ type: 'auto.function.nextjs.on_request_error',
+ });
+ }


Test uses conditional instead of separate test cases
Low Severity
The test at line 69 uses if (process.env.TEST_ENV === 'development') to conditionally run assertions for nextjs context and mechanism. Per the project review rules, conditionals within a single test case are discouraged — the recommendation is to split the test into separate test cases for each environment path. This ensures both paths are always visible in test results and avoids silently skipping assertions.
^{Triggered by project rule: PR Review Guidelines for Cursor Bot}

chargome · 2026-02-13T09:48:21Z

Calls to Sentry.captureException() inside a Next.js App Router route handler, lead to unparameterized transaction names

This happens because non-transaction events read their transaction from the isolation scope's transactionName, which is set to the raw URL by httpServerIntegration. On turbopack, the webpack wrapping loader doesn't run, so wrapRouteHandlerWithSentry (which sets the parameterized name on the current scope) is never called.
The fix updates handleOnSpanStart to also set the parameterized route on the isolation scope when hoisting the next.route attribute to the root span. This ensures manually captured events get the parameterized route regardless of bundler.
Adds E2E tests for route handler errors (throw), captureException, and captureMessage with parameterized routes in the nextjs-16 test app.

closes#19312

github-actions · 2026-02-13T09:57:22Z

Codecov Results 📊

Generated by Codecov Action

github-actions · 2026-02-13T09:57:22Z

Codecov Results 📊

✅ Patch coverage is 100.00%. Project has 14 uncovered lines.
✅ Project coverage is 83.13%. Comparing base (base) to head (head).

Files with missing lines (2)

File	Patch %	Lines
`mute.js`	79.10%	⚠️ 14 Missing and 7 partials
`etoa.js`	100.00%	⚠️ 1 partials

Coverage diff

@@ Coverage Diff @@## main #PR +/-##
==========================================
+ Coverage 60.31% 83.13% +22.82%
==========================================
Files 756 2 -754
Lines 41847 83 -41764
Branches 7996 57 -7939
==========================================
+ Hits 25248 69 -25179- Misses 16599 14 -16585- Partials 82 8 -74

Generated by Codecov Action

andreiborza

LGTM

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-13T12:08:04Z

+ handled: false,
+ type: 'auto.function.nextjs.on_request_error',
+ });
+ }


Test uses conditional instead of separate test cases
Low Severity
The test at line 69 uses if (process.env.TEST_ENV === 'development') to conditionally run assertions for nextjs context and mechanism. Per the project review rules, conditionals within a single test case are discouraged — the recommendation is to split the test into separate test cases for each environment path. This ensures both paths are always visible in test results and avoids silently skipping assertions.
^{Triggered by project rule: PR Review Guidelines for Cursor Bot}

chargome · 2026-02-13T09:48:21Z

Calls to Sentry.captureException() inside a Next.js App Router route handler, lead to unparameterized transaction names

This happens because non-transaction events read their transaction from the isolation scope's transactionName, which is set to the raw URL by httpServerIntegration. On turbopack, the webpack wrapping loader doesn't run, so wrapRouteHandlerWithSentry (which sets the parameterized name on the current scope) is never called.
The fix updates handleOnSpanStart to also set the parameterized route on the isolation scope when hoisting the next.route attribute to the root span. This ensures manually captured events get the parameterized route regardless of bundler.
Adds E2E tests for route handler errors (throw), captureException, and captureMessage with parameterized routes in the nextjs-16 test app.

closes#19312

github-actions · 2026-02-13T09:57:22Z

Codecov Results 📊

Generated by Codecov Action

github-actions · 2026-02-13T09:57:22Z

Codecov Results 📊

✅ Patch coverage is 100.00%. Project has 14 uncovered lines.
✅ Project coverage is 83.13%. Comparing base (base) to head (head).

Files with missing lines (2)

File	Patch %	Lines
`mute.js`	79.10%	⚠️ 14 Missing and 7 partials
`etoa.js`	100.00%	⚠️ 1 partials

Coverage diff

@@ Coverage Diff @@## main #PR +/-##
==========================================
+ Coverage 60.31% 83.13% +22.82%
==========================================
Files 756 2 -754
Lines 41847 83 -41764
Branches 7996 57 -7939
==========================================
+ Hits 25248 69 -25179- Misses 16599 14 -16585- Partials 82 8 -74

Generated by Codecov Action

andreiborza

LGTM

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-13T12:08:04Z

+ handled: false,
+ type: 'auto.function.nextjs.on_request_error',
+ });
+ }


Test uses conditional instead of separate test cases
Low Severity
The test at line 69 uses if (process.env.TEST_ENV === 'development') to conditionally run assertions for nextjs context and mechanism. Per the project review rules, conditionals within a single test case are discouraged — the recommendation is to split the test into separate test cases for each environment path. This ensures both paths are always visible in test results and avoids silently skipping assertions.
^{Triggered by project rule: PR Review Guidelines for Cursor Bot}

chargome · 2026-02-13T09:48:21Z

Calls to Sentry.captureException() inside a Next.js App Router route handler, lead to unparameterized transaction names

This happens because non-transaction events read their transaction from the isolation scope's transactionName, which is set to the raw URL by httpServerIntegration. On turbopack, the webpack wrapping loader doesn't run, so wrapRouteHandlerWithSentry (which sets the parameterized name on the current scope) is never called.
The fix updates handleOnSpanStart to also set the parameterized route on the isolation scope when hoisting the next.route attribute to the root span. This ensures manually captured events get the parameterized route regardless of bundler.
Adds E2E tests for route handler errors (throw), captureException, and captureMessage with parameterized routes in the nextjs-16 test app.

closes#19312

github-actions · 2026-02-13T09:57:22Z

Codecov Results 📊

Generated by Codecov Action

github-actions · 2026-02-13T09:57:22Z

Codecov Results 📊

✅ Patch coverage is 100.00%. Project has 14 uncovered lines.
✅ Project coverage is 83.13%. Comparing base (base) to head (head).

Files with missing lines (2)

File	Patch %	Lines
`mute.js`	79.10%	⚠️ 14 Missing and 7 partials
`etoa.js`	100.00%	⚠️ 1 partials

Coverage diff

@@ Coverage Diff @@## main #PR +/-##
==========================================
+ Coverage 60.31% 83.13% +22.82%
==========================================
Files 756 2 -754
Lines 41847 83 -41764
Branches 7996 57 -7939
==========================================
+ Hits 25248 69 -25179- Misses 16599 14 -16585- Partials 82 8 -74

Generated by Codecov Action

andreiborza

LGTM

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-13T12:08:04Z

+ handled: false,
+ type: 'auto.function.nextjs.on_request_error',
+ });
+ }


Test uses conditional instead of separate test cases
Low Severity
The test at line 69 uses if (process.env.TEST_ENV === 'development') to conditionally run assertions for nextjs context and mechanism. Per the project review rules, conditionals within a single test case are discouraged — the recommendation is to split the test into separate test cases for each environment path. This ensures both paths are always visible in test results and avoids silently skipping assertions.
^{Triggered by project rule: PR Review Guidelines for Cursor Bot}

chargome · 2026-02-13T09:48:21Z

Calls to Sentry.captureException() inside a Next.js App Router route handler, lead to unparameterized transaction names

This happens because non-transaction events read their transaction from the isolation scope's transactionName, which is set to the raw URL by httpServerIntegration. On turbopack, the webpack wrapping loader doesn't run, so wrapRouteHandlerWithSentry (which sets the parameterized name on the current scope) is never called.
The fix updates handleOnSpanStart to also set the parameterized route on the isolation scope when hoisting the next.route attribute to the root span. This ensures manually captured events get the parameterized route regardless of bundler.
Adds E2E tests for route handler errors (throw), captureException, and captureMessage with parameterized routes in the nextjs-16 test app.

closes#19312

github-actions · 2026-02-13T09:57:22Z

Codecov Results 📊

Generated by Codecov Action

github-actions · 2026-02-13T09:57:22Z

Codecov Results 📊

✅ Patch coverage is 100.00%. Project has 14 uncovered lines.
✅ Project coverage is 83.13%. Comparing base (base) to head (head).

Files with missing lines (2)

File	Patch %	Lines
`mute.js`	79.10%	⚠️ 14 Missing and 7 partials
`etoa.js`	100.00%	⚠️ 1 partials

Coverage diff

@@ Coverage Diff @@## main #PR +/-##
==========================================
+ Coverage 60.31% 83.13% +22.82%
==========================================
Files 756 2 -754
Lines 41847 83 -41764
Branches 7996 57 -7939
==========================================
+ Hits 25248 69 -25179- Misses 16599 14 -16585- Partials 82 8 -74

Generated by Codecov Action

andreiborza

LGTM

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-13T12:08:04Z

+ handled: false,
+ type: 'auto.function.nextjs.on_request_error',
+ });
+ }


Test uses conditional instead of separate test cases
Low Severity
The test at line 69 uses if (process.env.TEST_ENV === 'development') to conditionally run assertions for nextjs context and mechanism. Per the project review rules, conditionals within a single test case are discouraged — the recommendation is to split the test into separate test cases for each environment path. This ensures both paths are always visible in test results and avoids silently skipping assertions.
^{Triggered by project rule: PR Review Guidelines for Cursor Bot}

add tests
cd9cb83

chargome self-assigned this Feb 13, 2026

chargome added 2 commits February 13, 2026 11:24

add capture tests
aa10473

set tx name in onspanstart
f08eb02

chargome changed the title ~~test(nextjs): Add parameterization tests for errors in route handlers~~fix(nextjs): Set parameterized transaction name for non-transaction eventsFeb 13, 2026

chargome marked this pull request as ready for review February 13, 2026 10:29

chargome requested a review from logaretm February 13, 2026 10:29

sentryBot reviewed Feb 13, 2026
View reviewed changes

Comment threaddev-packages/e2e-tests/test-applications/nextjs-16/tests/route-handler.test.ts Outdated

andreiborza approved these changes Feb 13, 2026
View reviewed changes

chargome added 2 commits February 13, 2026 11:46

unify error tx naming
88eeda3

.
b66a1b9

sentryBot reviewed Feb 13, 2026
View reviewed changes

Comment threadpackages/nextjs/src/server/handleOnSpanStart.ts

wat
c258284

cursorBot reviewed Feb 13, 2026
View reviewed changes

chargome merged commit 337f538 into developFeb 13, 2026
68 checks passed

chargome deleted the cg/turbo-tx-parameterization branch February 13, 2026 12:54

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

github-actionsBot mentioned this pull request Feb 24, 2026
Context transaction name is not parametrized anymore #19312
Closed

add tests
cd9cb83

chargome self-assigned this Feb 13, 2026

chargome added 2 commits February 13, 2026 11:24

add capture tests
aa10473

set tx name in onspanstart
f08eb02

chargome changed the title ~~test(nextjs): Add parameterization tests for errors in route handlers~~fix(nextjs): Set parameterized transaction name for non-transaction eventsFeb 13, 2026

chargome marked this pull request as ready for review February 13, 2026 10:29

chargome requested a review from logaretm February 13, 2026 10:29

sentryBot reviewed Feb 13, 2026
View reviewed changes

Comment threaddev-packages/e2e-tests/test-applications/nextjs-16/tests/route-handler.test.ts Outdated

andreiborza approved these changes Feb 13, 2026
View reviewed changes

chargome added 2 commits February 13, 2026 11:46

unify error tx naming
88eeda3

.
b66a1b9

sentryBot reviewed Feb 13, 2026
View reviewed changes

Comment threadpackages/nextjs/src/server/handleOnSpanStart.ts

wat
c258284

cursorBot reviewed Feb 13, 2026
View reviewed changes

chargome merged commit 337f538 into developFeb 13, 2026
68 checks passed

chargome deleted the cg/turbo-tx-parameterization branch February 13, 2026 12:54

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

github-actionsBot mentioned this pull request Feb 24, 2026
Context transaction name is not parametrized anymore #19312
Closed

add tests
cd9cb83

chargome self-assigned this Feb 13, 2026

chargome added 2 commits February 13, 2026 11:24

add capture tests
aa10473

set tx name in onspanstart
f08eb02

chargome changed the title ~~test(nextjs): Add parameterization tests for errors in route handlers~~fix(nextjs): Set parameterized transaction name for non-transaction eventsFeb 13, 2026

chargome marked this pull request as ready for review February 13, 2026 10:29

chargome requested a review from logaretm February 13, 2026 10:29

sentryBot reviewed Feb 13, 2026
View reviewed changes

Comment threaddev-packages/e2e-tests/test-applications/nextjs-16/tests/route-handler.test.ts Outdated

andreiborza approved these changes Feb 13, 2026
View reviewed changes

chargome added 2 commits February 13, 2026 11:46

unify error tx naming
88eeda3

.
b66a1b9

sentryBot reviewed Feb 13, 2026
View reviewed changes

Comment threadpackages/nextjs/src/server/handleOnSpanStart.ts

wat
c258284

cursorBot reviewed Feb 13, 2026
View reviewed changes

chargome merged commit 337f538 into developFeb 13, 2026
68 checks passed

chargome deleted the cg/turbo-tx-parameterization branch February 13, 2026 12:54

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

github-actionsBot mentioned this pull request Feb 24, 2026
Context transaction name is not parametrized anymore #19312
Closed

add tests
cd9cb83

chargome self-assigned this Feb 13, 2026

chargome added 2 commits February 13, 2026 11:24

add capture tests
aa10473

set tx name in onspanstart
f08eb02

chargome changed the title ~~test(nextjs): Add parameterization tests for errors in route handlers~~fix(nextjs): Set parameterized transaction name for non-transaction eventsFeb 13, 2026

chargome marked this pull request as ready for review February 13, 2026 10:29

chargome requested a review from logaretm February 13, 2026 10:29

sentryBot reviewed Feb 13, 2026
View reviewed changes

Comment threaddev-packages/e2e-tests/test-applications/nextjs-16/tests/route-handler.test.ts Outdated

andreiborza approved these changes Feb 13, 2026
View reviewed changes

chargome added 2 commits February 13, 2026 11:46

unify error tx naming
88eeda3

.
b66a1b9

sentryBot reviewed Feb 13, 2026
View reviewed changes

Comment threadpackages/nextjs/src/server/handleOnSpanStart.ts

wat
c258284

cursorBot reviewed Feb 13, 2026
View reviewed changes

chargome merged commit 337f538 into developFeb 13, 2026
68 checks passed

chargome deleted the cg/turbo-tx-parameterization branch February 13, 2026 12:54

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

github-actionsBot mentioned this pull request Feb 24, 2026
Context transaction name is not parametrized anymore #19312
Closed

add tests
cd9cb83

chargome self-assigned this Feb 13, 2026

chargome added 2 commits February 13, 2026 11:24

add capture tests
aa10473

set tx name in onspanstart
f08eb02

chargome changed the title ~~test(nextjs): Add parameterization tests for errors in route handlers~~fix(nextjs): Set parameterized transaction name for non-transaction eventsFeb 13, 2026

chargome marked this pull request as ready for review February 13, 2026 10:29

chargome requested a review from logaretm February 13, 2026 10:29

sentryBot reviewed Feb 13, 2026
View reviewed changes

Comment threaddev-packages/e2e-tests/test-applications/nextjs-16/tests/route-handler.test.ts Outdated

andreiborza approved these changes Feb 13, 2026
View reviewed changes

chargome added 2 commits February 13, 2026 11:46

unify error tx naming
88eeda3

.
b66a1b9

sentryBot reviewed Feb 13, 2026
View reviewed changes

Comment threadpackages/nextjs/src/server/handleOnSpanStart.ts

wat
c258284

cursorBot reviewed Feb 13, 2026
View reviewed changes

chargome merged commit 337f538 into developFeb 13, 2026
68 checks passed

chargome deleted the cg/turbo-tx-parameterization branch February 13, 2026 12:54

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

github-actionsBot mentioned this pull request Feb 24, 2026
Context transaction name is not parametrized anymore #19312
Closed

add tests
cd9cb83

chargome self-assigned this Feb 13, 2026

chargome added 2 commits February 13, 2026 11:24

add capture tests
aa10473

set tx name in onspanstart
f08eb02

chargome changed the title ~~test(nextjs): Add parameterization tests for errors in route handlers~~fix(nextjs): Set parameterized transaction name for non-transaction eventsFeb 13, 2026

chargome marked this pull request as ready for review February 13, 2026 10:29

chargome requested a review from logaretm February 13, 2026 10:29

sentryBot reviewed Feb 13, 2026
View reviewed changes

Comment threaddev-packages/e2e-tests/test-applications/nextjs-16/tests/route-handler.test.ts Outdated

andreiborza approved these changes Feb 13, 2026
View reviewed changes

chargome added 2 commits February 13, 2026 11:46

unify error tx naming
88eeda3

.
b66a1b9

sentryBot reviewed Feb 13, 2026
View reviewed changes

Comment threadpackages/nextjs/src/server/handleOnSpanStart.ts

wat
c258284

cursorBot reviewed Feb 13, 2026
View reviewed changes

chargome merged commit 337f538 into developFeb 13, 2026
68 checks passed

chargome deleted the cg/turbo-tx-parameterization branch February 13, 2026 12:54

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

github-actionsBot mentioned this pull request Feb 24, 2026
Context transaction name is not parametrized anymore #19312
Closed

add tests
cd9cb83

chargome self-assigned this Feb 13, 2026

chargome added 2 commits February 13, 2026 11:24

add capture tests
aa10473

set tx name in onspanstart
f08eb02

chargome changed the title ~~test(nextjs): Add parameterization tests for errors in route handlers~~fix(nextjs): Set parameterized transaction name for non-transaction eventsFeb 13, 2026

chargome marked this pull request as ready for review February 13, 2026 10:29

chargome requested a review from logaretm February 13, 2026 10:29

sentryBot reviewed Feb 13, 2026
View reviewed changes

Comment threaddev-packages/e2e-tests/test-applications/nextjs-16/tests/route-handler.test.ts Outdated

andreiborza approved these changes Feb 13, 2026
View reviewed changes

chargome added 2 commits February 13, 2026 11:46

unify error tx naming
88eeda3

.
b66a1b9

sentryBot reviewed Feb 13, 2026
View reviewed changes

Comment threadpackages/nextjs/src/server/handleOnSpanStart.ts

wat
c258284

cursorBot reviewed Feb 13, 2026
View reviewed changes

chargome merged commit 337f538 into developFeb 13, 2026
68 checks passed

chargome deleted the cg/turbo-tx-parameterization branch February 13, 2026 12:54

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

github-actionsBot mentioned this pull request Feb 24, 2026
Context transaction name is not parametrized anymore #19312
Closed

add tests
cd9cb83

chargome self-assigned this Feb 13, 2026

chargome added 2 commits February 13, 2026 11:24

add capture tests
aa10473

set tx name in onspanstart
f08eb02

chargome changed the title ~~test(nextjs): Add parameterization tests for errors in route handlers~~fix(nextjs): Set parameterized transaction name for non-transaction eventsFeb 13, 2026

chargome marked this pull request as ready for review February 13, 2026 10:29

chargome requested a review from logaretm February 13, 2026 10:29

sentryBot reviewed Feb 13, 2026
View reviewed changes

Comment threaddev-packages/e2e-tests/test-applications/nextjs-16/tests/route-handler.test.ts Outdated

andreiborza approved these changes Feb 13, 2026
View reviewed changes

chargome added 2 commits February 13, 2026 11:46

unify error tx naming
88eeda3

.
b66a1b9

sentryBot reviewed Feb 13, 2026
View reviewed changes

Comment threadpackages/nextjs/src/server/handleOnSpanStart.ts

wat
c258284

cursorBot reviewed Feb 13, 2026
View reviewed changes

chargome merged commit 337f538 into developFeb 13, 2026
68 checks passed

chargome deleted the cg/turbo-tx-parameterization branch February 13, 2026 12:54

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

github-actionsBot mentioned this pull request Feb 24, 2026
Context transaction name is not parametrized anymore #19312
Closed

Uh oh!

Uh oh!

Conversation

chargome commented Feb 13, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

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

Uh oh!

Codecov Results 📊

Uh oh!

github-actionsBot commented Feb 13, 2026

Codecov Results 📊

Uh oh!

Uh oh!

andreiborza left a comment

Choose a reason for hiding this comment

Uh oh!

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

Test uses conditional instead of separate test cases

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Uh oh!

Conversation

chargome commented Feb 13, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

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

Uh oh!

Codecov Results 📊

Uh oh!

github-actionsBot commented Feb 13, 2026

Codecov Results 📊

Uh oh!

Uh oh!

andreiborza left a comment

Choose a reason for hiding this comment

Uh oh!

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

Test uses conditional instead of separate test cases

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Uh oh!

Conversation

chargome commented Feb 13, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

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

Uh oh!

Codecov Results 📊

Uh oh!

github-actionsBot commented Feb 13, 2026

Codecov Results 📊

chargome commented Feb 13, 2026•
edited
Loading

github-actionsBot commented Feb 13, 2026•
edited
Loading

chargome commented Feb 13, 2026•
edited
Loading

github-actionsBot commented Feb 13, 2026•
edited
Loading

chargome commented Feb 13, 2026•
edited
Loading

github-actionsBot commented Feb 13, 2026•
edited
Loading

chargome commented Feb 13, 2026•
edited
Loading

github-actionsBot commented Feb 13, 2026•
edited
Loading