add release-plan to simplify releases

[mansona]

I ran npm init release-plan-setup@latest to create this PR

This adds release-plan which is a super easy way to get npm releases done. I noticed that there were a few people asking for something to be released in #315 so I thought I would provide a solution rather than adding to the chorus of people 👍

[punit1108]

Is this repo active?

[NullVoxPopuli]

it doesn't seem like it, based on #315

if the maintainer wants help or doesn't have the bandwidth, I'm more than happy to lend a hand!

[lupomontero]

Hi @mansona, many thanks for suggeting this and apologies for the delay in getting back to you. I struggled to maintain this repo for quite a while due to work and personal issues, but I'm now back and two new releases have been published in the last couple of weeks.

I'm doing a lot of house keeping 🏠🧹 (issues, PRs, ...) as well as modernising the tooling.

I'm not familiar with release-plan but will look at it soon, as well as alternatives, to help streamline releases.

[lupomontero]

cc/ @mfdebian

[mansona]

let me know if you have any questions about it :) really i was just trying to help the process of the release along so feel free to ignore this PR now that things are back moving again.

And to be honest, looking at your git history, I'm not too sure release-plan is the best tool for you 🤔 It really relies on Github PRs to get information about what is in a release and if I'm not mistaken you're doing a rebase-merge for github PRs? So the fact that there is not a merge commit for each PR might prevent you from using release-plan 😞