Deployment

This page details the steps to deploy a new version of DeckMaster. This is done by the maintainer once the new release is ready.

Steps

1. Create a branch of main to draft the release in. Note, the branch should not be named using the same convension as tags (semantic with v prefix) as there is an unconfirmed bug that can unpublish a release. Instead, you should just name the branch with the version number omitting the prefix.
2. Merge all new features/patches into the new branch, resolving any merge commits along the way.
3. Manually test each new feature/patch to make sure that the other additions did not affect it.
4. Merge the branch into main.
5. Once workflows are complete, add the changelog text to the draft and publish the new release.