feat: sparkyfitness v0.16.6.3 -> v0.16.8 + handle versioning scheme change #87
Reference in New Issue
Block a user
Delete Branch "feat/sparkyfitness-v0.16.8"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
codewithcj changed sparkyfitness versioning on 2026-06-01 (4-segment
vX.Y.Z.W-> 3-segmentvX.Y.Z). Our version-checker regex^v\d+\.\d+\.\d+\.\d+$filtered out the new v0.16.7 / v0.16.8 tags, leaving only older 4-segment ones to pick as "newest" -- producing the bogus "upgrade to an older version" display.Bump both images from v0.16.6.3 to v0.16.8 (actual upstream latest) and loosen the regex to accept both schemes.
🤖 Generated with Claude Code
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>