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.envedit (4 updates). - Inlined global preset, zero-commit opt-in:
default.jsonis inlined intoconfig.jsviarequire('./default.json')rather thanglobalExtends, and repositories opt in through therepositoriesarray inconfig.jsso onboarding a stack does not require arenovate.jsoncommit that would trigger its CI and deploy pipeline. - Registry and versioning workarounds: three-part LinuxServer tags (
v1.6.2-ls372) must maplsNNto the regexbuildgroup because Renovate ignoresrevisionwhenbuildis absent1;linuxserver/*lookups are routed toghcr.io(1,000 pages) because anonymous Docker Hub tag paging returns HTTP403at page 11. - Dashboard approval for high-blast-radius changes: all major bumps,
0.xminor bumps (separateMinorPatch: true), language-runtime minor bumps, databases, caches, and the Forgejo CI host stack (codeberg.org/forgejo/forgejoanddata.forgejo.org/forgejo/runner) wait on the per-repository Dependency Dashboard until ticked2. - One email per changed run:
digest.shaggregates 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_TOKENonly.RENOVATE_GITHUB_COM_TOKEN,DOCKERHUB_TOKEN, andNOTIFICATION_TOKENare unset by choice; pull requests omit GitHub-hosted release notes, anddigest.shstrips the resulting"No github.com token has been configured"warning.
Architecture and daily execution flow
Section titled “Architecture and daily execution flow”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:
- A photo-library stack reads its live version from
IMMICH_VERSIONinside a SOPS-encrypted.envfile whiledocker-compose.ymlonly holds the${IMMICH_VERSION:-vX}fallback default. timescale/timescaledb-ha(pg18.6-ts2.31.0 -> pg18.6-ts2.32.0) required runningALTER EXTENSION timescaledb UPDATEin both the application database and thepostgresdatabase after container start.- Six PostgreSQL
18.7upgrades carried release-note advisories to audit andREINDEXbtree indexes on unconstrainedbpcharcolumns andgist_trgm_opsindexes. - 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.
| Approach | GitOps compatibility | Tag ordering and suffix awareness | Operator review point | Decision |
|---|---|---|---|---|
Self-hosted Renovate (compose_run pipeline) | Opens pull requests against pinned tags in Git; merge triggers the normal Forgejo-to-Composer webhook flow | Built-in docker-compose3, dockerfile, and custom.regex managers; regex versioning with compatibility groups1 | Per-update pull request with prBodyNotes plus Dependency Dashboard approval checkboxes2 | Picked |
Watchtower auto-pull / pipeline compose_pull | Fights pinned tags (radarr:6.4.4.10685-ls326); pulling :latest mutates runtime state outside Git | None beyond registry tag equality | None | Rejected: bypasses Git and cannot express post-deploy SQL or SOPS steps |
| Diun notifications | Detects registry updates without changing what runs | Registry tag comparison | Notification only | Rejected: opens no pull request and carries no post-deploy steps |
Custom oci_tags script | Would have to generate branches and pull requests via the Forgejo API | Would re-implement -alpine suffix matching, LinuxServer -lsNN ordering, and 0.x semver rules from scratch | Only if custom pull request and dashboard logic were also built | Rejected: duplicates Renovate’s datasource and versioning engine |
| Forgejo Actions scheduled workflow | Same pull request output as compose_run | Same Renovate engine | Same pull request and dashboard output | Rejected: runs on the Forgejo Actions runner inside the CI host it proposes updates for, competing with build jobs |
How repositories opt in
Section titled “How repositories opt in”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:
- Bot permissions and repository units: the non-admin Forgejo user
renovate-botis added as a collaborator withwriteaccess (the minimum required to pushrenovate/*branches and open pull requests), and the repository’shas_pull_requestsandhas_issuesunits are enabled viaPATCH /api/v1/repos/<owner>/<repo>4. Repositories originally converted from GitHub mirrors had pull requests disabled in Forgejo; whenhas_pull_requestsis off, Renovate logs"Repo has disabled pull requests"and skips the repository. - Global
repositoriesallowlist inconfig.js:config.jssetsplatform: 'forgejo',endpoint: 'https://git.example.com/api/v1/',onboarding: false,autodiscover: false, andrequireConfig: 'optional'5. Opting in is an entry in therepositoriesarray inconfig.jsrather than arenovate.jsoncommit in each stack repository, because committing a configuration file to an application repository would fire its CI workflow and build-and-deploy pipeline. - 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 ownrenovate.jsonon top of the global configuration: a vulnerability-sweep CLI and a sibling Go CLI repository setenabledManagersto includegomodin their per-repositoryrenovate.jsonso 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:
| Gotcha | Observed failure mode | Fix in config.js, default.json, or target repositories |
|---|---|---|
globalExtends with a local> preset | Setting globalExtends: ['local>config-repo/renovate'] in config.js fails immediately with config-presets-invalid because Renovate resolves global presets before initialising the Forgejo platform client | Inline require('./default.json') into config.js after deleting $schema and description, and bake default.json into the job image |
Inlined ignorePaths and digest.enabled | When default.json is spread into global config.js, top-level ignorePaths and manager-level digest.enabled are silently ignored | Express both as packageRules: disable matchUpdateTypes: ["digest"] and disable matchFileNames: ["**/archive/**"] |
| LinuxServer three-part vs four-part tags | Four-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 absent1 | Split 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 pages | Route 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 suffixes | Without 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.0 | Use 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 updates | Under 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 patches | Set separateMinorPatch: true on matchCurrentVersion: "/^v?0\\./" and apply dependencyDashboardApproval: true only to matchUpdateTypes: ["minor"] |
Flow-style Compose mappings and ARG-indirected FROM lines | Flow-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 it | Format 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.ymlwritesimage: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-v3.4.1}andimmich-machine-learning:${IMMICH_VERSION:-v3.4.1}, while the live value comes from SOPS.env. AcustomManagersregex rule extractsdepNameandcurrentValuefrom the${IMMICH_VERSION:-v...}default, and apackageRulesentry groups both images undergroupName: "immich"withprBodyNotesinstructing the operator to update the SOPS-encrypted.envon the branch before merging. - First-party and undeployed files: private images published by their own repositories’ CI workflows are disabled in
packageRules(enabled: falseprevents failed registry lookups from pollutingRepository 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 class | Matched packages / update types | Dashboard approval required? | Attached prBodyNotes or constraint |
|---|---|---|---|
Routine application patches and 1.x+ minors | LinuxServer apps (radarr, bazarr, sonarr, jellyfin), binhex/**, pgsty/silo, searxng/searxng, 0.x patches | No (opens pull request directly) | immich group notes the required SOPS .env update |
0.x minor updates | matchCurrentVersion: "/^v?0\\./" with matchUpdateTypes: ["minor"] (ghcr.io/dgtlmoon/changedetection.io) | Yes | Separated from 0.x patches via separateMinorPatch: true |
| Language runtime base images | python, golang, node, oven/bun (minor and major update types; patches open directly) | Yes | Python 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 caches | postgres, pgvector/pgvector, timescale/timescaledb-ha, ghcr.io/immich-app/postgres, valkey/valkey, redis (all update types) | Yes | postgres 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 stack | codeberg.org/forgejo/forgejo, data.forgejo.org/forgejo/runner (all update types) | Yes | Notes require verifying the runner queue is empty and no job exceeds its normal duration before merging |
| Major updates across all packages | matchUpdateTypes: ["major"] | Yes | Prevents 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:
- Cross-repository collection:
digest.shqueries/api/v1/user/repos?limit=50usingRENOVATE_TOKEN, iterates over every non-archived repository in sorted order, and fetches open pull requests authored byrenovate-botplus the body of each repository’s open"Dependency Dashboard"issue. - Markdown extraction and noise filtering: from each Dependency Dashboard body,
awkandsedextract 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". - Content-hash and 20-hour rate gates: the assembled Markdown body is hashed with
sha256sumand compared against/cache/digest.sha256. If the hash matches the previous post, or if the body is empty (sum=empty),digest.shrecords the state and exits0without posting. If the hash changed,digest.shchecks/cache/digest.lastagainstDIGEST_MIN_HOURS(default20hours): 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. SettingDIGEST_FORCE=1bypasses the age gate;DIGEST_DRY=1prints the hash and body to stdout without posting. - Single-issue subscription routing: when both gates pass,
digest.shposts 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 viaPUT /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.
Deliberate no-github-token decision
Section titled “Deliberate no-github-token decision”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 carriesrepoandwrite:packagesscopes, far wider than a read-only release-notes lookup. Running without agithub.comtoken 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, whichdigest.shfilters out.DOCKERHUB_TOKEN(unset): routinglinuxserver/*tag lookups toghcr.ioavoids the anonymous Docker Hub 10-page tag listing cutoff without a Docker Hub Personal Access Token.NOTIFICATION_TOKEN(unset): while unset,run.shlogs a notification-service-unavailable message on non-zero exit, and job failures surface through therenovate-dailypipeline run status in Composer.
Merging and how updates go live
Section titled “Merging and how updates go live”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 openrenovate-botpull requests, and queries/commits/<sha>/statusto printrepo#N | state (failing-contexts) | title.scripts/merge.sh repo#N...: verifies the pull request isopenand its commit status state issuccessor empty (""), reads the repository’sdefault_merge_style, and posts to/pulls/<n>/mergewithdelete_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 withfjctl run rerun <owner/repo> <run> --failed.scripts/red-mains.sh: checks both default-branch commit statuses and/actions/runscreated within the last 24 hours ($SINCE) forstatus=="failure", catching scheduled andworkflow_dispatchruns 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 queriespg_index,pg_class, andpg_opclassforgist_trgm_opsindexes orbpchar_ops/bpchar_pattern_opsindexes on unconstrainedbpcharcolumns (atttypmod IS NULL OR atttypmod = -1), matching the PostgreSQL 18.7 minor release advisory.
Two CI caveats during batch merges
Section titled “Two CI caveats during batch merges”- 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 tomain(a web-research stack builds its images onmainbehind 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" - 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.
How a merge goes live across the fleet
Section titled “How a merge goes live across the fleet”Merging a Renovate pull request updates main, but how that commit reaches production depends on the repository’s deployment model:
- 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: settingauto_sync: truein Composer does nothing ifwebhooks=0(four stacks hadauto_sync: truewith no webhook until the 2026-11-15 sweep audited them). - 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.
- CI deploy job on
main(application repositories): pushing tomainruns 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-pinnedbackup/Dockerfilein the session-history store also require cutting a release. - Release tag only (release-gated services): merging a
Dockerfileorgomodbump tomainruns CI tests, but production deploys only when a release tag triggersrelease.yml("Deploy via Composer", covered in Forgejo releases and container registry). - 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.
- Profiled job-image rebuild (Renovate and the companion infrastructure drift-check stack): when Renovate merges a self-update to its own
DockerfileFROMline, the stack must be synced and explicitly built because the Composer CLI build step skips services underprofiles: ["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]+$ nolinuxserver/bazarr ^v1\.[0-9]+\.[0-9]+-ls[0-9]+$ nolinuxserver/sonarr ?^4\.[0-9]+\.[0-9]+\.[0-9]+-ls[0-9]+$ nolinuxserver/jellyfin ^12\.[0-9]+ubu2604-ls[0-9]+$ nobinhex/arch-qbittorrentvpn ^5\.[0-9]+\.[0-9]+-[0-9]+-[0-9]+$ notimescale/timescaledb-ha ^pg18\.6-ts2\.[0-9]+\.[0-9]+$ yespgsty/silo ^RELEASE\.20[0-9]{2}-[0-9]{2}-[0-9]{2}T00-00-00Z$ nodocker.io/searxng/searxng ^20[0-9]{2}\.[0-9]+\.[0-9]+-[0-9a-f]+$ novalkey/valkey ^9\.[0-9]+\.[0-9]+-alpine$ yespostgres ^18\.[0-9]+-alpine$ yesredis ^8\.[0-9]+\.[0-9]+-alpine3\.23$ yesghcr.io/dgtlmoon/changedetection.io ^0\.60\.[0-9]+$ noghcr.io/dgtlmoon/changedetection.io ^0\.(6[1-9]|[7-9][0-9])\.[0-9]+$ yesscripts/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:
- It verifies that Renovate processed the config repository with
status: onboardedorstatus: activated. - It extracts every proposed
(depName, newValue, branchName)tuple forpackageFile == "fixtures/compose.yaml"from the"packageFiles with updates"log entry, and extracts every branch name where"creation is disabled because dependencyDashboardApproval=true"fired. - It checks all 13 rows in
fixtures/expected.tsv(both0.60.xun-gated patch and0.61+gated minor must appear simultaneously forchangedetection.io, provingseparateMinorPatch: trueworks). - It fails if any proposal crosses a compatibility boundary (
*sonarr:5.*,*timescaledb-ha:pg1[0-7]*, or non--alpinetags forvalkey/valkeyandpostgres).
Related docs
Section titled “Related docs”- Vigil fleet vulnerability sweep and CI gating - the companion security scanner that sweeps running container images across the fleet with Trivy, enriches findings with CISA KEV and FIRST EPSS, and tells the operator which Renovate updates fix exploitable CVEs
- Forgejo-primary fleet migration - how the repository fleet moved to Forgejo as primary and retired GitHub Dependabot
- Forgejo webhooks to Composer GitOps - the push webhook plumbing that turns a merged Renovate pull request into a stack deploy
- Composer GitOps Docker Compose manager - the stack controller and
compose_runpipeline engine that schedulesrenovate-daily - Self-hosted Forgejo on the router - the Forgejo instance hosting the repositories and the runner queue constraint
- Forgejo Actions runner - the single-runner architecture that motivates batching Renovate pull request merges
References
Section titled “References”-
Mend, “Regex Versioning,” Mend Renovate CLI Docs. https://docs.renovatebot.com/modules/versioning/regex/ ↩ ↩2 ↩3 ↩4
-
Mend, “Dependency Dashboard,” Mend Renovate CLI Docs. https://docs.renovatebot.com/key-concepts/dashboard/ ↩ ↩2 ↩3
-
Mend, “Automated Dependency Updates for Docker Compose,” Mend Renovate CLI Docs. https://docs.renovatebot.com/modules/manager/docker-compose/ ↩
-
Mend, “Forgejo,” Mend Renovate CLI Docs. https://docs.renovatebot.com/modules/platform/forgejo/ ↩
-
Mend, “Self-Hosted Configuration,” Mend Renovate CLI Docs. https://docs.renovatebot.com/self-hosted-configuration/ ↩
-
Mend, “Shareable Config Presets: local presets,” Mend Renovate CLI Docs. https://docs.renovatebot.com/config-presets/#local-presets ↩