Updates

Ropenode checks for a new version 30 seconds after it starts, and then once a day. The check is quiet: it never interrupts you, and an offline machine simply skips it.

Installing an update

When a new version is ready, a notice at the top of the window offers Restart to update. Ropenode downloads it, installs it and restarts. Your projects, settings and history are kept — they live in %APPDATA%\ropenode\, which the installer never touches. If agent consoles are running, Ropenode asks first, because restarting ends them; their conversations are kept and can be resumed.

To look straight away, use Settings → Licence → Check for updates. You can also download the new version from the download page and run its installer over the one you have.

Every release is signed

Each release is signed on the build machine with a private key that never touches the server, and the app checks that signature against a public key built into the copy of Ropenode you are already running before it installs anything. That makes the update server an untrusted party: compromising it could stop you getting updates, but it could not push you a modified build.

For a manual download, the download page lists each installer's SHA-256, so you can check the file yourself.