Upgrading to 7.91.0 breaks applications using @sentry/next `transaction.end is not a function`

[pckilgore]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/nextjs

SDK Version

7.91.0

Framework Version

13.3.4

Link to Sentry event

No response

SDK Setup

const config = {
  dsn: process.env.NEXT_PUBLIC_SENTRY_DSN,
  release: process.env.NEXT_PUBLIC_SENTRY_RELEASE,
  environment: publicRuntimeConfig.sentryEnvironment,
};

Sentry.init(config);

Steps to Reproduce

Upgrade to 7.91.0 from 7.88.0

Expected Result

Application continues to work as it has.

Actual Result

Application crashes with transaction.end is not a function.

This occurred across all our routes, example above.

Reverting fixes.

[pckilgore]

Looks like #9979 might be related, didn't come up in a search but looking at the error in the screenshot there seems similar root cause around .end not a function.

[pckilgore]

Based on a quick look at the diff and the error message, this appears to be the cause:

This PR: a04e780

cc @mydea

[lforst]

@pckilgore This is very likely because some of your @sentry/* dependencies' versions aren't aligned. Can you check this? Thanks!

[Cluster2a]

Got the same issue with @sentry/sveltekit 7.91.0.
No other sentry-dependencies involved.

[lforst]

If you run into this issue please check that all your sentry dependencies are aligned in your lockfile. If this is indeed a bug we need reproduction. All of our integration tests are passing which, in-theory, means everything is fine.

This error symptom can basically only happen if you have messed up dependencies. Unless I am missing something ofc.