From ad573406a512f54739fa87467ff8c2340fae4c68 Mon Sep 17 00:00:00 2001
From: MeepMr <67143880+MeepMr@users.noreply.github.com>
Date: Thu, 17 Sep 2026 00:39:05 +0200
Subject: [PATCH] probe: cyberchef only, to separate resource contention from
 the rest

The two-leg run on Gitea left the cyberchef pod Pending with no node and
no scheduling event, while its k3s node logged a Starting event 17s
after the deployment was created - the node restarted under it. Two k3s
clusters share one runner container there (6 CPU / 12Gi per #227),
where on GitHub two legs are two VMs. A single leg, repeated, tells
contention apart from a real fault.
---
 freesailarr/Chart.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/freesailarr/Chart.yaml b/freesailarr/Chart.yaml
index dff2fcc..a7801e2 100644
--- a/freesailarr/Chart.yaml
+++ b/freesailarr/Chart.yaml
@@ -8,7 +8,7 @@ description: A Helm chart to deploy a Wireguard-tunneled media automation stack
 
 type: application
 
-version: 3.0.6+up1.0.0
+version: 3.0.5+up1.0.0
 # The chart's own version marker, freely chosen and tied to no upstream. The
 # stack bundles nine independently versioned projects, so there is no single
 # "app version" to track here.