fix: handle docker-v prefix in version tags

Added configurable prefix field to each component to properly handle
different tag formats. Docker/moby tags are formatted as docker-v29.0.1
while others use just v2.329.0.

Changes:
- Added prefix field to each component in COMPONENTS JSON
- Updated fetch step to extract and strip the appropriate prefix
- Docker now uses docker-v prefix, others use v
- Uses bash parameter expansion instead of tr
- More robust and handles any prefix format

This fixes the issue where Docker versions were not being parsed
correctly from moby/moby release tags.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: kratsg

.github/workflows/update-versions.yml

@@ -9,12 +9,14 @@ on:
 env:
   COMPONENTS: >-
     [
-      {"var": "RUNNER_VERSION", "repo": "actions/runner", "name": "Runner"},
+      {"var": "RUNNER_VERSION", "repo": "actions/runner", "name": "Runner",
+    "prefix": "v"},
       {"var": "RUNNER_CONTAINER_HOOKS_VERSION", "repo":
-    "actions/runner-container-hooks", "name": "Container Hooks"},
-      {"var": "DOCKER_VERSION", "repo": "moby/moby", "name": "Docker"},
-      {"var": "BUILDX_VERSION", "repo": "docker/buildx", "name": "Buildx"}
-    ]
+    "actions/runner-container-hooks", "name": "Container Hooks", "prefix": "v"},
+      {"var": "DOCKER_VERSION", "repo": "moby/moby", "name": "Docker", "prefix":
+    "docker-v"},
+      {"var": "BUILDX_VERSION", "repo": "docker/buildx", "name": "Buildx",
+    "prefix": "v"} ]
 
 jobs:
   update-versions:
@@ -48,9 +50,11 @@ jobs:
           echo "$COMPONENTS" | jq -c '.[]' | while read -r component; do
             VAR=$(echo "$component" | jq -r '.var')
             REPO=$(echo "$component" | jq -r '.repo')
-            LATEST=$(gh api repos/$REPO/releases -q '.[0].tag_name' | tr -d 'v')
+            PREFIX=$(echo "$component" | jq -r '.prefix')
+            TAG=$(gh api repos/$REPO/releases -q '.[0].tag_name')
+            LATEST="${TAG#$PREFIX}"  # Strip prefix from tag
             echo "LATEST_$VAR=$LATEST" >> $GITHUB_ENV
-            echo "Fetched $VAR: $LATEST from $REPO"
+            echo "Fetched $VAR: $LATEST from $REPO (tag: $TAG)"
           done
 
       - name: Update .env if needed

README.md

@@ -114,15 +114,23 @@ To add a new component for automated version tracking:
    env:
      COMPONENTS: >-
        [
-         {"var": "RUNNER_VERSION", "repo": "actions/runner", "name": "Runner"},
+         {"var": "RUNNER_VERSION", "repo": "actions/runner", "name": "Runner",
+       "prefix": "v"},
          {"var": "RUNNER_CONTAINER_HOOKS_VERSION", "repo":
-       "actions/runner-container-hooks", "name": "Container Hooks"},
-         {"var": "DOCKER_VERSION", "repo": "moby/moby", "name": "Docker"},
-         {"var": "BUILDX_VERSION", "repo": "docker/buildx", "name": "Buildx"},
+       "actions/runner-container-hooks", "name": "Container Hooks", "prefix":
+       "v"},
+         {"var": "DOCKER_VERSION", "repo": "moby/moby", "name": "Docker",
+       "prefix": "docker-v"},
+         {"var": "BUILDX_VERSION", "repo": "docker/buildx", "name": "Buildx",
+       "prefix": "v"},
          {"var": "NEW_COMPONENT_VERSION", "repo": "org/repo", "name": "Friendly
-       Name"} ]
+       Name", "prefix": "v"} ]
    ```
 
+   The `prefix` field specifies what to strip from the release tag to get the
+   version number (e.g., `v2.329.0` → `2.329.0`, or `docker-v29.0.1` →
+   `29.0.1`).
+
 3. **(Optional) Update README.md** to document the new component:
    - Add to the Configuration section's `.env` example
    - Add to the Versioning Concepts section with description