privatebin 2.0.6 -> 2.0.5: revert the BIGNIGHT drill bump (d5d91e0) in the same phase

2026-09-14 21:17:55 +02:00
parent d5d91e09a0
commit a161ccb918
2 changed files with 9 additions and 1 deletions
@@ -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