`refreshed` timestamp isn't accurate

I just refreshed my core from candidate (16-2.28.1 (3017)) to beta (16-2.28.5 (3212)) but my refreshed time reads as 2017-10-13 23:07:44 +0100 BST instead of 2017-10-16 18:4x:xx +0100 BST.
Snappy user jhisvail ran into the same bug just now.

i think this timestamp actually marks when the release to the channel your snap is tracking happened on the store side … (it should perhaps be extended to “refreshed (in store):” to make this clearer…

1 Like