Changelog

Depot CI now caches the source code for GitHub Actions in Depot Code, so repeat jobs can load actions from Depot's infrastructure instead of downloading them from GitHub again. Caching is automatic and requires no workflow changes.

This cache is separate from actions/cache, package-manager caches, and Depot Cache, which preserve dependencies and build outputs. Public actions are cached automatically; private and internal actions can be reused across repositories in the same GitHub organization when the Depot Code Access GitHub App has access. Read the launch post for details.

You can now export GitHub Actions analytics as CSV or JSON from the Depot dashboard. Open the GitHub Actions Analytics page and use Export next to Insights to download a ZIP containing a separate file for each analytics table.

Exports follow your selected timeframe and filters, including overview comparisons, job duration and failure trends, daily activity, and CPU and memory metrics. Reporting periods and active filters are included in the download, so you can share the current view with your team or analyze the data in your own tools.

Depot CI now collects job summary outputs on the workflow run page.

You can review GITHUB_STEP_SUMMARY content from jobs across the run without opening each job separately. The workflow summary keeps outputs grouped by job for easier scanning.

The Container Builds Projects page and each project's build history now use sortable tables with column filters.

You can now filter build history by status, build or machine, initiator, platform, builder hardware, and start date. Table headings and pagination controls also remain visible while you scroll.

Datadog CI Visibility for Depot CI is out of private beta and available to every organization.

Once enabled, every Depot CI workflow run is sent to Datadog CI Visibility as a pipeline, with its jobs, steps, retries, and partial retries represented faithfully, so you can monitor Depot CI pipeline health alongside the rest of your pipelines.

To enable it, go to organization settings, turn on Send CI runs to Datadog under Datadog CI Visibility, and add a DD_API_KEY CI secret with your Datadog API key. See the Datadog CI Visibility docs for repo-scoped keys and non-US Datadog sites.

Depot CI can now run jobs on Arm64 sandboxes. Use an -arm label in runs-on. For example:

jobs:
  build:
    runs-on: depot-ubuntu-24.04-arm-8
    steps:
      - uses: actions/checkout@v4
      - run: make test

Sandbox sizes range from 2 CPUs/8 GB up to 64 CPUs/256 GB. See the full label list and pricing in Depot CI sandboxes.

Ubuntu runners in us-east-1 now use Depot’s private mirror for Ubuntu packages and repository metadata.

The mirror is synchronized every six hours from Ubuntu’s official Archive and Ports rsync services. It contains packages for both AMD64 and ARM64 runners.

The mirror is currently available only to runners in us-east-1. Runners in other regions continue to use their existing Ubuntu package sources.

The Windows Server 2022 and Windows Server 2025 images for GitHub Actions runners have been rebuilt from fresh AMIs.

The Windows Server 2025 image now includes Visual Studio 2026 instead of Visual Studio 2022, along with MSBuild 18 and supported .NET 10 builds. Visual Studio is installed at C:\Program Files\Microsoft Visual Studio\18\Enterprise.

We didn't change the Windows Server 2022 image source. However, with any fresh rebuild Windows Update and package versions may have changed over time.

Depot CI now keeps GitHub checks accurate when duplicate pull request events create multiple runs for the same commit.

Previously, a cancelled duplicate run could overwrite the result of a successful run, leaving the required check stuck as cancelled and blocking merges. The successful result now remains authoritative.

Test results uploaded from Depot GitHub Actions runners now include their source branch and commit SHA. Learn how to report and view GitHub Actions test results.

The Test Results Analytics page can now filter GitHub Actions results by branch and include them in flaky-test analysis. Job details also show the source. The new metadata applies to results uploaded after this release.

Depot CI no longer automatically cancels running pull_request workflow runs when a new commit is pushed to the same pull request. Running workflows now continue by default.

To cancel older running workflows when a newer run is triggered, configure a workflow concurrency group with cancel-in-progress: true.

Depot Cache now fetches blobs in parallel when Moonrepo restores cached tasks.

Large Moonrepo workspaces with blob-heavy caches can now restore faster without configuration changes. Learn how to configure Moonrepo to use Depot Cache.

Depot CI now integrates directly with Origin, Cursor's code hosting platform, during its early beta. You can connect Depot to an Origin namespace and run your existing GitHub Actions workflows without GitHub.

Pushes and pull requests in Origin trigger Depot CI runs, and CI results appear as status checks on Origin pull requests. Read the launch post for setup instructions and integration details.

Depot CI now assigns an increasing run number to each workflow file. The value is available through github.run_number, GITHUB_RUN_NUMBER, and OIDC claims.

Previously, every workflow reported a run number of 1. Separate runs now produce distinct values, so workflows can safely use the run number in artifact paths, reports, and external records.

Depot CI now supports GitHub Actions wildcard projections in runtime expressions. You can use expressions such as labels.*.name in step conditions, environment variables, and action inputs.

- name: Run for approved pull requests
  if: contains(github.event.pull_request.labels.*.name, 'approved')
  run: ./ci.sh

Previously, projections across arrays returned an empty value at runtime. They now match the behavior of GitHub Actions and Depot CI's compile-time expressions.

The Depot CI Runs page can now show runs for a specific workflow file across all branches.

Select a workflow to review its run history without searching by individual run IDs. The filter identifies the workflow by its repository and file path. See the Depot CI logs guide for other run filters.

After you select a repository, the Depot CI Workflows tab now shows the latest run status for each workflow file that has run.

Previously, frequently running workflows could crowd other workflow files out of the recent activity window, leaving their latest status blank. Each workflow now loads its own latest run.

The depot-macos-latest label now runs with macOS 26 (Tahoe) by default, giving you access to the latest Apple development tools and SDKs for your GitHub Actions workflows.

If you need to pin a job to a specific macOS version, you can use:

• depot-macos-26 for macOS 26 (Tahoe)
• depot-macos-15 for macOS 15 (Sequoia)
• depot-macos-14 for macOS 14 (Sonoma)

The macOS 26 runner type uses M4 chips with 8 CPUs, 24 GB of memory, and our disk accelerator for faster I/O operations.

Depot CI now supports GitHub's code-quality token permission for workflows that submit code quality and coverage results to GitHub.

Request the permission explicitly in your workflow:

permissions:
  contents: read
  code-quality: write

The permission isn't included in read-all or write-all. Existing Depot Code Access app installations in GitHub may need approval for the new permission. See the Depot CI permissions reference for details.

Depot CI now supports native GitHub stacked pull requests for pull_request workflows. Depot CI evaluates pull_request.branches against a stack's ultimate base branch, then runs matching workflows for each layer using that pull request's own merge ref.

Stack metadata is available through github.event.pull_request.stack when you need it for expressions. See the Depot CI compatibility reference for the supported behavior and examples.