Ask HN: How does your company manage browser extension releases?

Our team has been struggling with a good release process for our browser extensions.

With Chrome Extensions, every build needs to be reviewed by the chrome team. This can sometimes take 5-6 days and has never taken less than 24 hours. If a version is published, there is no way to revert to an old version in the event of bugs/issues that make it through the testing cycle.

True CI/CD is out of the question since we have no way to automatically release. Additionally, because of the extension architecture, automated testing is limited almost exclusively to unit level testing the client code.

How has your team overcome this? Any advice welcome here.