Renovate "Cannot find preset" error in CI

By Daniel Zoghalchali·Latchkey

Renovate resolves every entry in extends before running. If a preset name is wrong, or it lives in a private repository Renovate has no token for, resolution fails with "Cannot find preset" and the run stops.

What this error means

Renovate raises a "Cannot find preset" config error naming the preset from your extends array, and opens a config error issue instead of updating dependencies.

ERROR: Cannot find preset's package (github>myorg/renovate-config)
  presetName: default
  error: Not Found

Common causes

A misspelled or nonexistent preset

The extends entry references a preset or repo path that does not exist, so resolution returns Not Found.

A private preset repo Renovate cannot read

A shared config in a private repo needs a token with access to that repo; without it, Renovate cannot fetch the preset.

How to fix it

Correct the preset reference

1. Confirm the preset repo and file path exist.
2. Use the correct github>owner/repo (and preset name after a colon) syntax.
3. Re-run Renovate to confirm resolution.

{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": ["github>myorg/renovate-config:base"]
}

Grant access to a private preset repo

Give the Renovate token access to the repository that hosts the shared preset so it can be fetched at run time.

How to prevent it

• Reference presets by their exact repo path and name.
• Ensure the Renovate token can read private preset repos.
• Validate config so a bad extends is caught before merge.

Frequently asked questions

Related guides

References

• GitHub Actions documentation