Current steps for a release

~~Update Version in main.go~~ (now set in package build)
Update CHANGELOG.md
Tag
Push everything
Wait for the github workflows to complete
Download and verify the correct version of one of the binaries
Finish the draft release and publish.
Check gotop-builder for a successful everything build; if successful, publish.
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
Notify Nix
~~Notify Homebrew~~ Automated now.

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

Oh, what a tangled web.

for p in builder nvidia remote; 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

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.

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

1.7 KiB Raw Blame History

Current steps for a release

Nix

1.7 KiB

Raw Blame History