From a161ccb918610f8ceffe03b7175c625d4b7e9556 Mon Sep 17 00:00:00 2001 From: kisfenyo Date: Mon, 14 Sep 2026 21:17:55 +0200 Subject: [PATCH] privatebin 2.0.6 -> 2.0.5: revert the BIGNIGHT drill bump (d5d91e0) in the same phase --- CHANGELOG.md | 8 ++++++++ templates/privatebin/docker-compose.yml | 2 +- 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index e76c102..f3e50d3 100644 --- a/CHANGELOG.md +++ b/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.6 → 2.0.5 — the DRILL bump REVERTED (2026-09-14, BIGNIGHT Phase 4) + +Reverts `d5d91e0` in the same phase, as the drill required. The catalog is back on `privatebin/pdo:2.0.5`. +`catalog_since` stays 2026-09-14 because the `catalog-since` gate requires an image move to carry the day of the +move. The drill box (VM 333) keeps 2.0.6 — its guarded Update pinned it — and is torn down at the end of the night. +What the walk proved: the change reached the box on the next 15-minute sync (14 m 25 s after the push), the page +offered „Frissítés elérhető — ma", and the guarded Update finished in 11 s with the data intact. + ## 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 diff --git a/templates/privatebin/docker-compose.yml b/templates/privatebin/docker-compose.yml index 685cf2c..7229316 100644 --- a/templates/privatebin/docker-compose.yml +++ b/templates/privatebin/docker-compose.yml @@ -8,7 +8,7 @@ services: privatebin: - image: privatebin/pdo:2.0.6 + image: privatebin/pdo:2.0.5 container_name: privatebin restart: unless-stopped environment: