Post

NullVoxPopuli@nullvoxpopuli.com

💥 just released a thing: `release-plan` it aims to be a very simple, secure release workflow for maintainers that adheres to best security practices ⚪ trusted publishing on npmjs.com ⚪ github environment protection ⚪ generated release PR + changelog ⚪ automatic release + publish on merge ✨

Let's? 🤷

we have the power!

This is exactly the kind of conversation that could bring the package maintenance working group back together lol. Pretty sure I even proposed that we build release tooling sometime a while ago.

I used to build release tooling, and then I went through: release-it (didn't like tag-based automation) then semantic-release (didn't like commit strictness) then changesets (I like the changelog fidelity at review time, but it fell apart trying to get others on board, and distracted submitters)

23/5/26, 2:27 pm0 reposts3 likes

then the folks I work with (and somewhat myself, (albeit earlier iterations that weren't good enough)) built release-plan -- which at the very least *I* think looks promising - idempotent phased releases (tag, gh release, npm release, etc) - changelog preview and opportunity to edit - etc

@danielroe.dev already pointed this out, but it's super amusing that we independently basically built the same thing haha