Caching issues wouldn't usually happen because we update the JS cache buster with each upgrade. Unless you spotted this in the Admin CP before the upgrade happened...
Although I do see some odd attributes in your HTML source in that screenshot, so I wonder if there's some sort of caching / CDN layer involved?
Either way, can you remember what you were doing at the time?