Future of the project

[StefanTerdell]

Hello! This week I archived the repo, believing it had done its job. I've received some feedback both on here and on linked-in of all places asking me to reconsider.

While v3 is more or less as feature-complete its going to get, I can see why an archived repo with no way to register critical bugs etc. might make some of the developers behind the 13 14 million weekly downloads (!) a bit nervous.

Well, fair enough. Just wanted to let you know that while I'll be looking around for a new maintainer, until I find one I will keep the repo open for reporting any new-found issues. When I do I might stay on in a lead role, or as a human npm-package publishing bot. We'll see.

If you have any opinions on the matter, feel free to voice them here I guess.

[clemens]

One other thing that might make people nervous is the fact that the released package version is at 3.25.1, while the releases here on GitHub only seem to go to version 3.20.3 from almost 3 years ago – and the tags are also missing. In a year after a couple of major NPM-related supply chain attacks, I'd consider this suboptimal.

=> I'd suggest to create the missing releases and tags and ideally update your automations to create them for potential future releases.