Chromium versions

holtdroid-chromium-sync is a separate job (job: chromium in the chart deploy/helm/holtdroid-sync). It copies Chromium browser builds, one per milestone, into a folder or S3 prefix, which Holtdroid lists as a read-only source. Launch one like any other build to open a page in that browser version.

Where the builds come from

Chromium’s x86_64 snapshot builds in the public chromium-browser-snapshots bucket, the same ones the WebView catalog uses: ChromePublic.apk, Chromium as org.chromium.chrome, one APK with no splits. It is Chromium, not Google Chrome, so Google sign-in, sync and Play services features are missing. Builds go back to Chromium 129 (mid-2024), about 420 MB each.

Which milestones

Not all of them: the job keeps many recent milestones and fewer older ones. Counting the available milestones newest first, it keeps:

• the milestones on Android’s Stable, Beta, Dev and Canary channels;
• the newest milestones.latest (default 10);
• every milestone divisible by milestones.every (default 2);
• past the newest milestones.older.after (default 24), only milestones divisible by milestones.older.every (default 5) instead;
• milestones.extra.

In October 2026 the defaults pick 149–158, the even milestones 136–148 and 130: 18 builds, about 7.5 GB. Builds that stop matching as new milestones come out are deleted, but only after a pass in which Chromium Dash and the bucket answered. Each build is the milestone’s last Canary, give or take a few commits, and the current Canary milestone moves with every new Canary release.

Each build is chromium-{milestone}.apk with a sidecar: the title Chromium {milestone}, the version and snapshot revision as the note, and the tags milestone, version, channel, revision, minSdk, targetSdk, requiresSdk and frontend. Chromium 149 to 156 are tagged requiresSdk: 34: they abort at startup on Android 11 to 13. Chromium 157 and later are tagged requiresSdk: 35, see below. The launch dialog greys out the Android versions below requiresSdk, offering the newest Chromium that runs there instead, and the api refuses them.

Deploying

job: chromium
existingSecret: holtdroid-chromium-sync # S3_ACCESS_KEY, S3_SECRET_KEY
tmpSize: 2Gi # one unpacked APK at a time
config:
  interval: 6h
  target:
    type: s3
    s3:
      endpoint: https://s3.example.com
      bucket: holtdroid
      prefix: chromium
      accessKey: env:S3_ACCESS_KEY
      secretKey: env:S3_SECRET_KEY

And the source in Holtdroid:

sources:
  - name: chromium
    type: s3
    readOnly: true
    s3:
      endpoint: https://s3.example.com
      bucket: holtdroid
      prefix: chromium
      accessKey: env:S3_ACCESS_KEY
      secretKey: env:S3_SECRET_KEY

The job needs outbound HTTPS to chromiumdash.appspot.com and storage.googleapis.com. Every option is in the job’s docs.

Notes

• Snapshot builds report no DevTools frontend of their own. Holtdroid passes the build’s frontend tag (the milestone’s Canary commit) to the session, so the DevTools panel opens the browser’s tabs with that frontend. It can differ from the build by a few commits.
• Sessions skip Chrome’s welcome screens (--disable-fre in chrome-command-line) and make the browser the default one, so links from other apps open in it. Runtime permissions are granted at install.
• Two builds of the same package can’t be installed side by side: to compare milestones, start one session per milestone.
• Chromium 157 and later draw only through Vulkan 1.3 features. The Android 15 image of holtdroid-redroid ships newer Mesa Vulkan drivers for that; on Android 11 to 14 these builds abort with “GPU process isn’t usable”, hence requiresSdk: 35. Chromium 148 and older run on every version.