Dependabot "unknown package manager" in dependabot.yml in CI

Dependabot validates package-ecosystem against a fixed list of supported managers. A misspelling or an unsupported value fails schema validation, and the whole config is ignored until you correct it.

What this error means

The Dependabot tab or the .github/dependabot.yml editor reports the config is invalid, naming package-ecosystem as not one of the accepted values, and no updates run.

The property '/updates/0/package-ecosystem' value "yarn" is not one of the accepted values.
Accepted: npm, pip, bundler, cargo, composer, docker, gomod, ...

Common causes

A manager name instead of an ecosystem keyword

Using yarn or pnpm fails because the ecosystem for JavaScript is npm; the tool, not the ecosystem keyword, is what varies.

A typo or an unsupported ecosystem

A misspelled value, or one Dependabot does not support, is rejected by schema validation.

How to fix it

Use an accepted package-ecosystem value

1. Look up the ecosystem keyword for your manager (for example npm covers yarn and pnpm).
2. Replace the invalid value with the accepted keyword.
3. Commit and re-check the config from the Dependabot tab.

updates:
  - package-ecosystem: "npm"   # covers npm, yarn, pnpm
    directory: "/"
    schedule:
      interval: "weekly"

Validate the config before merging

Edit dependabot.yml in the GitHub editor, which flags invalid ecosystems inline, so the fix lands before it reaches the default branch.

How to prevent it

• Map your package manager to the correct Dependabot ecosystem keyword.
• Validate dependabot.yml in the editor before committing.
• Keep one updates entry per real ecosystem in the repo.

Related guides