1
0
mirror of https://github.com/EDCD/EDMarketConnector.git synced 2025-06-06 10:23:06 +03:00

docs/Releasing: Also replace hashes.sum if overriding an auto build

This commit is contained in:
Athanasius 2021-08-10 15:38:34 +01:00
parent 6328c47a41
commit 9027d7a4f1
No known key found for this signature in database
GPG Key ID: AE3E527847057C7D

View File

@ -305,9 +305,9 @@ installer file prior to making the release live.
Once that is done then for manually built installers: Once that is done then for manually built installers:
1. Add a git tag for the release, which you'll refer to when actually creating 1. Add a git tag for the release, which you'll refer to when actually creating
the release: the release:
1. This should be named `Release/A.B.C`, e.g. `Release/4.0.2.` as per 1. This should be named `Release/A.B.C`, e.g. `Release/4.0.2.` as per
the version string. the version string.
**Do NOT add this tag until you're sure you're ready. Pushing a tag to **Do NOT add this tag until you're sure you're ready. Pushing a tag to
GitHub that matches the pattern `Release/*` (double-check this in GitHub that matches the pattern `Release/*` (double-check this in
@ -316,8 +316,16 @@ Once that is done then for manually built installers:
Yes, this does mean you should really just be using this auto-build setup Yes, this does mean you should really just be using this auto-build setup
when creating an installer for release to users. You'll at least need to when creating an installer for release to users. You'll at least need to
edit the draft release that it creates, i.e. swap out its `.msi` for the edit the draft release that it creates:
one that you built. But, **again, you should just be using the auto-build
1. Swap out its `.msi` for the one that you built.
2. Create a matching `hashes.sum` file for your `.msi` file:
sha256sum EDMarketConnector_win*.msi > ./hashes.sum
and replace the one in the draft release with this.
But, **again, you should just be using the auto-build
mechanism**. mechanism**.
3. Now push the release-specific branch to GitHub. 3. Now push the release-specific branch to GitHub.