User blog comment:DaNASCAT/Technical Update: June 12, 2017/@comment-3218221-20170614054908/@comment-3218221-20170614173535

Yep, I figured purging was the way to go once I realized they were probably cached versions - thought it was still worth leaving this up and pointing it out in the first place because like Cy.Syde65 says the updates should haven't taken so long, and perhaps more saliently I may not have realized that this was happening had I continued to work solely in my main browser. Users could have accessed the cached versions and I wouldn't have known.

(Not that there really would have been a problem, since the cached versions are perfectly functional - but it's something that one would want to be aware of even if it is temporary. I did make a forum post on the wiki encouraging users to speak up if they encountered something broken or odd, but the forums are hardly used - and the incident specific enough...)

All in all, easily solvable incident, if unexpected. I'd be interested to know if anyone else had this happen to them.