Built-in updaters

Built-in updaters cover common repository maintenance without writing a plugin. Each updater detects whether a repository is applicable and avoids changes when its required inputs are absent.

GitHub Actions

Command	Summary
zizmor	Fix selected GitHub Actions and Dependabot findings
github-app-token	Rename the deprecated app-id action input

Copier

Command	Summary
copier	Advance a Copier-generated project to its newest template tag
copier-migration	Change one supported Copier answer at the current template revision

Pixi

Command	Summary
pixi-version	Update pixi-version pins in setup-pixi workflows
pixi-update	Regenerate Pixi lockfiles

Node dependencies

Command	Summary
node-dependency-cooldown	Add release-age protections for Node dependencies

One-off updaters

Command	Summary
custom	Run a trusted updater from a local Python file

See repository selection, preview and publication, and concurrency for shared options. See Configuration for deployment-wide defaults.

Managed branches

Publication pushes each update item to a deterministic branch and opens one pull request from it. <angle brackets> mark a suffix derived from the update item; the linked configuration changes the part before it.

Command	Default branch	Configure with
zizmor	zizmor-fixes	Pull-request template
github-app-token	github-app-token-client-id	Pull-request template
node-dependency-cooldown	node-dependency-cooldown-fixes	Pull-request template
copier	copier-autoupdate-<tag>	Not configurable
copier-migration	copier-migration-<migration>	Copier migration
pixi-version	pixi-version-autoupdate	autoupdate-branch in the repository
pixi-update	pixi-update/<manifest path>	autoupdate-branch-prefix in each manifest

quant-ranger checks managed pull requests prior to pushing to prevent overwriting manual changes on those branches.