# Build Cache for React Native v0.14.8

**URL:** <https://discuss.bitrise.io/t/build-cache-for-react-native-v0-14-8/26218>\
**Category:** Changelog\
**Tags:** step-update\
**Created:** [September 1, 2026, 10:13am UTC](https://discuss.bitrise.io/t/build-cache-for-react-native-v0-14-8/26218 "2026-09-01T10:13:18Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/d/d901cf2aad020f2dd11918afc89ec2089bb87b35.png) [@system](https://discuss.bitrise.io/u/system)\
**Post date:** [September 1, 2026, 10:13am UTC](https://discuss.bitrise.io/t/build-cache-for-react-native-v0-14-8/26218/1 "2026-09-01T10:13:18Z")

</div>

## What’s Changed

- Bump the Bitrise Build Cache CLI to v3.6.8, which stops installing the supervised daemon on CI. v3.6.7 had re-enabled it; the cache timeouts it was meant to fix did not recur, but build durations rose, so CI builds get the wrapper-forked proxy back.
- Cache operation failures now report channel-pool occupancy and queue wait, so a saturated pool can be told apart from a slow backend. With `--debug` the client also samples pool and process contention every 30s.
- The kv channel floor is raised from 2 to 4; the previous formula gave two channels on anything under 12 cores.

> **[Release 0.14.8 · bitrise-steplib/bitrise-step-activate-react-native-features](https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features/releases/0.14.8)**
>
> What's Changed
> 
> Bump the Bitrise Build Cache CLI to v3.6.8, which stops installing the supervised daemon on CI. v3.6.7 had re-enabled it; the cache timeouts it was meant to fix did not recur, but b...