From a004e6167cb6ce68eb5013867c6046c758fe13ab Mon Sep 17 00:00:00 2001
From: stxkxs <139715017+stxkxs@users.noreply.github.com>
Date: Sat, 8 Aug 2026 14:02:37 -0700
Subject: [PATCH] docs: pin the operator chart whose README is not wrong
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

0.6.5 is a documentation-only release. Its rendered manifests are identical to
0.6.4's — 34 changed lines against this repo's production values, all of them
the helm.sh/chart label.

The pin moves anyway, because the pinned version is also the pointer to the
chart's documentation. 0.6.4's README carries an `### operator SLO (slo.*)`
section describing values the chart removed at 0.6.0 and that its own
values.schema.json now rejects, so following it produces `additional properties
'slo' not allowed` rather than the alerting it promises. An OCI tag here is
immutable by policy — the release job refuses to overwrite a published version —
so those bytes are permanent, and anyone who inspects the chart this fleet
resolves reads them.

Correcting the README in source and leaving the fleet pinned a version behind it
would have left the defect exactly where it does harm: in the artifact a reader
actually reaches.
---
 applicationsets/addons-agent-operator.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/applicationsets/addons-agent-operator.yaml b/applicationsets/addons-agent-operator.yaml
index 8e62078..8376c40 100644
--- a/applicationsets/addons-agent-operator.yaml
+++ b/applicationsets/addons-agent-operator.yaml
@@ -60,7 +60,7 @@ spec:
         # charts in addons-ai-platform use.
         - repoURL: oci://ghcr.io/nanohype/eks-agent-platform/charts/operator
           chart: operator
-          targetRevision: 0.6.4
+          targetRevision: 0.6.5
           helm:
             # Matches the Application name above so Application == release ==
             # Deployment (eks-agent-platform-operator) — one fully-qualified name