Skip to content

Extra quick reference in deploy steps #354

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mircearoata merged 1 commit into from
May 12, 2026
Merged

Extra quick reference in deploy steps #354

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion DEPLOYMENT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,8 +19,10 @@ To create a new published release:
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](https://semver.org/).
4. Manually create and push a tag of the format `v*` to that commit, which triggers a
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](https://github.com/satisfactorymodding/SatisfactoryModManager/blob/master/.github/workflows/release.yml).
- 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.
Expand Down
Loading