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…
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…
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
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 welds storage and compute together, Depot Code stores git packfiles and their indexes as objects on…
Depot CI and Sandboxes now run on Depot MetalDepot Metal, the next generation of our compute and storage platform, is now live. Depot CI workloads and Depot Sandboxes are already running up to 50% faster on Depot Metal, according to our initial benchmarks. There's nothing to configure and no migrati
Depot CI and Sandboxes now run on Depot MetalDepot Metal, the next generation of our compute and storage platform, is now live. Depot CI workloads and Depot Sandboxes are already running up to 50% faster on Depot Metal, according to our initial benchmarks. There's nothing to configure and no migration on your end: you get the faster performance at no additional cost. Depot Metal runs microVMs on b…
GitLab CI OIDC trust relationshipsDepot now supports OIDC trust relationships for GitLab CI. You can configure a Depot project to trust a GitLab namespace and project, then use GitLab's short-lived ID tokens to authenticate depot build without storing a static Depot token in CI variables. In your Gi
GitLab CI OIDC trust relationshipsDepot now supports OIDC trust relationships for GitLab CI. You can configure a Depot project to trust a GitLab namespace and project, then use GitLab's short-lived ID tokens to authenticate depot build without storing a static Depot token in CI variables. In your GitLab job, request an ID token named DEPOT_OIDC_TOKEN with aud: https://depot.dev; the Depot CLI will…
Datadog CI Visibility for Depot CI in private betaDepot CI runs can now be sent to Datadog CI Visibility, so you can monitor Depot CI pipeline health alongside the rest of your pipelines. Each workflow run becomes a Datadog pipeline, its jobs become jobs, and their steps become steps, with retries a
Datadog CI Visibility for Depot CI in private betaDepot CI runs can now be sent to Datadog CI Visibility, so you can monitor Depot CI pipeline health alongside the rest of your pipelines. Each workflow run becomes a Datadog pipeline, its jobs become jobs, and their steps become steps, with retries and partial retries represented faithfully. This feature in private beta. Reach out to support to req…
New Depot CI triggers: repository_dispatch, pull_request_review, and deployment_statusDepot CI now supports three more GitHub Actions triggers that were previously unsupported: repository_dispatch — start a workflow from an external system (like a Vercel deployment) through the GitHub API, with no p
New Depot CI triggers: repository_dispatch, pull_request_review, and deployment_statusDepot CI now supports three more GitHub Actions triggers that were previously unsupported: repository_dispatch — start a workflow from an external system (like a Vercel deployment) through the GitHub API, with no polling or relay of your own. Filter by event type with types, and read the dispatch's action and cli…
Follow live logs when you start a Depot CI rundepot ci run now supports a --follow (-f) flag that starts the run and immediately streams its logs, so you no longer need a separate depot ci logs --follow call after triggering. depot ci run --workflow .depot/workflows/ci.yml --followCopy code When you
Follow live logs when you start a Depot CI rundepot ci run now supports a --follow (-f) flag that starts the run and immediately streams its logs, so you no longer need a separate depot ci logs --follow call after triggering. depot ci run --workflow .depot/workflows/ci.yml --followCopy code When you request a single --job, the command follows that job's logs. Otherwise it selects the job automatic…
Snapshot enhancements for Depot CISnapshots in Depot CI let you bake setup steps into a reusable custom image, so later jobs start from a prepared environment instead of repeating the same work. This release brings a few improvements. Persist environment variables: Snapshots now persist non-sensitiv
Snapshot enhancements for Depot CISnapshots in Depot CI let you bake setup steps into a reusable custom image, so later jobs start from a prepared environment instead of repeating the same work. This release brings a few improvements. Persist environment variables: Snapshots now persist non-sensitive environment variables, so configuration you set during the snapshot job is there when later jobs r…
Depot CI now supports issue comment triggersDepot CI now supports GitHub Actions workflows that use on.issue_comment, including comments on issues and pull requests. This makes ChatOps and branch-deploy workflows easier to move from GitHub Actions to Depot CI without rewriting the trigger. Depot CI
Depot CI now supports issue comment triggersDepot CI now supports GitHub Actions workflows that use on.issue_comment, including comments on issues and pull requests. This makes ChatOps and branch-deploy workflows easier to move from GitHub Actions to Depot CI without rewriting the trigger. Depot CI supports the created, edited, and deleted activity types, and workflows can use github.event.issue.p…
SOCI v2 support for Depot container buildsDepot container builds now support SOCI (Seekable OCI) v2. With a compatible runtime, containers start after downloading only the files they need instead of pulling the entire image first, cutting startup time for large images like CUDA or PyTorch. Depot gen
SOCI v2 support for Depot container buildsDepot container builds now support SOCI (Seekable OCI) v2. With a compatible runtime, containers start after downloading only the files they need instead of pulling the entire image first, cutting startup time for large images like CUDA or PyTorch. Depot generates the SOCI v2 index at build time, so there's no separate post-push indexing pipeline. SOCI is…