Datadog CI Visibility is now generally availableDatadog 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 fait
Datadog CI Visibility is now generally availableDatadog 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…
Added an Ubuntu package mirror for us-east-1 runnersUbuntu 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 ARM6
Added an Ubuntu package mirror for us-east-1 runnersUbuntu 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…
Depot CI supports Arm64 sandboxesDepot 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 testCopy code Sandbox sizes range from 2 CPUs/8 GB up to 64 CPUs/256 GB. See the ful
Depot CI supports Arm64 sandboxesDepot 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 testCopy code 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.
Updated Windows Server runner imagesThe 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. Vi
Updated Windows Server runner imagesThe 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…
Depot CI now continues earlier pull request runs after new commitsDepot 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 trigger
Depot CI now continues earlier pull request runs after new commitsDepot 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.
macOS 26 is now the default macOS version for GitHub Actions runnersThe 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 ca
macOS 26 is now the default macOS version for GitHub Actions runnersThe 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…
Depot CI now supports native GitHub stacked pull requestsDepot 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 me
Depot CI now supports native GitHub stacked pull requestsDepot 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 ex…
Set cache retention when creating a project with --cache-policy-keep-daysdepot projects create now supports a --cache-policy-keep-days flag, so you can set build cache retention at creation time instead of adjusting it afterward. depot projects create my-project --cache-policy-keep-days 30Copy code
Set cache retention when creating a project with --cache-policy-keep-daysdepot projects create now supports a --cache-policy-keep-days flag, so you can set build cache retention at creation time instead of adjusting it afterward. depot projects create my-project --cache-policy-keep-days 30Copy code The default is 14 days, and 0 means no limit. Previously, cache TTL could only be set through the SD…
View and edit project details from the Depot CLIThe Depot CLI now includes depot projects get and depot projects update. The commands provide access to project details and settings that were previously available only through the SDK, so now agents and scripts can inspect and configure a project enti
View and edit project details from the Depot CLIThe Depot CLI now includes depot projects get and depot projects update. The commands provide access to project details and settings that were previously available only through the SDK, so now agents and scripts can inspect and configure a project entirely from the CLI. depot projects get --output jsonCopy code depot projects update --name "name" --c…
Test results are now generally availableTest results are now generally available for Depot CI and GitHub Actions jobs. Ingest JUnit XML from your CI, see pass/fail/error/skip counts on every job, and dig into org-wide analytics for flaky, slow, and recurring failures. What you get: Inline results on
Test results are now generally availableTest results are now generally available for Depot CI and GitHub Actions jobs. Ingest JUnit XML from your CI, see pass/fail/error/skip counts on every job, and dig into org-wide analytics for flaky, slow, and recurring failures. What you get: Inline results on every job: pass/fail/error/skip counts, plus a full results page with filters by status, suite, cla…
AI analysis available for all Depot CI workflows and jobsYou can now ask Sherlock to analyze any Depot CI workflow or job directly from its page, whether or not the run failed. An Analyze workflow button appears on the workflow header, and an Analyze job button appears on the job's log view. Previou
AI analysis available for all Depot CI workflows and jobsYou can now ask Sherlock to analyze any Depot CI workflow or job directly from its page, whether or not the run failed. An Analyze workflow button appears on the workflow header, and an Analyze job button appears on the job's log view. Previously, the only way to hand a run to Sherlock was through the button inside the AI failure diagnosis c…
View the workflow source for runs started from a local fileRuns started from a local workflow file (for example depot ci run --workflow .depot/workflows/ci.yml) now show that workflow's source in the Depot dashboard. You can now inspect the exact uncommitted YAML a run used from the dashboard.
Split CI test suites with historical timing data (beta)Depot can now split a test suite across CI shards using durations from your earlier test reports. Give each shard the same candidate list, and Depot assigns a time-balanced, non-overlapping subset of candidates. Test splitting builds on the test
Split CI test suites with historical timing data (beta)Depot can now split a test suite across CI shards using durations from your earlier test reports. Give each shard the same candidate list, and Depot assigns a time-balanced, non-overlapping subset of candidates. Test splitting builds on the test results beta and reads timing data from the same JUnit reports. No separate setup needed: depot tes…
Split CI test suites with historical timing dataDepot can now split a test suite across CI shards using durations from your earlier test reports. Give each shard the same candidate list, and Depot assigns a time-balanced, non-overlapping subset of candidates. The new depot tests run command runs you
Split CI test suites with historical timing dataDepot can now split a test suite across CI shards using durations from your earlier test reports. Give each shard the same candidate list, and Depot assigns a time-balanced, non-overlapping subset of candidates. The new depot tests run command runs your test command and uploads its JUnit reports in one step. Use it directly from your CI shell or with…
Depot CI now supports TailscaleDepot CI jobs can now join your Tailscale tailnet, so builds and tests can reach private services like internal databases, clusters, and APIs without exposing them to the public internet or maintaining static IP allow lists. Previously, this was available for Depot Git
Depot CI now supports TailscaleDepot CI jobs can now join your Tailscale tailnet, so builds and tests can reach private services like internal databases, clusters, and APIs without exposing them to the public internet or maintaining static IP allow lists. Previously, this was available for Depot GitHub Actions runners and container builders, but CI jobs couldn't reach anything inside your private…
Depot Code is now available in private betaDepot Code, our own source control hosting, is now in private beta. It's a diskless git server backed by blob storage that scales horizontally, mirrors your GitHub repos, and plugs straight into Depot CI. Unlike the traditional hub-and-spoke git model that