Bump version, deployment notes

Author: budak7273

DEPLOYMENT.md

@@ -0,0 +1,26 @@
+# Deployment
+
+A [GitHub Action](https://github.com/satisfactorymodding/SatisfactoryModManager/blob/master/.github/workflows/push.yml)
+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](https://github.com/satisfactorymodding/SatisfactoryModManager/actions/workflows/push.yml) artifact output.
+You need to be signed into GitHub to download them, and they expire after some time.
+
+TODO how to point dev builds to ficsit.dev (staging) instead?
+
+## Releases
+
+To create a new published release:
+
+1. Ensure all intended changes are merged into the `master` branch.
+2. Make a `Bump version` commit on the master branch to increase the `productVersion` field in `wails.json`. Version numbers should follow [Semantic Versioning](https://semver.org/).
+3. Manually create and push a tag of the format `v*` to that commit, which triggers a [GitHub Action to make a release](https://github.com/satisfactorymodding/SatisfactoryModManager/blob/master/.github/workflows/release.yml).
+4. Have someone on the Satisfactory Modding team with Signpath access approve the release.
+   At the time of writing, that's Vilsol and Mircea.
+5. Review the draft release automatically created by Goreleaser and edit its description as needed.
+6. Publish the release.
+
+Users will automatically be prompted to update next time they launch SMM.

wails.json

@@ -12,7 +12,7 @@
     "email": "mircearoatapalade@gmail.com"
   },
   "info": {
-    "productVersion": "3.0.3",
+    "productVersion": "3.0.4",
     "fileAssociations": [
       {
         "ext": "smmprofile",