Skip to main content

Docs changelog

Subscribe to RSS

This page tracks documentation updates: new guides, updated procedures, and changes reflecting new or updated Bitrise features.

2026 Q4Click to copy link​

No updates match the current filters in this quarter.

2026 Q3Click to copy link​

Build Hub runners need no Build Cache tokenClick to copy link​

On Bitrise Build Hub runners, the Build Cache CLI authenticates itself because the machine is already connected to your workspace. This needs Bitrise Build Cache CLI v3.10.0 or newer. See Getting started with the Build Cache.

Clarified runs-on label matching for Build Hub GitHub Actions poolsClick to copy link​

The docs now spell out that a machine pool must have every label listed in a job's runs-on array, not just one of them, with a worked example. See Configuring your GitHub Actions workflow.

Linux tooling steps scoped to the Docker-based imageClick to copy link​

The tooling-access steps for Build Hub Linux machines apply only to the deprecated Docker-based image. If you use linux-bitvirt-2026, you can skip them. See Configuring your GitHub Actions workflow.

2026 Q2Click to copy link​

Build Hub: Gradle dependency mirroring explainedClick to copy link​

The Build Hub documentation now includes an explanation of how Gradle dependency mirroring works, giving you a clearer picture of caching behaviour for Gradle projects running on Build Hub.

2026 Q1Click to copy link​

No updates match the current filters in this quarter.

<head> <meta name="robots" content="noindex, follow" /> </head>