Renovate
What is out of date in the repositories on disk, as swamp data: Renovate run in its local mode, with no forge, no token and no pull request.
@dataverket/renovate/local has one method, lookup. It takes one repository directory or a list, starts one container of the Renovate image per directory with the directory mounted read-only, and records the updates Renovate would propose: dependency, datasource, manager, file, current and new version, update type, with counts by type, the lookups that failed, and Renovate's warnings. One record per repository and one inventory per run, so a workflow can assert "no major update pending" and a report can sum over repositories.
A directory that is missing, has no Renovate configuration, or whose run fails or passes its time limit is a recorded state and does not stop the others; so is one where Renovate looked nothing up or did not read the configuration that is there, and neither is ever called up to date. The host's proxy variables stay out of the container unless asked for. Runs on Podman or Docker; the live suite runs on rootless Podman.
Global Arguments
| Argument | Type | Description |
|---|---|---|
| image | string | The Renovate container image. It is the Renovate version, so there is no default: name a version tag or a digest. A tag that moves, such as latest, gives results that change without a change here |
| containerBinary? | string | The container command: podman or docker, by name from PATH or as a path |
| timeoutSeconds? | number | How long Renovate may run on one repository before its container is stopped and the repository is recorded as failed; at most an hour |
| pull? | enum | missing: pull the image once, before the first repository, when the engine does not hold it. never: fail instead |
| pullTimeoutSeconds? | number | How long that pull may take; the image is about 1.4 GB. At most an hour |
| logLevel? | enum | How much of Renovate's log reaches this method's log: with info its warnings and errors, with debug its other lines too. Renovate itself always runs at debug, where it says which configuration file it read |
| passProxy? | boolean | Podman only. false: the host's proxy variables (http_proxy, https_proxy, ftp_proxy, no_proxy) are kept out of the container. true: Podman passes them in, for a machine that reaches the registries through a proxy; a password in a proxy URL is then blanked in everything kept |
| network? | string | Given to the engine as --network: none, or the plain name of a network you made, for example one with restricted egress. A mode such as host or container:<name>, and any value with options, is refused: those can widen what a repository's configuration reaches. Left out, the engine's default network. none makes every lookup fail |
| Argument | Type | Description |
|---|---|---|
| repo? | string | One repository directory, absolute or relative to the swamp repository root. Give repo or repos, not both |
| repos? | array |
Resources
- Has README or module doc2/2earned
- README has a code example1/1earned
- README is substantive1/1earned
- Most symbols documented1/1earned
- No slow types (deprecated)1/1earned
- Dependencies pass trust audit2/2earned
- Docs keep secrets in a vault1/1earned
- Has description1/1earned
- Platform support declared (or universal)2/2earned
- License2/2earned
- Verified public repository2/2earned