Release pipeline

[rumpl]

Feature request description

I would like us to change the release pipeline, currently, in order to make a new release I have to:

• create a new tag
• create a release for that tag in github
• this will start a GHA that will release depcheck on npm

The issue with this order is that, after creating/pushing a tag the release GHA could fail (it has happened in the past). And we are now stuck with a tag that doesn't mean anything and was never released.

We should switch the pipeline so that I can do:

• start a release pipeline by giving it a git ref (branch, commit, whatever), using main as default
• once the release is really up on npm I can create a tag for it
• after tagging I can create a release in github

I'm pretty sure there exists a GHA somewhere that could do all of this in a single setting so that I don't even have to create the tag/release myself.

[pastelsky]

@rumpl have you considered using np — It takes away a lot of the pain with publishing new versions.

Also, it's been a while since an update was released. There's a bunch of fixes on master that I could use — do you mind cutting a release?

[rumpl]

Of course sindresorhus made a package for that :D

I didn't know np existed, I'll take a look.

Yeah I think it's high time for a new release, I'll take a quick look at the pending PRs and make a new release 👍

[pastelsky]

Thanks for your effort in maintaining this. Looking forward to the next release.