Repository navigation
ci: check images resolve, the stack boots and databases keep their data - #8
Merged
Merged
Conversation
dominics
force-pushed
the
ci/pr-checks
branch
7 times, most recently
from
November 14, 2026 14:49
09a24dc to
ed59eda
Compare
Renovate's pull requests arrived with no checks. Six jobs on hosted runners now say whether an image bump is safe to deploy: the compose files parse, each tag and digest exists with an amd64 build, the Dockerfiles build, the main stack and Immich boot on empty volumes and Traefik routes as configured, and each Postgres opens a data directory written by the image it replaces.
dominics
force-pushed
the
ci/pr-checks
branch
from
November 14, 2026 14:49
ed59eda to
95665c4
Compare
dominics
marked this pull request as ready for review
November 14, 2026 14:54
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 LLM generated description follows
What this adds
Renovate's pull requests here have had no checks at all. This adds one workflow,
.github/workflows/ci.yml, with six jobs that run onpull_requestand on pushes tomain. Most changes to this repository are an image tag or digest moving, so the jobs are about images: does the reference exist, does the container boot, does Traefik still route, does a database still open its data.It runs on hosted
ubuntu-latestrunners, not the ones inci-runner/. The repository is public, so hosted minutes are free, and a self-hosted runner would run a fork's pull request on dagger. No secrets are used:.github/ci/dummy-envwrites the.envfiles from.env.examplewith placeholders.Jobs
composedocker compose configaccepts each compose file in the repository (root,immich/,ci-runner/) with a.envbuilt from.env.example. A required variable added to a compose file but not to.env.examplefails here.imagesbuildDockerfilein the repository builds (today that isci-runner/Dockerfile).smoke:80redirects to https,www.statio.nzpasses geoblock and redirects to the bare name, the AIOStreams route answers 403 from outside the allowlist, and/replays/reaches the td-replays nginx through the docker provider.smoke-immich/api/server/ping, which it only does after reaching both and running its migrations.upgradeJob names are stable and can be made required checks as they are.
Evidence that it fails when it should
Throwaway commits were pushed to this branch and removed again; the runs remain.
imagesfails: "the pinned digest does not resolve".smokefails too, at the pull. (run)dynamic.yml: the aiostreams router namestailscale-onylsmokefails twice over: Traefik's API reportsaiostreams@filewithmiddleware "tailscale-onyl@file" does not exist, and the route answers 404 where 403 is expected. The other five jobs pass. (run)upgradeandsmokefail, see below. (run)The first green run also only passed
smoke-immichby winning a race (the server starting before Postgres was ready and being restarted); a later run lost it. The script now starts the database first, and that job has passed on all runs since.What it says about the open Renovate PRs
Each PR's commit was cherry-picked onto this branch and run through the workflow. The PRs themselves will show checks once this merges and they rebase.
upgradeandsmoke.upgrade: "postgres:18-alpine does not start on a data directory written by postgres:17-alpine" (job).smokefails as well (job): the 18 image refuses to start with a volume mounted at/var/lib/postgresql/dataand wants it at/var/lib/postgresql, so ryot-db never becomes healthy and Ryot never starts. So #7 needs the mount moved in the compose file as well as apg_upgradeor dump and restore of the live data; the image bump alone would take Ryot down.The
imagesjob also notes, as warnings, thatnginx:alpinehas moved on from its pinned digest; Renovate has no PR open for that one yet.What it cannot catch
dominics/tdand this repository's token cannot read it, soimagesskips it andsmokedoes not start it. Thetraged@dockerrouter is therefore never built in CI. Granting this repository read access to the package (Package settings -> Manage Actions access) would close that, with no new secret.AWS_*credentials are untested, and routes are exercised on Traefik's default certificate.upgradejob proves Postgres opens the old data directory, not that Ryot's or Immich's migrations succeed against years of rows.runtime: runcin CI, so the nvidia runtime and hardware transcoding are untested.192.168.1.200:8181), reddit behind redlib, usenet behind nzbdav, TMDB behind Ryot: none is reached. redlib is held only to "nginx answered".images.deploy-dagger,tailscale/apply-serveand thetraged/scripts are not run or linted, and neither is the Home Assistant config.smokefor reasons that have nothing to do with the change.🤖 Generated with Claude Code