Releases and updates
How a new version of Griddler is built, signed, published and delivered to your PC.
One build, one version
Every change that lands on main in the Griddler repository builds a new version, numbered
0.1.<build number>. One build produces everything that version needs:
| Output | For |
|---|---|
| The Windows installer and portable app, code-signed | Windows |
| The Linux AppImage | Linux |
| The macOS app (when that stage runs) | macOS |
| The Griddler Agent image, tagged with the same version | Your agents |
The agent image and the desktop share one number on purpose. An installed Griddler always pulls the agent that was built with it, so the two always speak the same protocol.
Griddler Social and this docs site have their own pipelines and deploy on their own when their code changes. Neither needs a desktop release.
How updates reach you
- Griddler checks the update feed a few seconds after it starts and then every few hours.
- A new version downloads in the background. It installs only when you click Update in the top bar (or Restart & update in Settings), never on its own, and not when you quit.
- The Windows installer updates itself. The portable Windows app, Linux and macOS don't today: install the new version by hand. The Doctor's Update feed row says which applies to you.
See Install for where to get each build.
Upgrading an agent
A new Griddler doesn't change your agents by itself. When your Griddler is newer, the agent's card shows · update beside its version. Click Deploy again: the container is replaced with the matching image, and open panes offer ▷ Reconnect. Your sign-ins and session history are kept on the volume.
Where things run
| Piece | Runs on |
|---|---|
| Griddler | Your PC |
| Griddler Social and this site | River Logic's cloud, behind one address |
| Griddler Agent | A dev VM you own, or Docker Desktop on your PC |
| Griddler for iPhone | TestFlight, from its own pipeline |