#89792 was caused by a change to a platform interface package that caused analysis warnings—which are fatal in flutter/plugins CI—in the dependent packages in the plugin group. This wasn't caught because while we do a path-based build of all plugins via the all_plugins check, analysis is done on a per-package basis, so is using the published dependencies, not the in-tree dependencies. In order to prevent this from happening in the future we need to change the way analysis is run.

I think we'll need to build tooling that can adjust all the repository's dependencies on platform interfaces that have changed but don't have breaking version changes, then re-analyze after running that. (I looked at Melos, but it doesn't allow the kind of precise targeting that we want here.)