From 2775e5d8507dc6d13fdd2a52db7560a2cf86381b Mon Sep 17 00:00:00 2001
From: MeepMr <67143880+MeepMr@users.noreply.github.com>
Date: Thu, 17 Sep 2026 00:14:03 +0200
Subject: [PATCH] probe: single chart, to isolate whether k3s boots at all

Both charts in the matrix collide: Gitea runs the legs CONCURRENTLY in
one job on one Docker daemon, and both create a cluster named
install-test. One leg logs 'Re-using existing network', the other
'container name /k3d-install-test-server-0 is already in use', and the
first rollback deletes the shared network under the second.

The workflow is still byte-identical to PR #253 - only cyberchef is
bumped now, which is the single-leg case most PRs actually produce, and
the only way to see whether k3s itself comes up.
---
 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.