chore(ci): migrate workflows to depot runners - #435
Conversation
Greptile SummaryThis PR migrates all GitHub Actions jobs to Depot runner labels, selecting larger runner variants for compile-heavy jobs and preserving the existing build, test, documentation, review, and publishing steps.
Confidence Score: 4/5The PR appears safe to merge, with only non-blocking stale runner documentation in the Rust workflows. The workflow behavior is consistently migrated to Depot labels, while two Rust setup comments still describe a GitHub-hosted image assumption and should be updated to match the new runner contract. Files Needing Attention: .github/workflows/build-check-test.yml, .github/workflows/latest-deps-test.yml Important Files Changed
Prompt To Fix All With AI### Issue 1
.github/workflows/build-check-test.yml:19
**Stale runner toolchain contract**
The migrated Rust jobs still explain their direct `rustup` calls as a GitHub-hosted-runner guarantee, even though they now run on Depot images. Update these comments and document or explicitly provision the Depot toolchain contract so future runner-image changes do not produce misleading missing-tool failures.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.Reviews (1): Last reviewed commit: "chore(ci): migrate workflows to depot ru..." | Re-trigger Greptile |
| matrix: | ||
| os: [ubuntu-latest, windows-latest, macos-latest] | ||
| os: [depot-ubuntu-latest-4, depot-windows-2022-4, depot-macos-latest] | ||
| python-version: ["3.10", "3.11", "3.12", "3.13", "3.14"] |
There was a problem hiding this comment.
Stale runner toolchain contract
The migrated Rust jobs still explain their direct rustup calls as a GitHub-hosted-runner guarantee, even though they now run on Depot images. Update these comments and document or explicitly provision the Depot toolchain contract so future runner-image changes do not produce misleading missing-tool failures.
Prompt To Fix With AI
This is a comment left during a code review.
Path: .github/workflows/build-check-test.yml
Line: 19
Comment:
**Stale runner toolchain contract**
The migrated Rust jobs still explain their direct `rustup` calls as a GitHub-hosted-runner guarantee, even though they now run on Depot images. Update these comments and document or explicitly provision the Depot toolchain contract so future runner-image changes do not produce misleading missing-tool failures.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
| matrix: | ||
| os: [ubuntu-latest, windows-latest, macos-latest] | ||
| python-version: ["3.10", "3.11", "3.12", "3.13", "3.14"] | ||
| os: [depot-ubuntu-latest-4, depot-windows-2022-4, depot-macos-latest] |
There was a problem hiding this comment.
Depot has depot-windows-latest (now 2025). Is 2022 pinned intentionally?
Closes #434.
Swaps every
runs-onin.github/workflows/from GitHub-hosted to Depot runners:depot-ubuntu-latestfor light jobs,depot-ubuntu-latest-4/depot-windows-2022-4for compile-heavy jobs (matching GitHub's 4-vCPU standard runners),depot-macos-latest(arm64, same as GitHub'smacos-latest) for macOS.Before merging:
nominal-ioorg (Depot dashboard -> GitHub Actions runners), or every job will queue forever.check-and-test (ubuntu-latest, 3.12)->check-and-test (depot-ubuntu-latest-4, 3.12).Notes:
id-token: write.eip-wheel-*artifact names embedmatrix.osand therefore change; theeip-*download pattern inpublish-eipstill matches.