Release mismatch on Sentry for Next.js project deployed via Vercel after upgrading from version 7 to 8

[fakkio]

I'm encountering an issue with release creation on Sentry after upgrading from version 7 to version 8 when deploying my Next.js project using Vercel.

I've configured a script that's invoked from the next.config.mjs file. This script reads the package.json and sets a release version in the format [email protected]. However, since the upgrade, Sentry is generating a release using the commit hash instead of the specified version format. As a result, the source maps and other artifacts are being uploaded to the commit-based release, not the one formatted as [email protected].

Here is the relevant part of my next.config.mjs:

function getRelease() {
  return `${appInfo.name}@${appInfo.version}`;
}

nextConfig = withSentryConfig(nextConfig, {
  // For all available options, see:
  // https://github.com/getsentry/sentry-webpack-plugin#options

  // Only print logs for uploading source maps in CI
  silent: !process.env.CI,
  release: getRelease(), // This is where I set the release version

  // Other options...
});

Has anyone else encountered this problem since upgrading? How can I ensure that Sentry uses the version from package.json as the release identifier, rather than the commit hash?

Any insights or suggestions would be greatly appreciated.