fix(publish): support my-repo@[version] versions

Closes #653

BREAKING CHANGE: Use sentry [email protected] name instead of reponame-1.2.3 which doesn't match any convention in Sentry

Author: ryshu

Diff for: README.md

@@ -66,7 +66,7 @@ The plugin can be configured in the [**semantic-release** configuration file](ht
 | `sourcemaps`    | Directory with sourcemaps. Example `dist`. Optional for upload sourcemaps                                                                                                                                                                                                                                                                                                                                                                                  |
 | `urlPrefix`     | URL prefix for sourcemaps. Example `~/dist`. Optional for upload sourcemaps                                                                                                                                                                                                                                                                                                                                                                                |
 | `rewrite`       | Boolean to indicate rewrite sourcemaps. Default `false`. Optional for upload sourcemaps                                                                                                                                                                                                                                                                                                                                                                    |
-| `releasePrefix` | String that is passed as prefix to the sentry release. <br/> Optional to fix the problem that releases are associated with the organization instead of the project ([Read More](https://github.com/getsentry/sentry-cli/issues/482)). <br/> Ex: `releasePrefix:"web1"` would resolve **only** the sentry release to `web1-1.0.0`. <br/>**Important Notice:** when you use this feature you also have to change the release name in your sentry client app. |
+| `releasePrefix` | String that is passed as prefix to the sentry release. <br/> Optional to fix the problem that releases are associated with the organization instead of the project ([Read More](https://github.com/getsentry/sentry-cli/issues/482)). <br/> Ex: `releasePrefix:"web1"` would resolve **only** the sentry release to `web1@1.0.0`. <br/>**Important Notice:** when you use this feature you also have to change the release name in your sentry client app. |
 
 | `pathToGitFolder` | Path to `.git` folder, relative to the current working directory. Optional. Defaults to current working directory |
 

Diff for: src/publish.js

@@ -69,7 +69,7 @@ module.exports = async (pluginConfig, ctx) => {
     const commits = await parseCommits(pluginConfig, ctx)
     ctx.logger.log('Commit data retrieved')
     const sentryReleaseVersion = pluginConfig.releasePrefix
-      ? `${pluginConfig.releasePrefix}-${ctx.nextRelease.version}`
+      ? `${pluginConfig.releasePrefix}@${ctx.nextRelease.version}`
       : ctx.nextRelease.version
     /** @type {SentryReleaseParams} */
     const releaseDate = {

Diff for: test/publish.test.js

@@ -255,7 +255,7 @@ describe('Publish', () => {
       ctx,
     )
     expect(result.release.version).to.equal(
-      `${releasePrefix}-${ctx.nextRelease.version}`,
+      `${releasePrefix}@${ctx.nextRelease.version}`,
     )
   })