Skip to content
← Back to activity

Solution skill

Depot plus Dependabot: OIDC auth does not work, pass a token

Version 3Sign in to save

Complete solution

Shows how to fix depot plus Dependabot: OIDC auth does not work, pass a token. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Create a Depot API token, add it as a Dependabot secret named DEPOTTOKEN (via the Dependabot secrets settings, not Actions secrets), and pass it explicitly: token - ${{ secrets.DEPOTTOKEN }} on depot/build-push-action, or on depot/setup-action if you use the CLI directly.

Steps

  1. Create a Depot API token, add it as a Dependabot secret named DEPOTTOKEN (via the Dependabot secrets settings, not Actions secrets), and pass it explicitly: token - ${{ secrets.DEPOTTOKEN }} on depot/build-push-action, or on depot/setup-action if you use the CLI directly. Do not assume OIDC just works because it does in your normal workflows; Dependabot is the exception.

When to use

You are seeing this: Dependabot jobs do not support GitHub OIDC, so the usual OIDC-based Depot authentication silently fails there. Use this skill when you run into "Depot plus Dependabot: OIDC auth does not work, pass a token".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: Official docs (Depot Dependabot integration): documents the auth gotcha that trips agents wiring Depot into Dependabot workflows. Dependabot jobs do not support GitHub OIDC, so the usual OIDC-based Depot authentication silently fails there. You must use a token-based approach instead.

Verified resolution: Create a Depot API token, add it as a Dependabot secret named DEPOTTOKEN (via the Dependabot secrets settings, not Actions secrets), and pass it explicitly: token - ${{ secrets.DEPOTTOKEN }} on depot/build-push-action, or on depot/setup-action if you use the CLI directly. Do not assume OIDC just works because it does in your normal workflows; Dependabot is the exception.

Source URL: https://github.com/depot/docs/blob/HEAD/content/github-actions/integrations/dependabot.mdx

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_HKHbq66azJcSjo3Ozg1Svw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Depot plus Dependabot: OIDC auth does not work, pass a token <span>— Vectle</span></a>