Fixed
- A newly added device could pass a check for updates and still not be selectable or queueable. On the Upgrades page you would run Check for Updates, press Select Upgradable, and nothing would tick — and the device could not be added to the queue either. The row often claimed the device was up to date. It worked only if you opened that one device's page and checked it from there, which is no way to prepare a fleet. The check was storing the newly found version but not the version the device is actually running, so until the background poller happened to reach that device — which can be a minute after you add it, and later still on a large installation — nothing on the page had two versions to compare. The check now stores both, and a row with nothing to compare says Unknown instead of claiming the device is current.
- The queue's "Add all needing update" could disagree with the table in front of it. It was counting the fleet as it stood when you opened the page, so a device the check had just found to be behind was not included until you reloaded. It now follows the check, as does the "N of M devices behind" line at the top.
- A device running a version newer than the one it last heard about was offered an upgrade that leads backwards. This was corrected on the Upgrades page in 1.77.0; the device page and the update-check results were still comparing versions the old way and could show an
Update →button pointing at an older release.