fix(release): bump version to 1.0.2 and number pre-releases from releases

package.json was at 0.2.0 while v1.0.1 is already published, so the
Pre-release workflow computed v0.2.0-pre.N behind the live release line and
collided with v0.2.0-pre.1 (permanently burned in the immutable-release
ledger). Bump to 1.0.2 so pre-releases lead the next patch, and derive the
next pre-release number from the releases list (incl. drafts + immutable)
instead of git tags, which never materialize under immutable releases.

Author: bakerboy448

.github/workflows/prerelease.yml

@@ -42,14 +42,21 @@ jobs:
         id: prerelease
         env:
           BASE_VERSION: ${{ steps.version.outputs.version }}
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          REPO: ${{ github.repository }}
         run: |
-          LATEST=$(git tag -l "v${BASE_VERSION}-pre.*" --sort=-version:refname | head -n1)
+          # Derive the next number from existing RELEASES (incl. drafts + already
+          # published immutable releases), NOT git tags. Under immutable releases a
+          # pre-release tag can be permanently reserved in the release ledger while
+          # never materializing as a git ref, so git-tag-based numbering collides on
+          # the same number every run. The releases list always reflects burned tags.
+          LATEST=$(gh api "repos/${REPO}/releases" --paginate \
+            --jq ".[].tag_name | select(startswith(\"v${BASE_VERSION}-pre.\"))" \
+            | sed "s|^v${BASE_VERSION}-pre.||" | sort -n | tail -n1)
           if [ -z "$LATEST" ]; then
             NUM=1
           else
-            PREFIX="v${BASE_VERSION}-pre."
-            NUM="${LATEST#"$PREFIX"}"
-            NUM=$((NUM + 1))
+            NUM=$((LATEST + 1))
           fi
           TAG="v${BASE_VERSION}-pre.${NUM}"
           echo "tag=$TAG" >> "$GITHUB_OUTPUT"

package.json

@@ -1,6 +1,6 @@
 {
   "name": "docker-compose-debugger",
-  "version": "0.2.0",
+  "version": "1.0.2",
   "description": "Browser-based Docker Compose debugger — redacts secrets, shows service cards, and generates markdown tables for support channels",
   "type": "module",
   "scripts": {