packman reported encountering a confusing “critical update” warning immediately after completing an update, despite the system initially showing no updates available. The version number had lost its “-dev” suffix, though the system appeared to function normally. After revisiting the Admin|Upgrade menu, packman discovered a missing commit from 4 hours prior, applied it, and successfully resolved the warning — returning to version 3.2.0.beta2-dev with a green status icon. RGJ reassured packman that this was not a fault on their part, but rather a rare coincidence of updating just as a new version was released — a roughly 1/1000 chance. packman joked about their luck and thanked RGJ for the quick response. The issue resolved itself without lasting impact, highlighting a transient synchronization quirk during release windows.
Weird. I clicked the upgrade link in the screenshot above which reported no updates needed. Then I posted the message above. After that I went back through the Admin|Upgrade menu option which then reported I was missing a commit from 4 hours ago, even though I’d only updated 10 minutes before. I applied that update and I’m now on 3.2.0.beta2-dev and the critical update warning had returned to a nice green smiley face.
So the problem fixed itself but I don’t understand why things happened the way they did.
Not your fault and nothing to worry about.
You had the (bad/good?) luck that you were updating at the very moment a new version was released. A 1/1000 chance and it happened to you 
Sounds like I should do the lottery this weekend 
Thanks for the quick reply.
