feat: allow disabling automatic version detection for releases #314
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.
This small change allows release to be set to undefined without being overridden with automatic release.
In v4 it was possible to set
clientConfig: { release: undefined }
(and same for server) to override automatically generated value. In v5 the merging library has been changed tolodash.merge
which is ignoringundefined
values making it no longer possible to override automatic release generation.We prefer not to include release in the configuration to avoid unnecessary changes to built files (small perf improvement for returning visitors). Instead we rely on
window.SENTRY_RELEASE
/process.env.SENTRY_RELEASE
. For that to work release must be undefined.