Release Process¶

While the process of making beta releases is completely automated, in order to make a “real” release there are some manual steps that still need to be performed. This page serves as a checklist to make sure that no steps are forgotten

Start the release process by opening a pull request in the main swyddfa/arlunio repository, one that looks to merge develop into master
On a local copy of the develop branch, generate the changelog entry for this release with towncrier:
```
(.env) $ towncrier --version=v<VERSION>
```
It will ask if it is ok to delete the changelog snippets in the changes/ directory. Say yes.
Commit and push the removal of these files along with the updated changelog to update the pull request.
Wait to ensure that all the workflow actions pass before merging the pull request with the Create a merge commit option. The merge will then trigger the automated release pipeline which will package arlunio and publish it to PyPi.
Once the pipline has finished it will have created the release on our releases page, but the changelog entry will be missing. However the entry should be identical to the previous beta release, so copy and paste it over.
Delete the build-number-X tag to reset the beta version counter.
Checkout the master branch locally and pull down the latest changes.
Checkout develop and merge in master
Bump the version number in arlunio/_version.py to the next candidate release number.
Commit and push to the develop branch.