Add changelog and release tool (it should give credit to author, provide link to the pr merged, with description (ideally pr title, which means the only thing we need to manually ensure is that PR titles are accurate descriptions prior to merge)
If you write one from scratch, and it's good/fulfills needs, while I can't speak for the org, I personally believe you would become the maintainer if the tool becomes part of the org, making this a enticing issue to tackle. that said, there are many such tools, re-invent if you want, but copy ideas from other node changelog release tools to gain experiential knowledge and ideas. (in other words, if you don't think a new changelog/release tool that can be used widely and has potential to gain large nodejs community momentum, don't write your own. However, if your frustrated with most of the tools out there, go for it. I have not looked, so I'm leaving this research and dev up to the contributor who tackles this.
Note, while the pr for the tool can be submitted here, once approved and discussed, it will need to be added to all http-party repos. If it's a re-written/re-invent the wheel new lib, it'll need it's own repo, in which case, you can point to your personal github for discussion and we'll transfer ownership, upon approval of all http-party maintainers.
(1/10 or 1/100 chance of writing a new tool and succeeding, so make it a code kata, not and end all goal, just fyi, for your sanity, friends, don't get your hopes up too high. again i don't know what else is out there atm though...)
Add changelog and release tool (it should give credit to author, provide link to the pr merged, with description (ideally pr title, which means the only thing we need to manually ensure is that PR titles are accurate descriptions prior to merge)
Note, while the pr for the tool can be submitted here, once approved and discussed, it will need to be added to all http-party repos. If it's a re-written/re-invent the wheel new lib, it'll need it's own repo, in which case, you can point to your personal github for discussion and we'll transfer ownership, upon approval of all http-party maintainers.
(1/10 or 1/100 chance of writing a new tool and succeeding, so make it a code kata, not and end all goal, just fyi, for your sanity, friends, don't get your hopes up too high. again i don't know what else is out there atm though...)
Addresses a bullet in #92
EDIT: Look into github packages: https://docs.github.com/en/packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages ?