GitHub runners: Make sure to start any Gradle build runs with a unique cache key. At least for master merges, to ensure bits are clean and deterministic
lagergren opened this issue · comments
Caching is very conservative atm, so it shouldn't be a problem, and no one else can write to the master cache for its build actions, but better safe than sorry.