blob: c05b61f646c7f3ede9e6ef23ad56e7ca8e53869b (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
|
# 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.
10. Wait for the [AUR](https://github.com/xxxserxxx/gotop-linux) 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
11. Notify Nix
12. ~~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.
## 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`
2. `docker run -it --rm --mount type=bind,source="\$(pwd)",target=/mnt nixos/nix sh`
3. `cd /mnt`
8. install & run vgo2nix to update deps.nix
7. `nix-build -A gotop`
8. When it fails, ...
|
