@nkrishnaswami Looks like it's fixed. All my extensions are working with version 110.0.5130.13, but I had to re-enable affected extensions manually. Not just repair them on the Extensions page (it had no effect), but go to the Chrome store and turn them on there.
But maybe you won't have to do it if you're updating from a version where the extensions are still working.