Let me know if anyone knows how to simulate updating the extension's version. I have tried using the reload button in about:debugging but that just closes the extension even though I am listening to onUpdateAvailable. Updating the package.json did not work either.

I don't have a PC available to check, but I think the onMount call is erroring, which is why e2e is failing.

runtime.onUpdateAvailable isn't available for content scripts so I would guess it isn't available for pages too.

I don't have a PC available to check, but I think the onMount call is erroring, which is why e2e is failing.

runtime.onUpdateAvailable isn't available for content scripts so I would guess it isn't available for pages too.

Where does it say that onUpdateAvailable isn't there for content scripts? I am able to console.log chrome.runtime.onUpdateAvailable from the page.

https://developer.chrome.com/docs/extensions/mv3/content_scripts/

Who knows if it's different for extension pages, usually it isn't ¯\_(ツ)_/¯

Moving to draft as this is low priority and high effort so we can figure it out later, perhaps during the mv3 rework.