Skip to content

support prereleases #7

Description

@davidjgoss

Is your feature request related to a problem? Please describe.
GitHub releases can be marked as prerelease. It would make sense to do this for release candidates.

Describe the solution you'd like
An optional prerelease input that defaults to false which we could trigger from our release action in consuming projects.

Describe alternatives you've considered
Manually updating releases once they're created, as I've done with cucumber-js.

Additional context
Not a high priority - we're doing it when publishing to npm which is important as it affects user installs, GitHub is more of a reference point.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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