hey folks, does the remote cache takes into consideration which gradle version was used to generate a cache entry? The context is that I'm planning to do a minor upgrade in our gradle wrapper but I'm unsure about the impact on the remote cache once the upgrade has been merged.

I hope so! Well, the wrapper should not affect the cache, but I guess you did not mean updating the wrapper (the jar checked into VCS) but the Gradle version the wrapper uses to run your build, defined in the wrapper properties. A different Gradle version could behave differently and produce a different result, like a fixed implementation of some logic. The Gradle jars should be part of the classpath of the task and the classpath should be part of the cache key. So if that minor Gradle update does not change the classpath, the cache key might be the same, but I'd say that's rather unlikely. But simply enable cache debugging, then you see exactly how and from what information the cache key is built, then you can compare.

great, thanks for the input @Vampire!