Skip to content

Forge and CIreference

Self-hosted Renovate for a Forgejo-primary Docker Compose fleet

After migrating the repository fleet to Forgejo as primary and turning off Dependabot on the read-only GitHub backups, container image tags across the Composer-managed Docker Compose stacks needed a Forgejo-native replacement. A self-hosted Renovate job runs daily at 18:40 UTC (02:40 SGT) as a one-shot compose_run pipeline step on the NAS Docker daemon, scans 29 opted-in repositories on a self-hosted Forgejo instance, and opens pull requests that deploy only when reviewed and merged.

The preset rules and operational gates were derived from a manual sweep of 14 stack deployments (41 candidate image updates) on 2026-11-13, verified by a 13-assertion dry-run harness (scripts/test-preset.sh) and a 27-repository onboarding dry run on 2026-11-13, exercised on a first full merge sweep of ~30 pull requests across 18 repositories on 2026-11-15, and expanded to 29 repositories on 2026-11-16 when two Go CLI repositories opted into gomod updates. A companion vulnerability scanner pairs with Renovate: it tells the operator which CVEs in the running fleet are actively exploited or fixable (covered separately in the vigil vulnerability sweep).

  • Pull requests over pull-and-restart: every stack pins exact image tags in Git, and 8 of the 41 updates in the 2026-11-13 manual sweep required either holding the release (4 updates) or running stack-specific steps such as ALTER EXTENSION, a PostgreSQL index audit, or an encrypted .env edit (4 updates).
  • Inlined global preset, zero-commit opt-in: default.json is inlined into config.js via require('./default.json') rather than globalExtends, and repositories opt in through the repositories array in config.js so onboarding a stack does not require a renovate.json commit that would trigger its CI and deploy pipeline.
  • Registry and versioning workarounds: three-part LinuxServer tags (v1.6.2-ls372) must map lsNN to the regex build group because Renovate ignores revision when build is absent1; linuxserver/* lookups are routed to ghcr.io (1,000 pages) because anonymous Docker Hub tag paging returns HTTP 403 at page 11.
  • Dashboard approval for high-blast-radius changes: all major bumps, 0.x minor bumps (separateMinorPatch: true), language-runtime minor bumps, databases, caches, and the Forgejo CI host stack (codeberg.org/forgejo/forgejo and data.forgejo.org/forgejo/runner) wait on the per-repository Dependency Dashboard until ticked2.
  • One email per changed run: digest.sh aggregates open pull requests, pending dashboard approvals, and filtered repository warnings across all visible repositories into a single comment on a tracking issue (“Renovate digest”), gated by a SHA-256 content hash and a 20-hour minimum interval.
  • Deliberate credential minimalism: the job runs with RENOVATE_TOKEN only. RENOVATE_GITHUB_COM_TOKEN, DOCKERHUB_TOKEN, and NOTIFICATION_TOKEN are unset by choice; pull requests omit GitHub-hosted release notes, and digest.sh strips the resulting "No github.com token has been configured" warning.
Composer pipelinerenovate-daily18:40 UTC (02:40 SGT)NAS Docker daemonrenovate-job:local(uid 12021, 2 CPU / 2 GiB)compose_run(45m timeout)Public registriesDocker Hub, ghcr.io, lscr.io,codeberg.org, data.forgejo.org,gcr.iotag lookups(/cache volume)Forgejo APIgit.example.comopted-in repositoriesrenovate/* branches,PRs + Dashboard issuesdigest.shSHA-256 + 20h gatetracking-issue commentpost-runOperator merge-> webhook / CI / release /manual deployafter review1 email toissue subscriber

The renovate stack lives on the NAS host behind a dedicated /24 bridge network (renovate, where .2 is the job container) with no published ports and no reverse-proxy route. Its compose.yaml places the single renovate service under profiles: ["jobs"] with restart: "no", a 2-CPU / 2-GiB resource limit, and a named cache volume mounted at /cache (RENOVATE_BASE_DIR: /cache). Because the service is profiled, a normal stack deploy never starts a long-running container; Composer’s renovate-daily pipeline invokes it once per day via a compose_run step with a 45m0s timeout.

Because Composer executes the stack on the remote NAS Docker daemon where repository-file bind mounts from the controller do not exist, the Dockerfile bakes config.js, default.json, run.sh (/usr/local/bin/renovate-job), and digest.sh (/usr/local/bin/renovate-digest) directly into renovate-job:local on top of ghcr.io/renovatebot/renovate:<pinned version> (the Dockerfile pin, which Renovate bumps through its own pull requests). Upstream Renovate runs as non-root user ubuntu (uid 12021); the Dockerfile creates /cache and chowns it to 12021:0 at build time so a freshly initialised named volume does not inherit root:root ownership and cause Renovate to exit 1 on startup.

Why Renovate over pull-and-restart alternatives

Section titled “Why Renovate over pull-and-restart alternatives”

The 2026-11-13 manual sweep across 14 deployed stacks tested 41 candidate image updates before any automation was written. Four updates were held (codeberg.org/forgejo/forgejo 17.0.1 for breaking app.ini duration parsing and a pending 17.0.2 secrets fix, changedetection.io 0.70.x for apprise 2.x template changes, valkey 9.2 as an unneeded minor bump, and linuxserver/sonarr 5.14-* development tags), and four deployed updates required coordinated actions outside the image tag itself:

  1. A photo-library stack reads its live version from IMMICH_VERSION inside a SOPS-encrypted .env file while docker-compose.yml only holds the ${IMMICH_VERSION:-vX} fallback default.
  2. timescale/timescaledb-ha (pg18.6-ts2.31.0 -> pg18.6-ts2.32.0) required running ALTER EXTENSION timescaledb UPDATE in both the application database and the postgres database after container start.
  3. Six PostgreSQL 18.7 upgrades carried release-note advisories to audit and REINDEX btree indexes on unconstrained bpchar columns and gist_trgm_ops indexes.
  4. A task-board stack (2.7.1 -> 2.8.0) required a matching companion CLI bump and an interactive first run to populate its new trust store.
ApproachGitOps compatibilityTag ordering and suffix awarenessOperator review pointDecision
Self-hosted Renovate (compose_run pipeline)Opens pull requests against pinned tags in Git; merge triggers the normal Forgejo-to-Composer webhook flowBuilt-in docker-compose3, dockerfile, and custom.regex managers; regex versioning with compatibility groups1Per-update pull request with prBodyNotes plus Dependency Dashboard approval checkboxes2Picked
Watchtower auto-pull / pipeline compose_pullFights pinned tags (radarr:6.4.4.10685-ls326); pulling :latest mutates runtime state outside GitNone beyond registry tag equalityNoneRejected: bypasses Git and cannot express post-deploy SQL or SOPS steps
Diun notificationsDetects registry updates without changing what runsRegistry tag comparisonNotification onlyRejected: opens no pull request and carries no post-deploy steps
Custom oci_tags scriptWould have to generate branches and pull requests via the Forgejo APIWould re-implement -alpine suffix matching, LinuxServer -lsNN ordering, and 0.x semver rules from scratchOnly if custom pull request and dashboard logic were also builtRejected: duplicates Renovate’s datasource and versioning engine
Forgejo Actions scheduled workflowSame pull request output as compose_runSame Renovate engineSame pull request and dashboard outputRejected: runs on the Forgejo Actions runner inside the CI host it proposes updates for, competing with build jobs

Opting a repository in grants the bot user write access, enables the pull-request and issue units on Forgejo, and adds the repository name to config.js without committing anything to the target repository:

  1. Bot permissions and repository units: the non-admin Forgejo user renovate-bot is added as a collaborator with write access (the minimum required to push renovate/* branches and open pull requests), and the repository’s has_pull_requests and has_issues units are enabled via PATCH /api/v1/repos/<owner>/<repo>4. Repositories originally converted from GitHub mirrors had pull requests disabled in Forgejo; when has_pull_requests is off, Renovate logs "Repo has disabled pull requests" and skips the repository.
  2. Global repositories allowlist in config.js: config.js sets platform: 'forgejo', endpoint: 'https://git.example.com/api/v1/', onboarding: false, autodiscover: false, and requireConfig: 'optional'5. Opting in is an entry in the repositories array in config.js rather than a renovate.json commit in each stack repository, because committing a configuration file to an application repository would fire its CI workflow and build-and-deploy pipeline.
  3. Manager scoping: the shared preset enables only container managers ("enabledManagers": ["docker-compose", "dockerfile", "custom.regex"]), matching any Compose filename via /(^|/)[^/]*compose[^/]*\.ya?ml$/. A repository that also wants language-level dependency updates carries its own renovate.json on top of the global configuration: a vulnerability-sweep CLI and a sibling Go CLI repository set enabledManagers to include gomod in their per-repository renovate.json so Go module pull requests never open fleet-wide.

The shared preset (default.json) and its gotchas

Section titled “The shared preset (default.json) and its gotchas”

The repository publishes default.json so any repository with a local renovate.json can write "extends": ["local>config-repo/renovate"]6. In the job container itself, config.js loads default.json directly into the exported global configuration object:

const preset = { ...require('./default.json') };
delete preset.$schema;
delete preset.description;
module.exports = {
...preset,
platform: 'forgejo',
endpoint: 'https://git.example.com/api/v1/',
gitAuthor: 'renovate-bot <renovate-bot@noreply.git.example.com>',
onboarding: false,
autodiscover: false,
repositories,
requireConfig: 'optional',
hostRules,
dockerMaxPages: 200,
};

Dry-running this setup against the 2026-11-13 pre-sweep tags surfaced the Renovate behaviours below, which default.json and the stack repositories encode as explicit rules:

GotchaObserved failure modeFix in config.js, default.json, or target repositories
globalExtends with a local> presetSetting globalExtends: ['local>config-repo/renovate'] in config.js fails immediately with config-presets-invalid because Renovate resolves global presets before initialising the Forgejo platform clientInline require('./default.json') into config.js after deleting $schema and description, and bake default.json into the job image
Inlined ignorePaths and digest.enabledWhen default.json is spread into global config.js, top-level ignorePaths and manager-level digest.enabled are silently ignoredExpress both as packageRules: disable matchUpdateTypes: ["digest"] and disable matchFileNames: ["**/archive/**"]
LinuxServer three-part vs four-part tagsFour-part tags (6.4.4.10685-ls326) use (?<build>\d+)-ls(?<revision>\d+), but three-part tags (v1.6.2-ls372) produced zero updates when lsNN was placed in revision: Renovate’s regex versioning ignores revision when build is absent1Split LinuxServer rules by matchCurrentValue: four-part tags keep ls(?<revision>\d+), while three-part tags map -ls(?<build>\d+)
Anonymous Docker Hub tag paging on linuxserver/*Anonymous hub.docker.com tag pagination returns HTTP 403 at page 11 and Renovate drops the lookup with no error; lscr.io lists ~10,000 tags alphabetically and caps at dockerMaxPages, cutting off v-prefixed tags (bazarr) at the default 20 pagesRoute linuxserver/** and docker.io/linuxserver/** to registryUrls: ["https://ghcr.io"] (1,000-page limit in Renovate’s Docker datasource) and raise dockerMaxPages in config.js to 200 for lscr.io/linuxserver/**
Compatibility prefixes and suffixesWithout a compatibility capture group, Renovate proposed switching GPU architecture tags on ghcr.io/huggingface/text-embeddings-inference (86-1.9.4 -> 121-1.9.4, where 86 is sm_86) and cannot separate the PostgreSQL floor from the extension version in timescale/timescaledb-ha:pg18.6-ts2.32.0Use named (?<compatibility>...) regex groups1 for linuxserver/jellyfin (ubu\d+), timescale/timescaledb-ha (pg\d+(?:\.\d+)?), and text-embeddings-inference (^[a-z0-9]+)
0.x minor vs patch updatesUnder semver, 0.x minor bumps can carry breaking changes (changedetection.io 0.60 -> 0.70 changed notification templates), but gating 0.x updates by default also hides 0.60.x patchesSet separateMinorPatch: true on matchCurrentVersion: "/^v?0\\./" and apply dependencyDashboardApproval: true only to matchUpdateTypes: ["minor"]
Flow-style Compose mappings and ARG-indirected FROM linesFlow-style YAML service definitions (svc: { image: foo:1.0 }) extract zero dependencies in the docker-compose manager; ARG GO_VERSION + FROM golang:${GO_VERSION} is detected in Dockerfiles but Renovate cannot rewrite itFormat Compose service definitions as block YAML, and pin the version directly on the FROM line in Dockerfiles

Two additional rules handle tags that are not plain image: repo:semver strings:

  • SOPS-backed Compose variable defaults: in a photo-library stack, docker-compose.yml writes image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-v3.4.1} and immich-machine-learning:${IMMICH_VERSION:-v3.4.1}, while the live value comes from SOPS .env. A customManagers regex rule extracts depName and currentValue from the ${IMMICH_VERSION:-v...} default, and a packageRules entry groups both images under groupName: "immich" with prBodyNotes instructing the operator to update the SOPS-encrypted .env on the branch before merging.
  • First-party and undeployed files: private images published by their own repositories’ CI workflows are disabled in packageRules (enabled: false prevents failed registry lookups from polluting Repository Problems), and the undeployed NAS rollback Compose file in the CI host stack repository is disabled so Renovate only proposes updates against the live deployment file.

Dependency Dashboard approval gates and version holds

Section titled “Dependency Dashboard approval gates and version holds”

Renovate runs with :dependencyDashboard enabled (prConcurrentLimit: 10, prHourlyLimit: 0, schedule "after 2am and before 6am" Asia/Singapore, and Mondays 2-5am for rolling searxng/searxng YYYY.M.D-sha tags)2. Instead of suppressing risky updates, default.json routes them to the repository’s Dependency Dashboard issue where they wait as unchecked Markdown boxes until ticked:

Rule classMatched packages / update typesDashboard approval required?Attached prBodyNotes or constraint
Routine application patches and 1.x+ minorsLinuxServer apps (radarr, bazarr, sonarr, jellyfin), binhex/**, pgsty/silo, searxng/searxng, 0.x patchesNo (opens pull request directly)immich group notes the required SOPS .env update
0.x minor updatesmatchCurrentVersion: "/^v?0\\./" with matchUpdateTypes: ["minor"] (ghcr.io/dgtlmoon/changedetection.io)YesSeparated from 0.x patches via separateMinorPatch: true
Language runtime base imagespython, golang, node, oven/bun (minor and major update types; patches open directly)YesPython held at <3.15 outside one local-LLM research assistant stack that already runs 3.15 (allowedVersions: "<3.15") until onnxruntime and rawpy ship cp315 wheels
Databases and cachespostgres, pgvector/pgvector, timescale/timescaledb-ha, ghcr.io/immich-app/postgres, valkey/valkey, redis (all update types)Yespostgres notes require checking minor release notes and running scripts/pg-reindex-audit.sh; timescaledb-ha notes require ALTER EXTENSION timescaledb UPDATE in every database (a media-server monitoring stack and postgres); one stack holds postgres at <18 to match its production Supabase project on PostgreSQL 17
Forgejo CI host stackcodeberg.org/forgejo/forgejo, data.forgejo.org/forgejo/runner (all update types)YesNotes require verifying the runner queue is empty and no job exceeds its normal duration before merging
Major updates across all packagesmatchUpdateTypes: ["major"]YesPrevents unattended major upgrades across every datasource

Cross-stack email digest and credential minimalism

Section titled “Cross-stack email digest and credential minimalism”

Without notification filtering, a daily run across 29 repositories would send a separate Forgejo email for every pull request and Dependency Dashboard edit. Instead, run.sh invokes digest.sh (renovate-digest) immediately after renovate finishes:

  1. Cross-repository collection: digest.sh queries /api/v1/user/repos?limit=50 using RENOVATE_TOKEN, iterates over every non-archived repository in sorted order, and fetches open pull requests authored by renovate-bot plus the body of each repository’s open "Dependency Dashboard" issue.
  2. Markdown extraction and noise filtering: from each Dependency Dashboard body, awk and sed extract unchecked items under ## Pending Approval (- [ ] lines rewritten to - needs approval: ... (tick it on the [dashboard](url))) and bullet lines under ## Repository Problems, stripping "No github.com token has been configured".
  3. Content-hash and 20-hour rate gates: the assembled Markdown body is hashed with sha256sum and compared against /cache/digest.sha256. If the hash matches the previous post, or if the body is empty (sum=empty), digest.sh records the state and exits 0 without posting. If the hash changed, digest.sh checks /cache/digest.last against DIGEST_MIN_HOURS (default 20 hours): when the previous post is less than 20 hours old, it logs the age and defers the comment to the next scheduled run so manual mid-day runs (which sent 9 extra digest emails on 2026-11-15/16 before the age gate was added) update pull requests silently. Setting DIGEST_FORCE=1 bypasses the age gate; DIGEST_DRY=1 prints the hash and body to stdout without posting.
  4. Single-issue subscription routing: when both gates pass, digest.sh posts a single comment on a dedicated open tracking issue. The repository owner unwatches all opted-in repositories (DELETE /api/v1/repos/<owner>/<repo>/subscription) and does not watch the config repository at the repository level (watching it also emails Renovate’s own self-update pull requests), subscribing only to the tracking issue via PUT /api/v1/repos/<owner>/<config-repo>/issues/<N>/subscriptions/<user>. Unwatching a stack repository does not suppress CI failure emails, because Forgejo sends Action failure notifications to the run’s triggering user or repository owner rather than watchers.

compose.yaml passes RENOVATE_GITHUB_COM_TOKEN, DOCKERHUB_TOKEN, and NOTIFICATION_TOKEN as optional environment variables (${VAR:-}), and run.sh explicitly unsets any variable that expands to an empty string before invoking renovate. On 2026-11-15 all three optional tokens were declined to avoid minting and rotating additional credentials:

  • RENOVATE_GITHUB_COM_TOKEN (unset): reusing a broad-scoped existing token was rejected because that token carries repo and write:packages scopes, far wider than a read-only release-notes lookup. Running without a github.com token means pull request bodies omit changelogs for GitHub-hosted upstreams and Renovate writes "WARN: No github.com token has been configured" into every repository’s Dependency Dashboard, which digest.sh filters out.
  • DOCKERHUB_TOKEN (unset): routing linuxserver/* tag lookups to ghcr.io avoids the anonymous Docker Hub 10-page tag listing cutoff without a Docker Hub Personal Access Token.
  • NOTIFICATION_TOKEN (unset): while unset, run.sh logs a notification-service-unavailable message on non-zero exit, and job failures surface through the renovate-daily pipeline run status in Composer.

scripts/ holds six helpers. Four wrap the Forgejo API (https://git.example.com/api/v1) for batch triage, pg-reindex-audit.sh runs the post-deploy PostgreSQL audit, and test-preset.sh is the preset regression test described below:

  • scripts/prstat.sh: enumerates all non-archived, non-mirror repositories, lists open renovate-bot pull requests, and queries /commits/<sha>/status to print repo#N | state (failing-contexts) | title.
  • scripts/merge.sh repo#N...: verifies the pull request is open and its commit status state is success or empty (""), reads the repository’s default_merge_style, and posts to /pulls/<n>/merge with delete_branch_after_merge: true.
  • scripts/tick-rebase.sh repo#N...: patches - [ ] <!-- rebase-check --> to - [x] <!-- rebase-check --> in the pull request body so the next Renovate run recreates the branch; on Forgejo 17+, failed workflow runs can also be retried in place with fjctl run rerun <owner/repo> <run> --failed.
  • scripts/red-mains.sh: checks both default-branch commit statuses and /actions/runs created within the last 24 hours ($SINCE) for status=="failure", catching scheduled and workflow_dispatch runs that do not attach a commit status.
  • scripts/pg-reindex-audit.sh <ssh-host> <container> <user>: connects to every non-template database in a PostgreSQL container and queries pg_index, pg_class, and pg_opclass for gist_trgm_ops indexes or bpchar_ops / bpchar_pattern_ops indexes on unconstrained bpchar columns (atttypmod IS NULL OR atttypmod = -1), matching the PostgreSQL 18.7 minor release advisory.
  1. Green pull request CI does not guarantee the Docker image builds: stacks without CI workflows (the shell-history, photo-library, media-server, task-board, Renovate, password-manager, monitoring, change-detection, and LLM-gateway stacks) report an empty commit status (""), and some application repositories run unit tests on pull requests but only build Docker images on push to main (a web-research stack builds its images on main behind a Trivy scan before its deploy job). For base-image bumps on those repositories, verify the image build locally before merging:
    Terminal window
    tmp=$(mktemp -d)
    git archive origin/<renovate-branch> | tar -x -C "$tmp"
    docker build "$tmp"
  2. Single-runner queue saturation: merging ~30 pull requests at once on 2026-11-15 flooded the single Forgejo Actions runner and caused Playwright, testcontainers, and 300-second Docker-build end-to-end jobs to time out. Merge in small batches of a few repositories, and rerun any timeout once the runner queue is empty before treating it as a regression.

Merging a Renovate pull request updates main, but how that commit reaches production depends on the repository’s deployment model:

Renovate PR mergedto main on the Forgejo instanceRepository deploy model?1. Composer push webhook(auto_sync + webhook > 0)-> SyncAndRedeploystandard Compose stack2. GitHub push webhook(CI host stack)-> redeploy when runner idleCI host stack3. CI deploy job on main(application repos)-> build + Trivy gate + deployCI-orchestrated stack4. Release tag only(release-gated services)-> cut vX.Y.Z tag to deployrelease-gated service5. Manual deploy(non-webhook stacks)-> sync / build / deploy via Composer CLIno webhook6. Job-image rebuild(profiled jobs services)-> deploy + build in Composerprofiled jobs service
  1. Composer push webhook (sync + up): standard Compose stacks (the shell-history, SSH docs, local-LLM research assistant, photo-library, media-server, task-board, monitoring, object-storage, password-manager, finance, and change-detection stacks) redeploy automatically via the Forgejo-to-Composer push webhook. Verify webhook wiring: setting auto_sync: true in Composer does nothing if webhooks=0 (four stacks had auto_sync: true with no webhook until the 2026-11-15 sweep audited them).
  2. GitHub push webhook (CI host stack): the Forgejo stack itself triggers its Composer webhook from the GitHub push mirror so a Forgejo outage cannot block recovery deploys, and must only be merged when the Actions runner is idle.
  3. CI deploy job on main (application repositories): pushing to main runs a Forgejo Actions workflow that builds first-party images, gates on Trivy (the web-research stack), and invokes Composer’s deploy script; bumps to a tag-pinned backup/Dockerfile in the session-history store also require cutting a release.
  4. Release tag only (release-gated services): merging a Dockerfile or gomod bump to main runs CI tests, but production deploys only when a release tag triggers release.yml ("Deploy via Composer", covered in Forgejo releases and container registry).
  5. Manual deploy (non-webhook stacks): repositories that intentionally omit a push webhook (a VM build stack, or stacks whose image is built locally on the host) require an explicit deploy via the Composer CLI after merge.
  6. Profiled job-image rebuild (Renovate and the companion infrastructure drift-check stack): when Renovate merges a self-update to its own Dockerfile FROM line, the stack must be synced and explicitly built because the Composer CLI build step skips services under profiles: ["jobs"]:
    Terminal window
    # sync + deploy, then build the profiled service
    <composer-cli> deploy <renovate-stack>
    <composer-cli> exec <renovate-stack> -- build <renovate-service>

Regression-testing the preset (scripts/test-preset.sh)

Section titled “Regression-testing the preset (scripts/test-preset.sh)”

Any edit to default.json can silently drop a package lookup or accidentally open an unapproved major pull request across 29 repositories. To test rule changes before building or deploying renovate-job:local, the repository carries fixtures/compose.yaml (12 representative services pinned to their pre-2026-11-13 tags; ignored during live runs via "ignorePaths": ["fixtures/**"] in renovate.json) and fixtures/expected.tsv:

# depName newValue must match (ERE); a leading ? means "if an update exists" dashboard approval (yes|no)
lscr.io/linuxserver/radarr ^6\.[0-9]+\.[0-9]+\.[0-9]+-ls[0-9]+$ no
linuxserver/bazarr ^v1\.[0-9]+\.[0-9]+-ls[0-9]+$ no
linuxserver/sonarr ?^4\.[0-9]+\.[0-9]+\.[0-9]+-ls[0-9]+$ no
linuxserver/jellyfin ^12\.[0-9]+ubu2604-ls[0-9]+$ no
binhex/arch-qbittorrentvpn ^5\.[0-9]+\.[0-9]+-[0-9]+-[0-9]+$ no
timescale/timescaledb-ha ^pg18\.6-ts2\.[0-9]+\.[0-9]+$ yes
pgsty/silo ^RELEASE\.20[0-9]{2}-[0-9]{2}-[0-9]{2}T00-00-00Z$ no
docker.io/searxng/searxng ^20[0-9]{2}\.[0-9]+\.[0-9]+-[0-9a-f]+$ no
valkey/valkey ^9\.[0-9]+\.[0-9]+-alpine$ yes
postgres ^18\.[0-9]+-alpine$ yes
redis ^8\.[0-9]+\.[0-9]+-alpine3\.23$ yes
ghcr.io/dgtlmoon/changedetection.io ^0\.60\.[0-9]+$ no
ghcr.io/dgtlmoon/changedetection.io ^0\.(6[1-9]|[7-9][0-9])\.[0-9]+$ yes

scripts/test-preset.sh mounts the working tree read-only into the upstream Renovate image (FROM line of Dockerfile), generates a temporary test.js that merges config.js with the local default.json while setting dryRun: 'full', requireConfig: 'ignored', schedule: [], and force: { ignorePaths: [], enabledManagers: ['docker-compose'] }, and captures JSON debug logs (LOG_LEVEL=debug, LOG_FORMAT=json) to run.jsonl:

  1. It verifies that Renovate processed the config repository with status: onboarded or status: activated.
  2. It extracts every proposed (depName, newValue, branchName) tuple for packageFile == "fixtures/compose.yaml" from the "packageFiles with updates" log entry, and extracts every branch name where "creation is disabled because dependencyDashboardApproval=true" fired.
  3. It checks all 13 rows in fixtures/expected.tsv (both 0.60.x un-gated patch and 0.61+ gated minor must appear simultaneously for changedetection.io, proving separateMinorPatch: true works).
  4. It fails if any proposal crosses a compatibility boundary (*sonarr:5.*, *timescaledb-ha:pg1[0-7]*, or non--alpine tags for valkey/valkey and postgres).
  1. Mend, “Regex Versioning,” Mend Renovate CLI Docs. https://docs.renovatebot.com/modules/versioning/regex/ ↩ ↩2 ↩3 ↩4

  2. Mend, “Dependency Dashboard,” Mend Renovate CLI Docs. https://docs.renovatebot.com/key-concepts/dashboard/ ↩ ↩2 ↩3

  3. Mend, “Automated Dependency Updates for Docker Compose,” Mend Renovate CLI Docs. https://docs.renovatebot.com/modules/manager/docker-compose/ ↩

  4. Mend, “Forgejo,” Mend Renovate CLI Docs. https://docs.renovatebot.com/modules/platform/forgejo/ ↩

  5. Mend, “Self-Hosted Configuration,” Mend Renovate CLI Docs. https://docs.renovatebot.com/self-hosted-configuration/ ↩

  6. Mend, “Shareable Config Presets: local presets,” Mend Renovate CLI Docs. https://docs.renovatebot.com/config-presets/#local-presets ↩