The issue is on the client side is the thing. I don't know exactly what happens under the hood, but client and UI scripts get saved to a user's browser, so any updates we've made to those script are ignored.

Our best solution right now is just telling users to clear their browser caches whenever we deploy a patch, but that's not ideal because some folks might miss the email, etc.

One potential solution I've considered is having a UI or client script that runs independently that refreshes the browser cache, but I'm not sure if there's a standard call to do that. I suppose there's something built into javascript that could refresh a browser cache.