Skip to main content

Scanner coverage

The shared custom managers track annotated versions in their supported file patterns. Check the policy source for the current list.
Place the annotation immediately before the value it tracks. The annotation can set a versioning value; otherwise the manager uses semver-coerced. Date-shaped or ragged tags need loose versioning. The image manager covers both defaults/main.yml and defaults/main/ layouts. A self-test checks those paths against the shared preset. Some pins have a companion checksum the scanner cannot calculate. Use a pull-request gate to reject a version/hash mismatch. Test the gate with a deliberate mismatch and confirm that it fails. The shared preset disables the Dependency Dashboard. When changing a manager, use the coverage self-test to check both role-default layouts. Extend the scanner for any new file shape and add a pull-request gate for companion hashes or coupled versions. Hindsight has coupled client and server pins. Proxmox guest tags use validation rather than schema enforcement.

Action and source pin policy

First-party dependencies use commit pins to the upstream branch green. Third-party actions use a full commit SHA with a trailing # vX.Y.Z comment. The enterprise Workflow Policy check enforces the third-party action pin rule. First-party source pins use commit references from green; their lock files hold the exact revision, and the org scanners enforce that shape:
  • zizmor. Third-party actions are hash-pinned.
  • CodeQL. Code scanning default setup on public repos only (free; private repos excluded to avoid the paid Code Security charge). tofu-github manages the default setup and requires CodeQL results on the same public repositories. No committed query-filter config.
  • OSV-Scanner. Reports dependency vulnerabilities, not ref pinning.
The full per-scanner posture lives in JacobPEvans/.github → SECURITY.md.

Master and repo config

JacobPEvans/.github is the Renovate policy master. Its renovate-presets.json owns the shared policy. The github>JacobPEvans/.github entry point is defined in default.json, and renovate-nix.json adds Nix support. dryvist/.github’s default.json keeps the local>dryvist/.github and github>dryvist/.github entry points. It combines config:recommended with the master preset. Its renovate-presets.json re-exports the JacobPEvans master preset unchanged; dryvist/.github owns no separate policy. Consumer configs extend the shared preset, then list only repo-specific holds.

Schedule and grouping

For third-party updates, the shared schedule is Saturday 00:00–05:59 in America/Indiana/Indianapolis. Renovate’s built-in group:allNonMajor opens one pull request per repository for minor, patch, and digest updates; each major update opens its own pull request. First-party pins use one grouped pull request per consumer, refreshed every 4 hours. The shared preset sets prCreation to not-pending, so Renovate waits for branch status checks to finish before it creates a pull request. The shared preset sets internalChecksFilter to strict. Third-party updates with the seven-day release-age hold wait until that age passes. The complete trust tiers live in SECURITY.md. The shared policy sets minimumReleaseAgeBehaviour to timestamp-optional for lock-file maintenance and digest updates. Updates without a release timestamp can proceed, while third-party dated releases retain their configured age hold. See the shared Renovate policy. The shared preset turns off npm lock-file maintenance so package-manager guardrails remain authoritative. It also turns off Terraform/OpenTofu lock-file maintenance because provider pins and their lock entries must move together in ordinary updates.

First-party pins

First-party dependencies are pinned to commits of the upstream branch green. Renovate keeps one grouped pull request per consumer, refreshed every 4 hours, with platform auto-merge and no release-age hold. Renovate pull requests take the bot lane. A pull request that needs an upstream change bumps the pin itself. Release tags exist for outside users.

Nix flake locks

Nix repos also extend the shared renovate-nix preset. Renovate’s nix manager and lockFileMaintenance relock flake.lock in the Saturday window. The shared presets set no minimumReleaseAge on lockFileMaintenance, so Nix lock-file maintenance has no release-age hold. In Nix repositories, Go directive and toolchain bumps come in their own review-required PRs.

Package-manager release ages

Project-level package managers use native settings for a seven-day release age on third-party updates:
  • uv in nix-ai orchestrator. Set exclude-newer = "7 days" and required-version = ">=0.9.17" in orchestrator/pyproject.toml.
  • Bun in ai-workflows-testing, raycast-smart-issue, and JacobPEvans/.github-ai. Set minimumReleaseAge = 604800 seconds in bunfig.toml.
  • uv in python-template. Set exclude-newer = "7 days" and required-version = ">=0.9.17" in pyproject.toml. It also lists reviewed exceptions in exclude-newer-package, which hold a named package to a later cutoff so a release that fixes a published advisory can resolve.
  • Private repositories. Several set the same seven-day npm and uv windows in their own config.
  • pnpm in three projects. Set minimumReleaseAge: 10080 minutes in each project’s tests/pnpm-workspace.yaml:
  • npm in homelab-wall. Set min-release-age=7 in .npmrc.
The nix-home Home Manager package config also writes user-level settings:
  • npm’s .npmrc sets min-release-age=7.
  • Bun’s ~/.bunfig.toml and ~/.config/.bunfig.toml set minimumReleaseAge = 604800 seconds.
  • uv’s ~/.config/uv/uv.toml sets exclude-newer = "7 days".
  • pip’s ~/.config/pip/pip.conf sets uploaded-prior-to = P7D.

Container image pins

One shared custom manager tracks *_image: keys in Ansible role defaults. It accepts plain or folded YAML values whether the tag is quoted or unquoted, with an optional sha256 digest. Use concrete tags, not latest or stable. The shared Molecule image manager tracks image: entries in any molecule/*/molecule.yml file. Put # renovate: datasource=<ds> depName=<image> on the line preceding image:. The value may use plain YAML or folded >- form and must pin tag@sha256:digest.

Dependabot security updates

Dependabot security updates are disabled in some repositories, so Renovate supplies security pull requests there. Dependabot alerts remain enabled, and Renovate reads them.