You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But lately, we're noticing few anomalies with our releases, wherein
There are duplicate releases with no artefacts. The releases made by our CI servers are correct since they have artefacts with valid dist. While we are currently clueless as to why redundant releases are being created.
There are totally new releases created with missing @{package_version} part in the release name. This is even weirder, since if we assume that package_version is empty string while we set release for Sentry on client end, the release will still end with @ as evident in the string interpolation.
Steps to reproduce:
Step
Issue in release management
Actual result:
Actual
Releases should be unique and dictated by release management and/or setting release in Sentry SDK Expected result:
Result
Duplicate releases and releases with invalid version
The text was updated successfully, but these errors were encountered:
I am closing all old issues, please if this is still a problem feel free to revive it.
Also, consider moving to our new SDK @sentry/react-native if it still happens there please open a new issue.
OS:
Platform:
Output of
node -v && npm -v && npm ls --prod --depth=0
Config:
I have following issue:
We have a custom release creation and artefact upload mechanism in place. Our releases are generally of the form
This works fine with the following client side code:
But lately, we're noticing few anomalies with our releases, wherein
dist
. While we are currently clueless as to why redundant releases are being created.@{package_version}
part in the release name. This is even weirder, since if we assume thatpackage_version
is empty string while we set release for Sentry on client end, the release will still end with@
as evident in the string interpolation.Steps to reproduce:
Issue in release management
Actual result:
Releases should be unique and dictated by release management and/or setting release in Sentry SDK
Expected result:
Duplicate releases and releases with invalid version
The text was updated successfully, but these errors were encountered: