did something change around buildscript dependencies in 8.6? i thought all plugins declared in settings.gradle pluginManagement are added to the root buildscript classpath, and subproject buildscript classpaths will always get those versions even if they declare something different. but now i am seeing plugins that are declared in settings, but only used in a subproject are not having ther dependencies resolved in the root buildscript classpath

no, that's unchanged.

pluginManagement

doesn't add to the root buildscript classpath, it sets up how plugin IDs would be resolved when used

hmm ok thanks.

I wonder if this could be related to https://issuetracker.google.com/issues/330202433, wherein Gradle 8.6+ and Android Gradle Plugin 8.3 mostly work, but result in a super subtle failure to pull in Guava correctly, breaking app bundles. I was finally able to work around this yesterday by writing a settings plugin that does nothing but add a dependency on the correct version of guava.

Interesting. Im not using agp, but it seems like a similar problem