fix(nextjs): Fix automatic release value discovery #6513
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #6504
In we switched from the Sentry Webpack plugin to using a custom loader to inject the release value into the SDK that either reads from options or from environment variables. We didn't consider that the Webpack Plugin (or rather Sentry CLI) has a mechanism to determine a release value apart from options or environment variables.
This PR in essence reverts #6404 which introduced this bug.