Skip to content

Better release process #15

@drzax

Description

@drzax

There are too many manual steps involved in cutting a new release. I just came back to it for the first time in a few weeks and have failed for 3 separate reasons, including that there appears to have been a version published to npm from a branch other than main.

I propose we use something like np which does a bunch of pre-flight to make sure everything is in order before attempting to release a new 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