Changelog — data corrections & upstream changes

Every change to published data, dated and sourced: our own corrections included, and upstream requirement changes as we detect them. No silent edits.

2026-07-24 — gitea: Verification: RAM/CPU figure source corrected — the quote lives on the docs home page (System Requirements), not /installation/comparison; quote restored to the literal sentence ending 'small teams/projects.' (seed had truncated it). Values unchanged. (source)
2026-07-24 — immich: Verification: redis dependency re-sourced to the official docker-compose.yml — the requirements page no longer mentions Redis/Valkey, but the compose file still runs a required redis service (valkey image). Dependency itself unchanged. (source)
2026-07-24 — home-assistant: Verification: RAM minimum quote replaced with the full literal bullet 'Raspberry Pi 4 or 5 with power supply (minimum 2 GB RAM)' — seed had an ellipsis-joined fragment. Value and scope unchanged. (source)
2026-07-24 — jellyfin: Verification: recommended-RAM quote replaced with the full literal sentences (seed paraphrase dropped the word 'running'); scope softened — the docs state no hard minimum but do not 'explicitly avoid' one. Value unchanged. (source)
2026-07-24 — frigate: Verification: added official RAM figures (4GB basic minimum, 16GB recommended) from the 'Planning a New Installation' page, which the harvest missed; recorded GHCR image size/arches for the :stable tag (no :latest tag exists); deps changed from none to ffmpeg (bundled, required). (source)
2026-07-24 — paperless-ngx: Verification: broker dependency restructured — docs require 'a Redis-compatible broker (a current release of Valkey or Redis)' and the official compose ships valkey, so valkey is listed required with redis as an accepted alternative (optional); filled GHCR image size/arches. (source)
2026-07-24 — frigate: QA: ffmpeg reclassified — it is bundled inside the official image, not an external service the operator runs; deps now 'none required'. (source)
2026-07-24 — jellyfin: QA: ffmpeg reclassified — jellyfin-ffmpeg ships with the server, not an external service; deps now 'none required'. (source)
2026-07-24 — adguard-home: QA: absence evidence_url replaced — discussion 7350 did not evidence the gap; now cites the official getting-started page that publishes no hardware figures. (source)
2026-07-27 — vaultwarden: AUDIT #1: docker.size_mb corrected 77→83 — the rolling `latest` tag rebuilt after harvest (real image change, not a fabrication). Retroactively logged 2026-07-30: this correction should have produced a changelog entry the day it was made and didn't. (source)
2026-07-30 — discourse: Re-QA: docker.size_mb corrected 1144→1173 — same rolling-`latest`-tag drift pattern as vaultwarden (AUDIT #1); flagged by independent re-QA, not self-caught. Figures/deps otherwise unchanged; status moved pending-second-qa→live. (source)
2026-08-03 — discourse: AUDIT #2: docker.size_mb corrected 1173→1144 — the `latest` tag was rebuilt again the morning of this audit (tag_last_pushed 2026-08-03T08:22Z); size reverted close to its original 1144 value. Third occurrence of this exact drift shape (vaultwarden AUDIT #1, discourse itself 2026-07-30) — see AUDIT.md for the structural finding. (source)
2026-08-03 — immich: AUDIT #2: docker.size_mb corrected 761→763 — minor rolling-`latest`-tag drift (image manifest re-summed from GHCR: 799608153 bytes = 762.57MiB). Same pattern as discourse/vaultwarden, smaller magnitude. (source)
2026-08-09 — linkwarden: Re-QA: source_url/evidence_url/sources_of_truth citing linkwarden/docs installation.md now 404 (repo restructured, page moved) — confirmed via live re-fetch; repointed to the new setup.md location where the same verbatim quote still lives. Value/quote unchanged; also tightened scope wording (hardware section precedes the Docker Compose/Manual Installation branch in official docs, so it reads as a general figure, not Docker-specific). (source)
2026-08-10 — discourse: AUDIT #3: docker.size_mb corrected 1144→1164 — `latest` tag rebuilt again the morning of this audit (Docker Hub tag_last_pushed 2026-08-10T07:10Z, ~1.5h before this check). Fourth occurrence of this exact drift shape on this field (AUDIT #1 vaultwarden, 2026-07-30 discourse, AUDIT #2 discourse) — see AUDIT.md for the structural finding on discourse's rebuild frequency specifically. (source)
2026-08-10 — n8n: AUDIT #3: docker.size_mb corrected 363→362 — rolling-`latest`-tag drift (Docker Hub amd64 layer sum 379794039 bytes = 362.20MiB, tag_last_pushed 2026-08-07). First recorded drift for this field. (source)
2026-08-10 — rocket-chat: AUDIT #3: docker.size_mb corrected 295→296 — rolling-`latest`-tag drift (Docker Hub amd64 layer sum 310338149 bytes = 295.96MiB, tag_last_pushed 2026-08-07). First recorded drift for this field. (source)
2026-08-10 — home-assistant: AUDIT #3: docker.size_mb corrected 594→590 — rolling-`latest`-tag drift (GHCR amd64 manifest re-summed: 618150752 bytes = 589.51MiB). First recorded drift for this field. (source)
2026-08-17 — discourse: AUDIT #4: docker.size_mb corrected 1164→1250 — rolling-`latest`-tag drift (Docker Hub amd64 layer 1310370993 bytes = 1250.03MiB, tag_last_pushed 2026-08-17T00:04Z, minutes before this check). 6th recorded drift on this field — this image rebuilds unusually often. (source)
2026-08-17 — home-assistant: AUDIT #4: docker.size_mb corrected 590→625 — rolling-`latest`-tag drift (GHCR amd64 manifest re-summed: 655436525 bytes = 625.00MiB). 3rd recorded drift on this field. (source)
2026-08-17 — mattermost: AUDIT #4: docker.size_mb corrected 438→441 — rolling-`latest`-tag drift (Docker Hub amd64 layer 462562076 bytes = 441.12MiB, tag_last_pushed 2026-08-04). First recorded drift for this field. (source)
2026-08-17 — n8n: AUDIT #4: docker.size_mb corrected 362→346 — rolling-`latest`-tag drift (Docker Hub amd64 layer 362818469 bytes = 346.02MiB, tag_last_pushed 2026-08-14). First recorded drift for this field since AUDIT #3's correction. (source)
2026-08-17 — openproject: AUDIT #4: docker.size_mb corrected 394→398 — rolling-`latest`-tag drift (Docker Hub amd64 layer 417707610 bytes = 398.32MiB, tag_last_pushed 2026-08-13). First recorded drift for this field. (source)
2026-08-17 — nextcloud: AUDIT #4: docker.size_mb corrected 526→530 — rolling-`latest`-tag drift (Docker Hub amd64 layer 555244112 bytes = 529.62MiB, tag_last_pushed 2026-08-14). First recorded drift for this field. (source)
2026-08-17 — wazuh: AUDIT #4: docker.image repointed from bare `wazuh/wazuh-manager` (implies `:latest`, which Wazuh has never published on Docker Hub — a literal `docker pull` on our citation would fail) to the explicit `:4.14.7` tag actually current at harvest time. size_mb (864) unchanged — confirmed it already matched the :4.14.7 manifest exactly. New Defect Class #14. (source)
2026-08-17 — immich: AUDIT #4: docker.image repointed from bare `ghcr.io/immich-app/immich-server` (implies `:latest`, which does not exist on GHCR for this image) to the explicit `:release` tag — already known from Frigate's `:stable` precedent but never back-applied to this entry. size_mb (763) unchanged, live-confirmed exact match. New Defect Class #14. (source)
2026-08-24 — linkwarden: AUDIT #5: quote drift — docs/self-hosting/setup.md was rewritten since the 2026-08-09 re-QA (which had confirmed 'the same verbatim quote still lives' at this URL); the anecdotal "tested on a VPS with 4gb of memory" prose is gone, replaced by a formal Hardware Requirements list. Quote re-sourced to the new literal line ('**Memory:** 4 GB is a comfortable starting point.'); ram_rec_mb value (4096) unchanged — coincidentally still accurate. Scope note updated to drop the now-false "informal/anecdotal" characterization. Also noted: the new list publishes a CPU figure ('any 2 core machine') that didn't exist in the old prose — not harvested here (AUDIT doesn't self-grade new figures); flagged to backlog for next BUILD's harvest+verify pass. (source)
2026-08-24 — keycloak: AUDIT #5: docker.size_mb drift 258→255 — rolling `:latest` tag repush (Docker Hub amd64 layer sum, tag_last_pushed 2026-08-21, 9 days after our 2026-08-12 retrieval). (source)
2026-08-24 — chatwoot: AUDIT #5: docker.size_mb drift 685→642 — rolling `:latest` tag repush (Docker Hub amd64 layer sum, tag_last_pushed 2026-08-19, 17 days after our 2026-08-02 retrieval; largest single drift recorded on this field to date). (source)
2026-08-24 — discourse: AUDIT #5: docker.size_mb drift 1250→1255 — 7th recorded drift on this field (the most volatile in the dataset); Docker Hub tag_last_pushed 2026-08-24T00:05, hours before this check. (source)
2026-08-24 — gitlab-ce: AUDIT #5: docker.size_mb drift 1313→1382 — rolling `:latest` tag repush (Docker Hub tag_last_pushed 2026-08-20, 8 days after our 2026-08-12 retrieval). (source)
2026-08-24 — grafana: AUDIT #5: docker.size_mb drift 361→452 (+25%, largest relative drift recorded on this field) — this was the 2026-07-24 bootstrap entry, never re-verified since launch; Docker Hub tag_last_pushed 2026-08-18. (source)
2026-08-24 — n8n: AUDIT #5: docker.size_mb drift 346→356 — rolling `:latest` tag repush (Docker Hub tag_last_pushed 2026-08-21, 4 days after our 2026-08-17 retrieval; 3rd recorded drift on this field). (source)
2026-08-24 — linkwarden: AUDIT #5: docker.size_mb drift 496→499 — rolling `:latest` tag repush (GHCR amd64 manifest, our 2026-07-30 retrieval). (source)
2026-08-31 — discourse: AUDIT #6: docker.size_mb drift 1255→1259 — 8th recorded drift on this field (the most volatile in the dataset); Docker Hub tag_last_pushed 2026-08-31T00:06, hours before this check. (source)
2026-08-31 — nextcloud: AUDIT #6: docker.size_mb drift 530→527 — rolling `:latest` tag repush (Docker Hub tag_last_pushed 2026-08-29, 12 days after our 2026-08-17 retrieval). Also restored ram_min_mb/ram_rec_mb quote's markdown bold markers around the two figures ('**128MB**'/'**512MB**'), silently stripped at original harvest — same quote-formatting-fidelity class as AUDIT #5's chatwoot/openproject/seafile/plausible-ce fixes (Defect Class #8); value/scope unchanged. (source)
2026-08-31 — n8n: AUDIT #6: docker.size_mb drift 356→360 — rolling `:latest` tag repush (Docker Hub tag_last_pushed 2026-08-31, 7 days after our 2026-08-24 retrieval; 4th recorded drift on this field). (source)
2026-08-31 — coolify: AUDIT #6: docker.size_mb drift 130→134 — rolling `:latest` tag repush (Docker Hub tag_last_pushed 2026-08-28, 12 days after our 2026-08-16 retrieval). (source)