Merge pull request 'feat: sparkyfitness v0.16.6.3 -> v0.16.8 + handle versioning scheme change' (#87) from feat/sparkyfitness-v0.16.8 into main

codewithcj changed sparkyfitness versioning on 2026-06-01:
  - Old (through v0.16.6.3 / 2026-05-24): vMAJOR.MINOR.PATCH.BUILD
  - New (from v0.16.7 / 2026-06-01)      : vMAJOR.MINOR.PATCH

Our version-checker regex was `^v\d+\.\d+\.\d+\.\d+$` (4 segments
only), so the new v0.16.7 / v0.16.8 tags were invisible to it. The
"newest matching" became an arbitrarily-chosen old 4-segment tag
(v0.16.5.9 in the latest scan), which then showed up as an "upgrade
to an older version" -- nonsense, but predictable given the filter.

Two changes:
  1. Bump both `codewithcj/sparkyfitness` (frontend) and
     `codewithcj/sparkyfitness_server` (backend) from v0.16.6.3 to
     v0.16.8 (the actual upstream latest).
  2. Loosen the regex to `^v\d+\.\d+\.\d+(\.\d+)?$` so it matches
     both the legacy 4-segment form and the new 3-segment form.
     Once everything's on 3-segment we can tighten it again if we
     want, but the current form is harmless.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

admin-system/renovate.yaml

@@ -149,7 +149,6 @@ data:
             "linuxserver/sonarr"
           ],
           "enabled": false
-        },
         }
       ],
       "labels": ["renovate"]

workout-system/sparkyfitness.yaml

@@ -144,8 +144,10 @@ spec:
         app.kubernetes.io/instance: sparkyfitness
         app.kubernetes.io/name: server
       annotations:
-        # Tag format is vMAJOR.MINOR.PATCH.BUILD (e.g. v0.16.6.3)
-        match-regex.version-checker.io/server: '^v\d+\.\d+\.\d+\.\d+$'
+        # Tag format used to be vMAJOR.MINOR.PATCH.BUILD (e.g. v0.16.6.3),
+        # changed to vMAJOR.MINOR.PATCH on 2026-06-01 (v0.16.7+). Accept
+        # both so historical comparisons + new releases both match.
+        match-regex.version-checker.io/server: '^v\d+\.\d+\.\d+(\.\d+)?$'
     spec:
       enableServiceLinks: false
       securityContext:
@@ -166,7 +168,7 @@ spec:
               echo "PostgreSQL is ready!"
       containers:
         - name: server
-          image: codewithcj/sparkyfitness_server:v0.16.6.3
+          image: codewithcj/sparkyfitness_server:v0.16.8
           env:
             # ---- Database (owner / superuser role, used for migrations) ----
             - name: SPARKY_FITNESS_DB_HOST
@@ -330,12 +332,12 @@ spec:
         app.kubernetes.io/instance: sparkyfitness
         app.kubernetes.io/name: frontend
       annotations:
-        match-regex.version-checker.io/frontend: '^v\d+\.\d+\.\d+\.\d+$'
+        match-regex.version-checker.io/frontend: '^v\d+\.\d+\.\d+(\.\d+)?$'
     spec:
       enableServiceLinks: false
       containers:
         - name: frontend
-          image: codewithcj/sparkyfitness:v0.16.6.3
+          image: codewithcj/sparkyfitness:v0.16.8
           env:
             - name: SPARKY_FITNESS_SERVER_HOST
               value: "sparkyfitness-server"