privatebin 2.0.5 -> 2.0.6: DRILL bump for the BIGNIGHT guarded-update walk (reverted in the same phase)

CHANGELOG.md

@@ -12,6 +12,14 @@ still showed „Uploaded content"). The k3s service targets port 80 for the same
 frontend's `/api` and `/auth` proxy stays as it is — that is also the k3s shape. Nothing else differed
 (`PUBLIC_URL`, `CSRF_TRUSTED_ORIGINS`, `ORIGIN`, `BODY_SIZE_LIMIT` all match). No version moved.
 
+## privatebin 2.0.5 → 2.0.6 — a DRILL bump, reverted in the same phase (2026-09-14, BIGNIGHT Phase 4)
+
+A real upstream one-step release (`privatebin/pdo:2.0.6`, Docker Hub 2026-08-08), pushed so the guarded
+Update could be walked end to end on the big night's test box (no app in the catalog had a newer version).
+`catalog_since` set to 2026-09-14 per the rule. **The revert commit follows in the same phase**; nothing
+in the fleet is meant to keep 2.0.6 from this commit. Evidence:
+`felhom.eu/documentation/audits/evidence-bignight-2026-09-14/phase4/`.
+
 ## catalog-since gate: an image move must bump catalog_since (2026-09-13, R-452)
 
 `scripts/check-catalog-since.py`, fifth gate in `catalog_gates.py` (fast, git-history, `--range A..B`

templates/privatebin/.felhom.yml

@@ -10,7 +10,7 @@ subdomain: "paste"
 slug: "privatebin"
 # catalog_since: the date THIS repo last changed this app's pinned images. Any commit that
 # changes an image: line must set this to the same day (see CLAUDE.md).
-catalog_since: "2026-07-18"
+catalog_since: "2026-09-14"
 
 # --- Resource hints (displayed on deploy screen) ---
 resources:

templates/privatebin/docker-compose.yml

@@ -8,7 +8,7 @@
 
 services:
   privatebin:
-    image: privatebin/pdo:2.0.5
+    image: privatebin/pdo:2.0.6
     container_name: privatebin
     restart: unless-stopped
     environment: