This is a draft of the steps taken to make a release.
I intend to flesh this out as I actually make releases.

Try to push our dependency changes upstream:
  https://github.com/mikedilger/qrcode-rust  (unlikely, stale for >3 years)
  https://github.com/mikedilger/egui

nostr-types
   -- cargo update, and check for new versions, maybe update dependencies
   -- cargo test
   -- cargo clippy; cargo fmt
   -- FORK 0.N:
      -- all deps switch to released versions
      -- version 0.N
      -- package/publish
      -- version to 0.N.1-unstable
   -- master:
      -- version to 0.N+1.0-unstable

gossip-relay-picker
   -- cargo update, and check for new versions, maybe update dependencies
   -- cargo test
   -- cargo clippy; cargo fmt
   -- FORK 0.N:
      -- all deps switch to released versions
      -- version 0.N
      -- package/publish
      -- version to 0.N.1-unstable
   -- master:
      -- version to 0.N+1.0-unstable

gossip
   -- cargo update, and check for new versions, maybe update dependencies
   -- cargo test
   -- cargo clippy; cargo fmt
   -- FORK 0.N:
      -- all deps switch to released versions
      -- verison 0.N
      -- package/publish (see below)
      -- version 0.N.1-unstable
   -- master
      -- version 0.N+1.0-unstable

-----------------------------
Package & Publish of gossip:

Package for windows:
 * main version, as .msi
 * main version with lang-cjk, as .msi

Package for debian:
 * main version, as .msi
 * main version with lang-cjk, as .msi

Create github release (it will create source tar files)
 * Post the windows .msi files
 * Post the debian .deb files

Update aur.archlinux.org PKGBUILD