Skip to content

Fix npm dist-tags if it is actually broken #42

Description

@OliverDudgeon

I fear that switching away from (broken) release-it will just tag all new versions as latest. From the tag it would be nice to select the dist-tag and set that in the npm publish command. E.g 2.1.0-rc.3 -> rc but 1.2.3 -> latest.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions