fix: resolve docs javadoc version from git tags

Ensure docs-pages checkout uses full history and fetches tags so gradle-jgitver can derive semantic versions instead of fallback 0.0.0-0.

Add a workflow guard that fails early when fallback version is resolved.

Author: Beowolve

.github/workflows/docs-pages.yml

@@ -19,6 +19,8 @@ jobs:
     steps:
       - name: Checkout
         uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
 
       - name: Set up Node.js
         uses: actions/setup-node@v4
@@ -34,6 +36,24 @@ jobs:
       - name: Set up Gradle
         uses: gradle/actions/setup-gradle@v4
 
+      - name: Fetch tags for jgitver
+        run: git fetch --force --tags
+
+      - name: Validate resolved version for JavaDoc
+        shell: bash
+        run: |
+          version="$(./gradlew --no-daemon -q :snapfx-core:properties | awk -F': ' '/^version:/ {print $2; exit}')"
+          if [ -z "${version}" ]; then
+            echo "::error::Could not resolve project version from Gradle properties."
+            exit 1
+          fi
+
+          echo "Resolved version: ${version}"
+          if [ "${version}" = "0.0.0-0" ]; then
+            echo "::error::Resolved fallback version 0.0.0-0. Ensure full git history and tags are available for gradle-jgitver."
+            exit 1
+          fi
+
       - name: Generate API JavaDoc
         run: ./gradlew --no-daemon :snapfx-core:javadoc
 

CHANGELOG.md

@@ -16,6 +16,9 @@ Changelog categories for `Unreleased` and new release sections (in order, includ
 
 ## Unreleased
 
+### Build and Tooling
+- ✅ Updated the GitHub Pages docs workflow to fetch full Git history and tags for `gradle-jgitver`, and added a JavaDoc version guard that fails if fallback version `0.0.0-0` is resolved.
+
 ## v0.7.1 - 2026-03-17
 
 ### Fixes