From what I can see at, e.g., https://docs.sentry.io/product/cli/releases/, Sentry seems to intend for you to use reponame@version (where version is either a commit hash or semver`) vs.
repoPrefix allows generating reponame-1.2.3, but not reponame@1.2.3.
Would you accept a PR to support a different parameter to support this, or do you know of another workaround to tweak the way the plugin receives ctx.nextRelease.version?
From what I can see at, e.g., https://docs.sentry.io/product/cli/releases/, Sentry seems to intend for you to use
reponame@version(where version is either a commit hash or semver`) vs.repoPrefixallows generatingreponame-1.2.3, but notreponame@1.2.3.Would you accept a PR to support a different parameter to support this, or do you know of another workaround to tweak the way the plugin receives
ctx.nextRelease.version?