Skip to main content

Caching

actions/cache and the tools built on it (setup-node, setup-python, rust-cache, …) work unchanged, with GitHub’s scoping: a push saves to its branch; a pull request saves to itself and reads its own caches, then its base branch’s, then the default branch’s. Caches never cross repositories.
  • By default they are GitHub’s Actions caches of your repository, as on any runner.
  • With Darkbloom’s build cache (enabled per repository by Darkbloom), they are stored encrypted on the Mac that saved them instead, and restore at disk speed. A job placed on another Mac misses, and pull requests from forks get none.
Either way, a Mac that runs a job can write that job’s cache scope: keep cache-saving push jobs that releases depend on off Darkbloom, or have only pull requests approved. A cache saved by a job with zstd is not restored by a runner without it, and the compression is part of a cache’s version. Both Darkbloom images carry zstd, so routed jobs use the same compression GitHub’s runners use.

Network

A job reaches the network over outbound HTTPS only, through Darkbloom’s gateway, and only to hosts on the repository’s list:
  • GitHub’s published Actions hosts (checkout, actions, caches, artifacts, releases);
  • the hosts Darkbloom reviewed for your repository (package registries, model hubs).
No other ports, no IP addresses and no wildcards. A connection to an unlisted host is refused and logged, and the step fails. Tell your Darkbloom contact which hosts beyond GitHub your jobs download from. Darkbloom updates the list and your approval together. The route job itself runs on a GitHub-hosted runner, so it needs none of these hosts.