Release process is entirely manual

liw opened 1 year ago

I keep forgetting to make a tag, or to push it.

z6MkrnXJ...SFS3 commented 1 year ago

I’d offer to help write a pipeline that runs on the Concourse CI setup instance I’m running for Radicle.

liw commented 9 months ago

Alas, the way I do releases isn't doable in CI. There's manual steps that can't be updated, e.g., updating release notes. But I can script the parts that can be automated and run the script locally, and I think that'll be good enough.

liw added chore 9 months ago

liw commented 9 months ago

Rough release process, right now:

Update NEWS.md based on changes since the previous release.
Make sure make passes correctly.
Run cargo msrv find to figure out what the next version number should be.
Update version in Cargo.toml and debian/changelog.
Make sure everything is committed.
Run cargo publish --dry-run then fix any problems it finds.
Create a signed git tag for the release.
Run cargo publish.
Announce new release on Zulip.

After the release:

Add new release commit to the upgrade test and drop any releases that are no longer needed.
If needed, update and release any dependent Radicle CI components.

liw commented 3 months ago

I've started automating the mechanical steps in a new tool, unperish, https://app.radicle.xyz/nodes/radicle.liw.fi/rad%3Az38NiGQiDgKqP7BK6kazjU5ooUuEm