Jacques_Pienaar:

So updating affects a user that is pulling frequently for some reason, but not quickly enough to get enough cache reuse


I think It will affect external contributors that have more then one waiting PR for a review or when they need to rebase as we have conflict against master.
These two cases really depend on how fast our review process is vs the number of bumps and the internal “direct commit/copybara” activities.
Also it will affect when I contribute a new PR e.g. just a week or few days later to the last merged one.
Then, but this a  separated topic, it is also about what we are asking to the external contributor to execute a clean room build to populate the first cache and how to manage the garbage collection for the --disk_cache as It is currently unmaneged in bazel specially if we are growing too fast on the disk size with these bumps.