Updates

The app updates itself (ui/updates.go), with MyGo’s updater: it downloads the new version’s signed archive, or a delta from the running version, checks the signature against the public key built into the app, and replaces the app.

In the app

• A little after it starts (15 s) and every 6 hours, the app asks for a newer version, unless Check for updates automatically is off in the update dialog.
• A version found shows in a card at the window’s bottom right: Update now installs it there, What’s new opens the dialog, Later puts the card off until the app starts again (each launch shows it again, until the version is installed or skipped). It also stays as Update to x.y.z in the title bar.
• The chip opens the dialog: the release notes, then Install update, Later or Skip this version (a skipped version shows again only when asked for). Installing shows its progress and can be cancelled; the running app goes on meanwhile.
• Restart now runs the new version. Its daemon is of the same version, so the app replaces the local one as it connects (hostconn), and the daemon brings the sessions back, agents continuing their conversations. Servers’ daemons are upgraded the same way at their next connection.
• Check for updates in the command palette asks now and says how it went.

Development builds (make dev) and builds without an update feed don’t update themselves: the palette says so, and the background checks stay quiet.

Where updates come from

GitHub Releases of enowx/enowx (updates.github in cmd/enowx/mygo.json): apps read the update manifests of the latest published release, and check each update’s signature against updates.publicKey, built into them.

The secret half of that key signs every release. It is the repository secret MYGO_UPDATER_PRIVATE_KEY, and a copy is kept by the maintainer outside the repository: installed apps accept only updates signed with it, so losing it strands them, and whoever has it can ship code to every user. Never commit it.

Releasing

1. Set the version in cmd/enowx/mygo.json, and add its section to CHANGELOG.md (## x.y.z): it is what the update dialog shows.
2. Commit, then tag and push: git tag vx.y.z && git push origin vx.y.z.
3. The Release workflow (.github/workflows/release.yml) checks the tag against the version and the changelog, creates a draft release, and builds every platform on its own runner (mygo build -upload): the installers, each platform’s signed archive, delta updates from the last versions, and update-<platform>.json, uploaded to the draft.
4. Look at the draft, then publish it: from then on, apps find it within six hours, or at once with Check for updates.

Running the workflow by hand builds the same files as the run’s artifacts, publishing nothing.

Apps installed by a package manager (the .deb in /opt) are updated by it, not by themselves; the disk image’s app, the Windows setup’s and Linux’s install.sh install update themselves.