xmtop/docs/releasing.md

Current steps for a release

1. Update Version in main.go (now set in package build)
2. Update CHANGELOG.md
3. Tag
4. Push everything
5. Wait for the github workflows to complete
6. Download and verify the correct version of one of the binaries
7. Finish the draft release and publish.
8. Check gotop-builder for a successful everything build; if successful, publish.
9. Notify Nix
10. Notify Homebrew Automated now.
11. Trigger extensions:

    for p in builder nvidia remote linux; do
    curl -H "Accept: application/vnd.github.everest-preview+json" \
         -H "Authorization: token ${TOKEN}" \
         --request POST \
         --data "{'event_type': 'my-release', 'client_payload': {'tag': '${TAG}'}}" \
         https://api.github.com/repos/xxxserxxx/gotop-${p}/dispatches
    done
    

    and then go in and mark each release as not a pre-release.
12. Wait for the AUR project to finish building.
    1. Update package versions in gotop and gotop-bin
    2. namcap PKGBUILD
    3. updpkgsums
    4. makepkg --printsrcinfo > .SRCINFO
    5. git commit -a
    6. git push
    7. Test install gotop, gotop-bin, and gotop-git with running & version check

The AUR project still needs secret credentials to aurpublish to the AUR
repository, so the final publish step is still currently manual.

Nix

I haven't yet figured this out, so currently just file a ticket and hope somebody on that end updates the package.

Nix adds new and interesting complexities to the release.

0. Download the gotop src package; run sha256 on it to get the hash
1. cd to the nixpkgs directory
2. Update the sha256 hash in pkgs/tools/system/gotop/default.nix
3. docker run -it --rm --mount type=bind,source="\$(pwd)",target=/mnt nixos/nix sh
4. cd /mnt
5. install & run vgo2nix to update deps.nix
6. nix-build -A gotop
7. When it fails, ...