You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: DEPLOYMENT.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,8 +19,10 @@ To create a new published release:
19
19
2. Ensure someone with Signpath access is around to approve the release in the next few minutes.
20
20
At the time of writing, that's Vilsol and Mircea.
21
21
3. 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/).
22
-
4. Manually create and push a tag of the format `v*` to that commit, which triggers a
22
+
4. Manually create and push a tag of the format `vX.Y.Z` to that commit, which triggers a
23
23
[GitHub Action to make a release](https://github.com/satisfactorymodding/SatisfactoryModManager/blob/master/.github/workflows/release.yml).
24
+
- Create a tag on HEAD: `git tag tag_name_here`
25
+
- Push a single tag: `git push origin tag tag_name_here`
24
26
5. The action will automatically request signing approval, sending an email to approvers and including the link in the action output.
25
27
The action will busy-wait until approval is granted.
26
28
6. Review the draft release automatically created by Goreleaser and edit its description as needed.
0 commit comments