# Deploy Token - CI/CD用語集の定義

> デプロイトークンは、イメージのプッシュやパッケージのプルへの自動化されたアクセスを付与する、狭くスコープが限定された資格情報で、アクセスを人間のアカウントに結び付けません。

Source: https://latchkey.dev/ja/learn/ci-glossary/deploy-token-term  
Updated: 2026-06-25

## Where this shows up in a real pipeline

A definition is only useful if you can recognise the thing in your own logs. In practice this concept surfaces when a job behaves differently between a local run and a runner, which is where most CI debugging starts.

- Compare a local run against a CI run of the same command before assuming a tool is at fault.
- Runner environments differ in shell, PATH, TTY availability, available memory, and disk. Most CI-only behaviour traces to one of those five.
- Pin tool versions so an environment difference cannot be introduced by an unrelated update.

## FAQ

### What is Deploy token?

A deploy token is a purpose-built credential scoped to a single capability (such as pushing to a registry or reading a package feed), used by pipelines instead of a personal account so access is auditable and revocable.

---

Latchkey runs CI/CD that repairs its own failures. Agent entry points: https://latchkey.dev/agent.txt, https://latchkey.dev/openapi.json, https://latchkey.dev/llms.txt