[Chore] Update release instructions

Problem: Turns out the release instructions are not entirely accurate.

In order for `xrefcheck-action` to work, the release page must have the
linux binary and the windows zip file attached.

Turns out the recommended way to do this is to edit the "auto-release"
page created by the "Create a pre-release" CI step, see the instructions
here:
https://raw.githubusercontent.com/serokell/scratch/release-binary/scripts/release-binary.sh

Solution: edit the release checklist to include these instructions.
This commit is contained in:
Diogo Castro 2022-09-24 13:33:51 +01:00
parent 4cf1f562f7
commit 4eadd0198a
No known key found for this signature in database
GPG Key ID: 24CC151ACE03BA28

View File

@ -54,7 +54,8 @@ checkmark indicating that you are sure it is dealt with (be that by irrelevance)
- [ ] I updated the version number in `package.yaml`.
- [ ] I updated the [changelog](https://github.com/serokell/xrefcheck/tree/master/CHANGES.md) and moved everything
under the "Unreleased" section to a new section for this release version.
- [ ] (After merging) I created a new entry in the [releases](https://github.com/serokell/xrefcheck/releases) page,
with a summary of all user-facing changes.
* I made sure a tag was created using the format `vX.Y.Z`
- [ ] (After merging) I edited the [auto-release](https://github.com/serokell/xrefcheck/releases/tag/auto-release).
* Change the tag and title using the format `vX.Y.Z`.
* Write a summary of all user-facing changes.
* Deselect the "This is a pre-release" checkbox at the bottom.
- [ ] (After merging) I updated [`xrefcheck-action`](https://github.com/serokell/xrefcheck-action#updating-supported-versions).