Depot
@depot.dev
40x faster Docker builds on 3x faster GitHub Actions runners.
Automatic intelligent caching, blazing-fast compute and zero-configuration ⚡
Automatic intelligent caching, blazing-fast compute and zero-configuration ⚡
Top 5 finishers each direct $1,000 to a registered charity of their choice.
Plus: STEM & developer-focused charities get a 50% boost!
Solve puzzles. Make an impact.
Join here: depot.dev/events/advent-of-code-2025
Plus: STEM & developer-focused charities get a 50% boost!
Solve puzzles. Make an impact.
Join here: depot.dev/events/advent-of-code-2025
November 20, 2025 at 1:26 AM
Top 5 finishers each direct $1,000 to a registered charity of their choice.
Plus: STEM & developer-focused charities get a 50% boost!
Solve puzzles. Make an impact.
Join here: depot.dev/events/advent-of-code-2025
Plus: STEM & developer-focused charities get a 50% boost!
Solve puzzles. Make an impact.
Join here: depot.dev/events/advent-of-code-2025
Full breakdown with solutions: depot.dev/blog/trouble...
November 14, 2025 at 7:37 PM
Full breakdown with solutions: depot.dev/blog/trouble...
Dependabot secrets not working
Regular workflow secrets worked fine, but Dependabot workflows failed to access private registries on self-hosted runners.
The reason: Dependabot runs in a restricted security context and needs its own secrets.
Regular workflow secrets worked fine, but Dependabot workflows failed to access private registries on self-hosted runners.
The reason: Dependabot runs in a restricted security context and needs its own secrets.
November 14, 2025 at 7:37 PM
Dependabot secrets not working
Regular workflow secrets worked fine, but Dependabot workflows failed to access private registries on self-hosted runners.
The reason: Dependabot runs in a restricted security context and needs its own secrets.
Regular workflow secrets worked fine, but Dependabot workflows failed to access private registries on self-hosted runners.
The reason: Dependabot runs in a restricted security context and needs its own secrets.
Azure CLI authentication failures
azure/login worked great on GitHub-hosted runners but failed on self-hosted with "DefaultAzureCredential: failed to acquire a token."
Why? GitHub's runners have managed identities. Self-hosted don't. The solution: explicitly provide credentials
azure/login worked great on GitHub-hosted runners but failed on self-hosted with "DefaultAzureCredential: failed to acquire a token."
Why? GitHub's runners have managed identities. Self-hosted don't. The solution: explicitly provide credentials
November 14, 2025 at 7:37 PM
Azure CLI authentication failures
azure/login worked great on GitHub-hosted runners but failed on self-hosted with "DefaultAzureCredential: failed to acquire a token."
Why? GitHub's runners have managed identities. Self-hosted don't. The solution: explicitly provide credentials
azure/login worked great on GitHub-hosted runners but failed on self-hosted with "DefaultAzureCredential: failed to acquire a token."
Why? GitHub's runners have managed identities. Self-hosted don't. The solution: explicitly provide credentials
A customer's runner was idle and ready, but jobs kept timing out. The culprit?
GitHub's "Selected workflows" filter was blocking jobs from pull requests because refs didn't match.
The error said "waiting for runner" when it was really a permissions issue.
GitHub's "Selected workflows" filter was blocking jobs from pull requests because refs didn't match.
The error said "waiting for runner" when it was really a permissions issue.
November 14, 2025 at 7:37 PM
A customer's runner was idle and ready, but jobs kept timing out. The culprit?
GitHub's "Selected workflows" filter was blocking jobs from pull requests because refs didn't match.
The error said "waiting for runner" when it was really a permissions issue.
GitHub's "Selected workflows" filter was blocking jobs from pull requests because refs didn't match.
The error said "waiting for runner" when it was really a permissions issue.