Departures from Renovate
The Count is an independent project, not a Renovate clone, and he does many
things his own way. This page lists only the differences a Renovate user is
likely to trip over: defaults that differ, features they would expect that are
missing, and behaviour that changes their pull requests. The
compatibility matrix maps managers and options, and
migrating a config translates a renovate.json.
Configuration
Section titled “Configuration”Pkl, not JSON
Section titled “Pkl, not JSON”- Renovate: JSON or JSON5, with named presets,
local>references and config migration - The Count: Pkl only, with a typed schema; unknown fields are errors. Configs are shared with ordinary Pkl
amendsandimportof local files, with no remote imports - Why: Typed, composable config that is validated when it loads, without network access
No presets; explicit defaults
Section titled “No presets; explicit defaults”- Renovate: Most of a typical config comes from presets such as
config:recommended - The Count: No presets. The schema’s defaults are exact versions, except that Cargo,
pyproject.toml, Bundler and Composer default topreserve(a release a range already allows moves the committed lockfile and leaves the manifest alone), digest pins for actions and images, manual merges, one PR per update, release notes, a dependency label and a semantic commit prefix - Why: Every default is visible in the schema, so a config says exactly what it changes
Default excluded paths
Section titled “Default excluded paths”- Renovate:
ignorePathsdefaults tonode_modulesandbower_components;vendor, test and example directories are ignored only by theconfig:recommendedpreset. A repository’signorePathsreplaces the list - The Count:
excludedefaults tonode_modules,bower_components,vendor,.git,test,tests,__tests__,__fixtures__,fixturesandexamplesat any depth. Amending adds to the defaults and a!entry re-includes a path; assigning a new Listing replaces them - Why: With no preset layer, the defaults carry what a recommended setup ignores; test data and examples hold manifests nobody deploys
Prefixed patterns
Section titled “Prefixed patterns”- Renovate: Match fields accept either a slash-delimited regex or a glob
- The Count: Patterns need an explicit
regex:orglob:prefix, optionally negated with!; globs are path-aware - Why: No guessing from delimiters, and literal slashes in package names stay literal
Rules replace lists
Section titled “Rules replace lists”- Renovate:
packageRulesmerge, so a later rule adds to an earlier rule’s lists - The Count:
rulesapply in order and a later rule replaces whole values, lists included. An emptygroupmeans separate PRs - Why: A smaller, explicit policy model: the last rule that sets a value wins
One extractor model
Section titled “One extractor model”- Renovate: Regex custom managers with
currentValueanddepNamecaptures and Handlebars templates - The Count: Pkl
extractorswithcurrent,sourceanddependencycaptures and plain{capture}substitution, in Rust regex syntax, which has no lookaround - Why: One validated model with no executable template helpers
Schedules are cron windows
Section titled “Schedules are cron windows”- Renovate: Natural-language or cron
schedulewith atimezone, and duration strings - The Count:
waitHoursplus cronwindowswith a named time zone; a window is due on the first run after it opens. Empty windows mean any time - Why: A mistyped schedule is an error when the config loads, instead of a window that never opens
Zero is not unlimited
Section titled “Zero is not unlimited”- Renovate:
0means unlimited for limits such asprConcurrentLimit - The Count:
concurrentis 10 by default andperHouris unlimited,nulllifts a limit, and zero is rejected - Why: Zero meaning “unlimited” is easy to set by accident
Branch and commit names
Section titled “Branch and commit names”- Renovate:
renovate/branch prefix;semanticCommitsswitches the commit style - The Count:
patchula/branch prefix and achore(deps):commit prefix (fix(deps):for security fixes, so release tooling ships them), both overridable - Why: His own identity and predictable messages
How the Count runs
Section titled “How the Count runs”No onboarding pull requests
Section titled “No onboarding pull requests”- Renovate: Opens an onboarding PR in a repository without a config
- The Count: Skips repositories without a config. In a local checkout with no config, the CLI offers its defaults or a starter
patchula.pklat a terminal, and--default-configuses the defaults without asking - Why: Repositories opt in deliberately
NuGet sources need a source mapping
Section titled “NuGet sources need a source mapping”- Renovate: Looks a NuGet package up in every source
nuget.configlists - The Count: Looks it up on nuget.org only when nuget.org is the only source, or when
packageSourceMappingmaps the package there; with another source and no mapping, every NuGet lookup fails. See package registries - Why: NuGet takes a package from whichever source answers, and its lockfile does not say which, so without a mapping a private package’s name could be looked up on nuget.org, where it may be someone else’s. Source mapping is also NuGet’s own advice against dependency confusion
One other Maven repository fails every lookup
Section titled “One other Maven repository fails every lookup”- Renovate: Queries every repository a POM,
settings.xmlor Gradle script names and merges what they list - The Count: Looks artifacts up on Maven Central only when no build file in the repository names another repository; with one anywhere, every lookup of that build system fails — a warning names the file and repository once per build. See package registries
- Why: Maven and Gradle take an artifact from the first repository that has it and record nothing about which, so merging lists can propose a public artifact that shadows a private one of the same coordinates
Registry credentials are operator settings
Section titled “Registry credentials are operator settings”- Renovate:
hostRulesin the repository config, with secrets encrypted for the app or passed in by the self-hosted runner - The Count:
registriesin the operator settings file, keyed by URL prefix, with secrets from environment variables or files. A repository config cannot name a credential or a host to send one to — and a repository that commits one anyway, as an explicit credential setting a tool or lookup reads (auth keys in.npmrc,.yarnrc.yml,pnpm-workspace.yaml,composer.json,nuget.config,poetry.toml,pyproject.tomlor.cargo/config, or a user and password in a field that names a registry URL), is refused outright as hygiene: no lookups, no branches. Credentials cover registry reads, version lookups and image manifest and SBOM reads alike, for the sources that take a registry URL. Lockfile tools get an entry’s credentials only when it setstools = true, and as they run repository and package code, any repository the Count processes can then read them - Why: One server serves many organisations, and a repository config can point a dependency at any URL
Packages come from their lockfile
Section titled “Packages come from their lockfile”- Renovate: Looks a Python package up in every index the project names,
--extra-index-urlincluded, a gem in the sources its Gemfile names, and a PHP package in the repositoriescomposer.jsonlists - The Count: Takes each Python package’s index from what
uv.lockorpoetry.lockrecords, each gem’s source fromGemfile.lock, or from a Gemfile made only of a few plain forms, and each PHP package’s registry fromcomposer.lock. A package neither settles fails its lookup, with a message to commit a lockfile, in a project that configures any registry besides the public one, or whose settings the Count does not know; for gems, that includes a Gemfile line such as a condition or agit_source. See package registries - Why: With several registries, the same name can be a private package in one and anyone’s package on the public one. The lockfile is the tool’s own answer; predicting it from the settings, or from a Gemfile, which is Ruby, would mean re-implementing each tool’s resolution, and a wrong guess is how dependency confusion happens
pip requirements files are not maintained
Section titled “pip requirements files are not maintained”- Renovate: Updates
requirements.txtandpip-compileinputs, looking packages up in the indexes their options name - The Count: Does not read them. Each pip requirements file is listed as skipped with the reason, recommending a move to uv (
uv init --bare, thenuv add -r requirements.txt), whosepyproject.tomlanduv.lockit maintains - Why: pip takes each package from whatever index a file’s options, the files it includes and the environment name, which cannot be settled for certain from the repository; a guess could propose someone else’s package of the same name
A run that lost a race exits 5
Section titled “A run that lost a race exits 5”- Renovate: A repository that changes during a run is retried on a later run, and the run itself succeeds
- The Count: The repository is reported
stale, the server runs it again a minute later, andpatchula runexits 5, so a scheduled GitHub Actions run fails its step - Why: A run that wrote nothing should not look green; the next scheduled run retries it
See GitHub Actions.
What gets updated
Section titled “What gets updated”Indirect Go requirements
Section titled “Indirect Go requirements”- Renovate: Indirect requirements are off by default
- The Count: Every explicit
go.modrequirement is maintained, indirect ones included - Why: A security fix should not wait for a direct dependency to move
mise tools
Section titled “mise tools”- Renovate: Looks each tool up through its backend’s datasource, under the backend’s package name
- The Count: Asks the pinned mise to list each tool (
mise ls-remote --json --prerelease) in a sandbox, and reports the tool’s own name as its package with the sourcemise - Why: Every backend mise can list works, with mise’s own registry and version rules
Rules and branch names use the tool’s name: jq, not jqlang/jq, and patchula/jq-1.x. A tool’s options travel with it in brackets, so its package is rust[profile="minimal"] for rust = { version = "1.100.0", profile = "minimal" }; a rule’s packages selects it by the bare name, rust. asdf: and vfox: tools, and registry names that only have a plugin backend, are refused with a warning, because their plugins are code from the repository being read. See mise lookups.
As a GitHub App, the Count hands mise a read-only token scoped to the repository being read, not the installation’s token. A tool released from another private repository the App can read, such as github:your-org/internal-cli, is not found from a different repository, where Renovate’s installation token would list it.
Nix flake inputs
Section titled “Nix flake inputs”- Renovate: The
nixmanager is beta and off by default - The Count:
nixis on by default; it readsflake.lockbeside aflake.nixand resolves each input withnix flake prefetch - Why: Locking runs no repository code, so there is no reason to keep it opt-in
See Nix.
Copier templates are reported, not applied
Section titled “Copier templates are reported, not applied”- Renovate: Runs
copier updateto move a template to its new tag, with--trustwhen allowed - The Count: Reports the new tag and opens no PR. Copier runs only on your own working tree, with your own
copier, when you ask for it in the TUI or withpatchula apply --copier, and never with--trust - Why: Applying a template runs the template author’s code at a new, unreviewed version; on the server that code would run next to the installation token and other repositories
The Count never bumps _commit on its own either, since the next copier update would diff from the wrong base. See Copier.
A 24-hour release-age wait
Section titled “A 24-hour release-age wait”- Renovate:
minimumReleaseAgeis off by default - The Count:
waitHoursis 24 by default for dated releases; the newest eligible release is proposed and newer ones are reported as held back - Why: It follows mise’s default
minimum_release_age; undated releases have no wait
See the release-age wait.
The wait binds what Cargo locks
Section titled “The wait binds what Cargo locks”- Renovate:
minimumReleaseAgechecks only the dependency it updates; what the lockfile gains in the same run is not age-checked - The Count: tells Cargo
registry.global-min-publish-age, so every release a Cargo update or maintenance resolve newly locks — dependencies it names and transitive crates alike — has waited as long - Why: Holding the named dependency while Cargo locks a newer release of something else quietly defeats the wait; a
security.applyfix inside the window alone runsresolver.incompatible-publish-age = "allow"
See Cargo’s cooldown. Rust older than 1.100 does not understand the keys; the run warns that transitive crates do not wait.
Exact npm versions
Section titled “Exact npm versions”- Renovate:
rangeStrategydefaults toauto, which keeps a caret or tilde range and updates only the lockfile when the new version satisfies it - The Count:
versions = "exact"pins dependencies and devDependencies; peer ranges are widened, never pinned - Why: Reproducible installs, while consumers keep the peer ranges they support
See version policies.
A separate patch track
Section titled “A separate patch track”- Renovate: Proposes the highest non-major release
- The Count: Offers a patch update alongside the minor one
- Why: The smaller upgrade can be taken on its own
Stable releases, not LTS
Section titled “Stable releases, not LTS”- Renovate: Node targets follow the LTS line
- The Count: Proposes the newest eligible stable version the policy allows
- Why: A hidden LTS restriction should not be inferred from a package name
For an opt-in LTS rule, see lookup policy.
Warnings when auto-merge has nothing behind it
Section titled “Warnings when auto-merge has nothing behind it”- Renovate: Automerges as configured, whatever CI the repository has
- The Count: Warns on PRs set to merge, and on the dashboard, only on positive evidence: no CI runs on the PR and no checks reported on recent default-branch commits; GitHub’s native auto-merge is on and no status check is required; or a security fix merges, nothing runs on the default branch for its files and no checks reported on recent commits. What he can’t read is unknown and never warns
- Why: An update that merges untested, or merges and never ships, is worse than one left open
See tooling warnings.
No new step-level SHA pins in locked workflows
Section titled “No new step-level SHA pins in locked workflows”- Renovate:
pinDigestspins every action reference to a commit SHA - The Count: In a workflow
.github/workflows/actions.locklists, he adds no new SHA pin to a step’suses:— the lockfile records the commit itself, sogh actions-lockwould treat his pin as something to unpin. An existing pin still moves with its update,jobs.<id>.usesreusable workflows still pin, and workflows the lockfile does not list pin as before - Why: Two tools writing the same line disagree about who owns the ref; the lockfile is the pin
See actions.lock.
Reference data merges itself
Section titled “Reference data merges itself”- Renovate: No built-in category; release age, schedules and automerge apply as configured
- The Count: CA root bundles, time zone data and the public suffix list are
reference-data; by default their updates skip the wait and windows, get their own PR and merge once checks pass - Why: A stale trust store keeps trusting a distrusted CA, and these packages change data, not APIs
See reference data.
Advisories from OSV.dev
Section titled “Advisories from OSV.dev”- Renovate:
vulnerabilityAlertsreads the repository’s Dependabot alerts and opens separate alert PRs - The Count: OSV.dev only, on by default; updates that fix an advisory are marked and labelled, with no separate alert PRs
- Why: Works without Dependabot or the App’s
vulnerability_alertspermission, and fits one batched query per run
See security advisories.
Image rebuild advisories
Section titled “Image rebuild advisories”- Renovate: Vulnerability alerts cover package ecosystems, not the OS packages inside an image
- The Count: Compares a pinned image’s old and new SBOMs through OSV.dev; a rebuild whose new digest no longer has an advisory the old digest had is a security update
- Why: Rebuilds of a pinned tag are mostly OS security fixes, which otherwise look like any other digest change
Lockfiles
Section titled “Lockfiles”aube for npm, pnpm and Yarn Classic
Section titled “aube for npm, pnpm and Yarn Classic”- Renovate: Regenerates npm, pnpm and Yarn locks with npm, pnpm and Yarn
- The Count: Regenerates
aube-lock.yaml,pnpm-lock.yaml,package-lock.json,npm-shrinkwrap.jsonand Yarn Classicyarn.lockwith aube;lockfiles.npmEngine = "npm"restores native npm for npm lockfiles. Berryyarn.lockstays with Yarn - Why: Lockfile updates are 10 to 30 times faster; why aube lists how its output differs from each tool’s
actions.lock
Section titled “actions.lock”- Renovate: Runs
gh actions-lockover the whole.github/workflowsdirectory - The Count: Runs it only over the edited workflows the lockfile already lists, with
--no-onboardand--no-narrowalways set: the Count never adds a workflow or an action to the lockfile and never rewrites auses:ref he did not edit. Local./composites are never locked, so an update inside one makes no run; a$/composite is relocked under the listed workflows that call it - Why: Someone else’s broken or unpinned action in an unlisted workflow must not hold the Count’s update, and a run that onboards would grow the lockfile he was never asked to write
Lockfile maintenance also runs the tool, with --relock over the whole
directory: refs that moved upstream, such as a floating v7, are advanced
to their new commits, listed workflows that no longer exist are dropped, and
the maintenance PR lists each moved ref. Renovate’s documentation does not
describe a relock, so a Renovate user should expect actions.lock in the
maintenance PR. No release-age wait applies to what the relock picks up.
The run authenticates with the run’s own GitHub token — a scoped installation token on the App server, the token the run was given for the CLI and the GitHub Action, as Renovate hands its token to tools — and reaches github.com only. An action the token cannot read, such as a private one, holds the update with the reason rather than publishing a lock that drops it. See actions.lock.
© 2026 Sweepy
