Release automation

[Tunous]

Current idea for a workflow looks like this:

1. Run manual workflow
   • [ ] An automated pull request is created preparing all that is necessary for a release
     • [x] Update repository changelog
     • [ ] Update F-Droid changelog
     • [ ] Keep these up to date if changes happen before merge
     • [ ] Read current version from build file
2. Review and merge "release pull request"
   • [ ] Merged commit is tagged with appropriate version
     • [x] GitHub release is created with correct changelog and assets
     • [ ] New version is uploaded to Play Store internal (or beta?) track
   • [ ] Commit with bump for new version is created
   • [ ] Matching milestone is closed
   • [ ] A milestone for new version is created

This is being done so it'll be much quicker to release new version preventing long waits on users side for new features.

[Tunous]

Updated with new steps and marked what is done or still is todo with task list.

[AbsurdlySuspicious]

Commit with bump for new version is created

~~I presume it should update versionName too, but which digit should it increment by default? Patch or minor?~~ EDIT: nvm, I see there's an input for this in action already

[Tunous]

It should increment patch number. The version entered into action is actually used to prepare changelog and merge request. Should change it to extract that from build file instead.

[msfjarvis]

I did some buildSrc fuckery to implement automatic version bumps in Password Store, the workflow logic is a bit complicated by how we handle branching there but I can port it to Dawn sometime in the coming week.

[Tunous]

That won't be necessary. We have access to gradle so getting it will be easy. I'm more interested in finding something to automate F-Droid changelog.