Skip to content

Commit 520e6b9

Browse files
committed
update release procedure
1 parent 4c62ef2 commit 520e6b9

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

release-procedure.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,15 +2,15 @@
22
1. Update `version.txt` and the `AssemblyVersion` tag in `Gui.csproj` and/or `AvaGui.csproj`
33
1. Add, commit, push these changes with the commit message "prepare <x.x.x>"
44
1. `git tag -a 'x.x.x'`, where the x's are the new version number
5-
1. `git push --tags`
5+
1. `git push --tags` with the tag message "tag <x.x.x>"
66
1. Locally in Visual Studio, create a release build for each platform
77
1. `dotnet publish AvaGui/AvaGui.csproj -c Release -p:PublishSingleFile=true --runtime win-x64 --self-contained`
88
1. `dotnet publish AvaGui/AvaGui.csproj -c Release -p:PublishSingleFile=true --runtime linux-x64 --self-contained`
99
1. `dotnet publish AvaGui/AvaGui.csproj -c Release -p:PublishSingleFile=true --runtime osx-x64 --self-contained`
1010
1. For the OSX and Linux builds, `chmod +x` the binary to make it executable
11-
1. Zip up each build appropriately
12-
1. Windows - make a ZIP file
13-
1. :Linux - `tar -jcvf linux-x64.tar linux-x64`
14-
1. OSX (Mac) - `tar -jcvf osx-x64.tar osx-x64`
11+
1. Go into the `publish` directory for each build, and zip each appropriately
12+
1. Windows - make a ZIP file, named `object-editor-x.x.x-win-x64`
13+
1. Linux - `tar -jcvf object-editor-x.x.x-linux-x64 .`
14+
1. OSX (Mac) - `tar -jcvf object-editor-x.x.x-osx-x64 osx-x64`
1515
1. In GitHub, create a new release from that tag
1616
1. On that release page, add the zipped files as build artefacts

0 commit comments

Comments
 (0)