Repository navigation
A plugin's admin screen could keep running old code for hours after its deploy went green, and only a manual hard refresh fixed it.
Cache-busting stamps every asset URL the build controls, but it walked HTML and admin/*.js only. A plugin's admin module is reached neither way — the admin imports it on demand from the URL in api/site.json — so that URL carried no version, and browsers and CDNs held on to the old copy for the whole of its TTL.
Those URLs now carry the same content hash as every other asset. api/site.json is not cached, so a deploy changes the URL and the new module loads on the next ordinary reload.
Nothing to do beyond merging the update PR. If you write plugins with admin screens, this is worth taking.