LoginSign Up
← Back to all sparks
D

Depot

INFRA · APIS
Velocity6.3

Depot keeps absorbing the CI stack — tests, networking, runners, now its own git host.

ci-cdbuild-accelerationtest-intelligencegit-hostingcli-paritydeveloper-infrastructure
◆Current state
Depot has moved well past build caching. Test results reached general availability in July with org-wide flaky, slow, and recurring failure analytics plus timing-based shard splitting; Sherlock's AI analysis became available on any run rather than only failed ones; and CI jobs can join a Tailscale tailnet to reach private services. The runner fleet now defaults to macOS 26 on M4 hardware, Depot CI understands GitHub stacked pull requests, and Depot Code — a diskless git server backed by blob storage — entered private beta.
◆Where it's heading
The pattern is absorbing each adjacent piece of the pipeline that Depot's position already gives it data about. It runs the builds, so it owns test timing, so it can balance shards; it runs the jobs, so it can diagnose them; it hosts the runners, so it can wire private networking into them. Depot Code extends the same logic upstream to source hosting, which would close the loop between repository and runner. A quieter parallel thread keeps moving SDK- and dashboard-only settings into the CLI, stated explicitly as making projects configurable by agents and scripts.
◆Prediction
Depot Code widening past private beta and binding more tightly to CI is the move the rest of the window sets up. The test work is also positioned to go from reporting to selection — skipping tests a change cannot affect — since Depot now holds the timing and failure history that would require, though the entries stop short of saying so.

◆Recent moves

  1. 9d ago

    macOS 26 is now the default macOS version for GitHub Actions runners

    The depot-macos-latest label now resolves to macOS 26 on M4 runners with 8 CPUs and 24 GB of memory, with explicit labels left for pinning to macOS 15 or 14. Routine fleet maintenance, and the kind of upkeep that has to stay current for the hosted-runner half of the business to be worth using.

  2. 16d ago

    Depot CI now supports native GitHub stacked pull requests

    Depot CI evaluates pull_request.branches against a stack's ultimate base branch and runs matching workflows for each layer using that PR's own merge ref, with stack metadata exposed for expressions. It closes a real compatibility gap for teams working in stacked PRs, and fits the broader effort to make Depot CI a drop-in for GitHub Actions behavior.

  3. 19d ago

    Set cache retention when creating a project with --cache-policy-keep-days

    Cache retention can be set at project creation with --cache-policy-keep-days instead of adjusted afterward through the SDK or dashboard. Small on its own, but it is the same CLI-parity thread as the projects get and update commands from the day before: settings that scripts could not previously reach.

  4. 20d ago

    View and edit project details from the Depot CLI

    depot projects get and depot projects update bring project details and settings that were SDK-only into the CLI, both with JSON output. The stated motivation is letting agents and scripts inspect and configure a project end to end, which makes this a deliberate step toward a machine-drivable control surface rather than a convenience command.

  5. 21d ago

    Test results are now generally available

    ⚡ SPARK

    Test results going GA is the clearest instance of Depot's absorb-the-adjacent-layer pattern, and the timing data it collects is what makes the shard splitting and any future test selection possible. The CLI and stacked-PR work since reads as filling in the surface around a product that now spans build, run, and analyze.

  6. 29d ago

    AI analysis available for all Depot CI workflows and jobs

    Sherlock can now analyze any Depot CI workflow or job from its page, not just runs that failed through the AI diagnosis card. Opening the analysis to slow, passing, and in-progress runs turns a failure triage tool into a general investigation one, on the same data Depot already holds.