From 6007de6e418526bc01cb54d840d296f087766e10 Mon Sep 17 00:00:00 2001
From: Claude <claude@havari.me>
Date: Thu, 30 Apr 2026 13:09:26 +0300
Subject: [PATCH] =?UTF-8?q?tower=200.61.9=20=E2=80=94=20Phase=20I=20tenant?=
 =?UTF-8?q?-neutral=20export=20bundle?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Bundles now emit odoosky.export.v3 schema with a recipe sub-object
and explicit provenance section. The `source` field is dropped from
addon entries (the Phase I tenant leak we identified). Readers handle
both v2 and v3 schemas; v2 bundles in flight stay restorable but their
addon `source` field is silently ignored at restore time.

Phase I closes the export-bundle side of the cross-tenant data leak.
---
 values.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/values.yaml b/values.yaml
index d2afe8f..32ab882 100644
--- a/values.yaml
+++ b/values.yaml
@@ -9,7 +9,7 @@ backend:
     # so every cluster that runs Tower needs the same imagePullSecret
     # provisioned out-of-band (until cluster-platform-v3 owns it).
     repository: registry.odoosky.cloud/odoosky/docker-mirror/tower
-    tag: "0.61.8"
+    tag: "0.61.9"
     pullPolicy: IfNotPresent
   imagePullSecrets:
     - name: docker-mirror-pull