What’s Changed
- Bump the Bitrise Build Cache CLI to v3.8.4.
- Activation now persists the credential it resolves, so the Gradle plugins can still authenticate when the build runs in a later step. Since v3.8.1 the plugins resolve their own token by running the CLI mid-build instead of reading one from the init script; on CI where the credential is scoped to the activation step — the usual shape on GitHub Actions — the build had no token to find and analytics uploads were rejected with
Unauthenticated. Builds on Bitrise were unaffected, because the per-build JWT is present in every step.