Skip to content

support my-repo@[version] versions #653

Closed
@wyardley

Description

@wyardley

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 [email protected].

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions