Post

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

Curious, what are your views on changesets? I’m kinda torn

it looks really nice and I would consider it if I needed a more complex workflow or independent versioning of packages but I wanted something effortless + simpler, that works off of the metadata already present in conventional commits

I used to use changesets, but then helped develop release-plan -- which supports both same versions and independent versions dependening on config, and semver impact labels I do still miss the fidelity of a manual high context changelog entry tho

`uppt` supports editing the PR body so you can add context maybe a feature for release-plan?

Editing everything every step of the way if you want is supported - the release preview pr gives a last chance there But it doesn't use the pr description for changelog - i want a way for it to do so

But! How does uppt differentiate between info for changelog and info for reviewer ? (Why, how to review, considerations, etc) Seems very useful! I suppose it could be done with html comment markers or something

ahhhh no, I mean it supports editing the release PR body, which becomes the changelog entry. I find it _fascinating_ we both ended up with very, very close to the same workflow great minds, eh?

Automation is so nice! The thing i'm excited for next is plugins: with a way for them to all be idempotent like the existing bits: github.com/release-plan... Reason: i want to have vscode marketplace and open vsix plugins in addition to npm cc @evoactivity.bsky.social <3

I have very similar plugin plans for bumpy.varlock.dev 🐸 I think it fixes some things you were wanting in changesets. I’m fairly convinced that a file based workflow is right for non trivial cases. Also bumpy has a command to generate a bump file from conventional commits - best of both worlds.

awesome! I really do like the fidelity that changesets encourage when the context is fresh in PRs I also used to use semantic-release using conventional commits -- but it was too much a hassle for drive-by contributions :(