Skip to content

Write down how to cut a release #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
paulglover merged 1 commit into from
Aug 10, 2026
Merged

Write down how to cut a release #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -435,6 +435,36 @@ go vet ./...
make deb # proves nfpm.yaml still packages
```

## Cutting a release

The version in the package comes from `git describe`, so the tag is the first
step rather than the last — build before tagging and the `.deb` is named after
the previous release.

```bash
git checkout main && git pull # from a clean tree: --dirty
# would land in the version
git tag -a vX.Y.Z -m "vX.Y.Z"
git push origin vX.Y.Z

make deb # amd64
make deb ARCH=arm64 # and arm64
( cd dist && shasum -a 256 *.deb > SHA256SUMS )

gh release create vX.Y.Z --prerelease \
--title "vX.Y.Z" --notes "…" \
dist/randomimageviewer_X.Y.Z_amd64.deb \
dist/randomimageviewer_X.Y.Z_arm64.deb \
dist/SHA256SUMS
```

Both architectures, even though the deployment this was written for is amd64:
`make deb` alone quietly produces an amd64-only release, and a Pi is an obvious
place to run this.

Drop `--prerelease` once a version has run somewhere other than the machine it
was written on.

## License

MIT — see [LICENSE](LICENSE).
Loading