Skip to content

Migrating a config

There is no converter. A renovate.json is usually a handful of presets and a few rules, and most of those presets turn out to be the Count’s defaults already. Translating by hand, or asking an agent to, takes minutes and leaves you with a config you understand.

config:recommended, :semanticCommits, :dependencyDashboard, :pinAllExceptPeerDependencies, helpers:pinGitHubActionDigests and docker:pinDigests mostly describe what the Count does without being asked: exact pins (Cargo, pyproject.toml, Bundler and Composer default to preserve instead, and move the lockfile for releases a range already allows), digest pins for actions and images, semantic commit prefixes, the dependency dashboard and one PR per update. A config with nothing in it is close.

patchula.pkl
amends "PatchulaConfig.pkl"

Read through the defaults and keep what you actually rely on. Departures lists the defaults that differ from Renovate’s, such as the 24-hour release-age wait and exact npm pins.

Renovate Count Patchula
extends amends "org.pkl" or import
enabledManagers managers (Renovate names differ: gomod is go, docker-compose is compose, pep621 and poetry are pyproject (pip_requirements has no equivalent), helmv3 is helm)
ignoreDeps ignore, with globs and regexes
ignorePaths exclude
managerFilePatterns files
packageRules rules
matchPackageNames select { packages { ... } }
matchDepNames select { dependencies { ... } }
matchManagers, matchDatasources select { managers }, select { sources }
matchFileNames select { files }
matchUpdateTypes select { updates } (pinDigest is pin)
matchDepTypes select { kinds }
matchCurrentVersion select { current = "semver:..." }
allowedVersions apply { permitted = "semver:..." }
enabled: false apply { active = false }
groupName apply { group = "..." }
automerge apply { merge = true }
rangeStrategy apply { versions = "exact" | "preserve" | "widen" }
pinDigests: false apply { digest = false }
minimumReleaseAge apply { waitHours = 72 }
schedule, timezone windows { new Window { cron { ... } zone = "..." } }
labels, addLabels labels
semanticCommitType, commitMessagePrefix commitPrefix
prBodyNotes bodyNotes
fetchChangeLogs: "off" releaseNotes = false
prConcurrentLimit, prHourlyLimit prs { concurrent; perHour }
branchPrefix prs { branch }
rebaseWhen prs { rebase = "conflicts" | "behind" }
dependencyDashboard prs { dashboard = false } turns off the dashboard, which is on by default
lockFileMaintenance lockfiles { refresh = true }
postUpdateOptions: ["gomodTidy"] lockfiles { tidyGo = true }
customManagers (regex) extractors
regexManagers capture depName capture dependency
currentValue current
extractVersion extract
datasourceTemplate, depNameTemplate, packageNameTemplate, versioningTemplate source, dependency, package, scheme

Watch for these when translating (the configuration guide has the details):

  • A later rule replaces an earlier one’s lists instead of merging them.
  • Empty group means separate PRs.
  • Zero is never “unlimited”; use null.
  • concurrent is 10 by default, so the first run on a neglected repository opens ten ordinary PRs and lists the rest on the dashboard. Security fixes are not held back by the limit, so a first run can open more than ten.
renovate.json
{
"extends": ["config:recommended"],
"schedule": ["before 6am on monday"],
"packageRules": [
{
"matchUpdateTypes": ["minor", "patch"],
"matchCurrentVersion": "!/^0/",
"automerge": true
},
{
"matchPackageNames": ["/^@vitest//", "vitest"],
"groupName": "vitest"
}
]
}

becomes

patchula.pkl
amends "PatchulaConfig.pkl"
defaults {
windows {
new Window { cron { "* 0-5 * * 1" } }
}
}
rules {
new Rule {
select {
updates { "minor"; "patch" }
current = "!semver:<1"
}
apply { merge = true }
}
new Rule {
select { packages { "vitest"; "glob:@vitest/*" } }
apply { group = "vitest" }
}
}

Then check it:

Terminal window
patchula config check .
patchula run --dry-run owner/repo

The examples directory has a dozen real configs translated this way.

Presets, onboarding, config migration, postUpgradeTasks, replacement PRs and platforms other than GitHub have no equivalent. Of hostRules, only the credentials for supported lookups carry over, as operator registries in the settings file rather than the repository config. vulnerabilityAlerts reads Dependabot alerts; the Count checks OSV.dev advisories instead, on by default. The compatibility matrix lists everything. A # renovate: comment used by a regex manager can stay in your files: it is only text, and your Pkl extractor can match it.