DEPLOYMENT.md

Deployment

A GitHub Action automatically creates testing builds from commits on any branch and uploads them to the run as build artifacts.

Development Builds

Since the build action is triggered on every push to any branch, non developers can obtain testing builds easily from GitHub Actions artifact output. You need to be signed into GitHub to download them, and they expire after some time.

To point development builds to ficsit.dev instead of production, see the Readme's configuration section.

Releases

To create a new published release:

1. Ensure all intended changes are merged into the master branch.
2. Ensure someone with Signpath access is around to approve the release in the next few minutes. At the time of writing, that's Vilsol and Mircea.
3. Make a Bump version commit on the master branch to increase the productVersion field in wails.json. Version numbers should follow Semantic Versioning.
4. Manually create and push a tag of the format vX.Y.Z to that commit, which triggers a GitHub Action to make a release.
   • Create a tag on HEAD: git tag tag_name_here
   • Push a single tag: git push origin tag tag_name_here
5. The action will automatically request signing approval, sending an email to approvers and including the link in the action output. The action will busy-wait until approval is granted.
6. Review the draft release automatically created by Goreleaser and edit its description as needed.
7. Publish the release.

Users will automatically be prompted to update next time they launch SMM.