Depot CI now caches GitHub Actions

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.

There is nothing to change in your workflow. Existing steps such as uses: actions/checkout@v4 continue to work as written, and Depot CI handles caching automatically.

This is separate from the cache you use for dependencies and build outputs. actions/cache, package-manager caches, and Depot Cache preserve data produced or downloaded by your jobs. This new layer caches the action code needed to start those jobs in the first place.

Faster action setup

Each remote uses: step must be downloaded before it can run. On ephemeral runners, that work is repeated across jobs. Depot CI now caches action source so later jobs can reuse it, reducing repeat downloads and reliance on GitHub during job startup.

The first time an action is used, the job continues through GitHub as usual while Depot prepares the cache for later runs.

Public and private actions

Workflows across repositories in the same GitHub organization can reuse cached private and internal actions. The Depot Code Access GitHub App must have access to the action repository. If access is missing, Depot shows the affected repository and provides a link to update the GitHub App installation.

Public actions are cached automatically.

Existing action references keep working

Action references such as @v4, @main, and full commit SHAs continue to work without changes. To choose exactly which version your workflow runs, pin an action to a full commit SHA.

If an action is not available from the cache, Depot CI downloads it from GitHub. Access to private actions continues to follow your GitHub App permissions.

No workflow changes required

Action caching is automatic for supported GitHub Actions used in Depot CI. Keep writing the same uses: steps:

steps:
  - uses: actions/checkout@v4
  - uses: actions/setup-node@v4
    with:
      node-version: 24
  - run: npm test

If you are new to Depot CI, migrate an existing GitHub Actions workflow or review the GitHub Actions compatibility reference. Your workflow syntax stays the same; action delivery gets a faster, more reliable path underneath it.