Releasing app updates - livewire caching

I'm periodically releasing updates to my app but my users are experiencing some weird bugs that aren't present on my local version.

Is it possible that the users' browsers are caching the livewire assets, which then causes a conflict when I release an update?

That's my theory - if it's true, is there a way to ensure my users load the latest version of the livewire assets so that when I release an update they get the latest version?