From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

there are different things and I think you're referring to the build script classpath, not specifically the build cache.

if you update a _version_ or _dependency coordinates_ in the toml file, the generated accessors will be identical, so the classpath is going to be the same

however, depending on the tasks, some might be out of date, so _not cached_, simply because you upgraded a dependency that is used as an input

if you change an alias name, or add an entry, then the classpath is invalidated and it would behave more or less like a buildsrc change.

Thanks for comprehensive answer!

Yes, I'm referring to the build script classpath.
Adding or removing new entry is the only problem I have with custom solution I've came up with.

All build cache is lost on every change in buildSrc, because build script classpath was changed. Essentially causing a clean build.

I had a hope, that Version Catalog somehow deals with this problem.

P.S. By "build cache" I mean not Gradle Build Cache, maybe it's called project cache (/build).