We release Wasabi and as part of the process we publish a note under this public key npub129hpcwy3h7uhpzwzts6utkt2p5st7lf4qpzp3d2j0p6z56lvkpgspngzeq, which means that those who follow that account will see that there is a new version available with all the links to download the packages and verify them. The Wasabi client also subscribes to that nostr npub and listens for updates. In case a newer version is published, the Wasabi client will use the links in the nostr note to download the appropriate package, verify its authenticity, and let you know that the package was downloaded and is available for you to install. So, Wasabi users don't need to do anything. But what if something bad happens? Imagine GitHub doesn't allow us to host the releases on their platform or takes down the repository or something similar - how is this feature useful? In a case like that, we can host the packages somewhere else and update the links, or we can even publish more URIs to IPFS, Torrent, or whatever. Of course, the Wasabi client only understands HTTP, but more advanced users might prefer to download Wasabi using something different.