Build Cache for React Native v0.16.1

Changelog
1

What’s Changed

  • Bump the Bitrise Build Cache CLI to v3.8.1. The generated Gradle init script no longer carries an authToken for the cache and analytics plugins — remote-cache 2.1.0 and gradle-analytics 3.2.3 now resolve their own token by running bitrise-build-cache auth token. That is what lets the Gradle configuration cache work with a rotating per-build JWT: a token baked into the init script is a configuration input, so it invalidated the cache whenever it changed. test-distribution still receives a token.
  • activate gradle now exports BITRISE_BUILD_CACHE_CLI with the CLI’s own path. The plugins look for the CLI only in that variable, on $PATH and in ~/.bitrise/bin, while this step installs it elsewhere — without the export they would find no CLI, and with no token in the init script there would be nothing to fall back on. React Native builds reach this same Gradle path via activate react-native, so they get both changes.
  • No intervening CLI versions: 0.16.0 shipped v3.8.0, so this release picks up v3.8.1 only.
  • Also picks up the Gradle plugin bumps: common 1.0.8, remote-cache 2.1.0, gradle-analytics 3.2.3, test-distribution 2.2.11.