I wonder if there was a best-practice for releasing a new extension version and making sure no changes would break something for current users who upgrade the extension.
Haven’t maintained my public extension for some years, so I’m not really up-to-date with development procedures.
My attempt would be to create a fresh FF profile, install the current version of my extension, then use web-ext
to run the new version in that profile.
That’s a pretty good approach!
But in any case, the difference between updating addon and simply reloading it is only the runtime.onInstalled
event. So if it works during development, usually it means it will work in production as well.
But if you are doing some data migration, make sure to test it with the real data.
Additionally, right after the release, click “Check for updates” to trigger the update on your PC and test it right away. And if it somehow doesn’t work, simply disable the released version in the “Manage Status & Versions” page. That will stop the update from spreading and new users will be still able to install the previous version.
2 Likes