we have test results in beta inside of Depot now and it's really cool to see the big uptick in people trying it out.
check it out here 👉
If agents write the code, they have to be able to drive CI too. Depot CI has a typed API: trigger, retry, and cancel runs, pull logs and metrics, read failure diagnoses. You, your scripts, and your agents read the same contract. depot.dev/docs/api/ci/re…- Nominal builds the data supply chain for hardware engineering: cars, rockets, energy systems. Their builds on Depot: Windows linking: 8 min → 30 sec Docker builds: 12 min → 4 min Merge to live: ~10 min How @Nominal_io did it:
- Replying to @depotdev4/ Kernel hardening, sorted by what it actually costs you: A. Free housekeeping (`kernel.dmesg_restrict=1`, `fs.suid_dumpable=0`) B. Nearly free: prune and lock kernel modules C. Costs visibility: `ptrace`, eBPF D. Costs performance E. Costs real money: SMT, `io_uring`5/ It's not a checklist. Know your threat model, document the trade-offs, don't start a Paranoiafest. "A turned-off computer buried in the forest is extremely secure, but won't serve customers."
- macOS 26 (Tahoe) is now on Depot GitHub Actions runners. Change one line, `runs-on: depot-macos-26`, and you're on Apple M4 with Xcode 26 and the macOS 26 SDKs preinstalled. Simulators baked in too, no per-run downloads.
- Already have the Depot CLI? You already have this. Update and go: `depot ci run list` `depot ci diagnose --run <id>`
- Depot reposted
Just three weeks until Startup School Paris! Looking forward to discussing the future of dev tools with @kylegalbraith of @depotdev.
