@htekdev/actions-debugger 1.0.20 → 1.0.21

package/errors/runner-environment/android-sdk-api37-hash-mismatch.yml

@@ -0,0 +1,97 @@
+id: runner-environment-055
+title: "Android SDK Platform 37 Installed as 'android-37.0' — Builds Fail Looking for 'android-37'"
+category: runner-environment
+severity: error
+tags:
+  - android
+  - android-sdk
+  - gradle
+  - ubuntu-2404
+  - sdk-platform
+  - hash-string
+patterns:
+  - regex: "Failed to find target with hash string 'android-37'"
+    flags: "i"
+  - regex: "Failed to find target.*android-37[^\\d]"
+    flags: "i"
+  - regex: "Could not determine.*dependencies.*android-37[^\\d]"
+    flags: "i"
+  - regex: "platforms/android-37\\.0.*android-37[^\\.]"
+    flags: "i"
+error_messages:
+  - "Failed to find target with hash string 'android-37' in: /usr/local/lib/android/sdk"
+  - "Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'."
+  - "> Failed to find target with hash string 'android-37'"
+root_cause: |
+  On the Ubuntu 24.04 runner image (from approximately image version 20260323), the
+  Android SDK Platform 37 is installed under the directory name `android-37.0` rather
+  than the expected `android-37`. Gradle and the Android Gradle Plugin (AGP) look up
+  platform targets by their hash string (`android-37`), which must exactly match the
+  subdirectory name inside `$ANDROID_SDK_ROOT/platforms/`.
+
+  When `sdkmanager` installs `platforms;android-37.0`, it creates:
+    `/usr/local/lib/android/sdk/platforms/android-37.0/`
+
+  But AGP resolves `compileSdk = 37` (or `compileSdkVersion 37`) to hash string
+  `android-37`, not `android-37.0`. The lookup fails even though the SDK is physically
+  present on the runner (runner-images#13859).
+
+  Root cause in the runner image: the `platforms;android-37.0` package name was published
+  by Google with a `.0` version suffix in the SDK package path, causing a naming
+  inconsistency between the package identifier and the installed directory name expected
+  by build tools.
+fix: |
+  Add a workaround step that creates a symlink from `android-37` → `android-37.0` before
+  the Gradle build. This resolves the hash lookup without any source code changes.
+
+  Alternatively, pin `compileSdk` to 36 (which is installed normally) until the runner
+  image is fixed, or install `platforms;android-37` explicitly via sdkmanager — but note
+  that as of the time of writing the `android-37` (non-.0) package may not yet be
+  published to the official SDK registry.
+fix_code:
+  - language: yaml
+    label: "Symlink workaround — link android-37 to android-37.0 before build"
+    code: |
+      steps:
+        - uses: actions/checkout@v4
+
+        - name: Fix Android SDK 37 directory name mismatch
+          run: |
+            SDK_PLATFORMS="$ANDROID_SDK_ROOT/platforms"
+            if [ -d "$SDK_PLATFORMS/android-37.0" ] && [ ! -d "$SDK_PLATFORMS/android-37" ]; then
+              ln -s "$SDK_PLATFORMS/android-37.0" "$SDK_PLATFORMS/android-37"
+              echo "Symlinked android-37 -> android-37.0"
+            fi
+
+        - name: Build APK
+          run: ./gradlew assembleDebug
+  - language: yaml
+    label: "Pin compileSdk to 36 as temporary workaround"
+    code: |
+      # In app/build.gradle or build.gradle.kts:
+      android {
+          compileSdk = 36   # Use 36 until android-37 symlink issue is resolved
+          # compileSdk = 37  # <- caused 'android-37' hash mismatch
+      }
+  - language: yaml
+    label: "Install android-37 explicitly via sdkmanager"
+    code: |
+      steps:
+        - name: Install Android SDK Platform 37
+          run: |
+            echo "y" | $ANDROID_SDK_ROOT/cmdline-tools/latest/bin/sdkmanager \
+              "platforms;android-37" \
+              "build-tools;37.0.0"
+        - name: Build
+          run: ./gradlew assembleDebug
+prevention:
+  - "When upgrading `compileSdk` to a newly released Android API level, test against ubuntu-24.04 runners in a feature branch first before rolling out to all jobs."
+  - "Subscribe to runner-images releases for `ubuntu-24.04` to catch SDK directory naming changes early."
+  - "Add an explicit `sdkmanager` install step for the exact platform and build-tools version your project requires instead of relying on pre-installed SDKs."
+docs:
+  - url: "https://github.com/actions/runner-images/issues/13859"
+    label: "runner-images#13859 — Ubuntu 24.04 installs API 37 as android-37.0; builds fail looking for android-37"
+  - url: "https://developer.android.com/studio/releases/platforms"
+    label: "Android SDK Platform releases — official platform package naming"
+  - url: "https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources"
+    label: "GitHub Docs — GitHub-hosted runner software"

package/errors/runner-environment/android-sdk-platforms-v33-removed.yml

@@ -0,0 +1,120 @@
+id: runner-environment-056
+title: "Android SDK Platforms and Build Tools < v34 Removed from Runner Images (Jan 2026)"
+category: runner-environment
+severity: error
+tags:
+  - android
+  - android-sdk
+  - gradle
+  - runner-images
+  - ubuntu-2204
+  - macos-14
+  - windows-2022
+  - compile-sdk
+patterns:
+  - regex: "Failed to find target with hash string 'android-3[0-3]'"
+    flags: "i"
+  - regex: "Failed to find Build Tools revision 3[0-3]\\."
+    flags: "i"
+  - regex: "Build Tools revision.*not installed|not installed.*Build Tools"
+    flags: "i"
+  - regex: "compileSdkVersion.*3[0-3].*not found|SDK Platform.*3[0-3].*not installed"
+    flags: "i"
+error_messages:
+  - "Failed to find target with hash string 'android-33' in: /usr/local/lib/android/sdk"
+  - "Failed to find Build Tools revision 33.0.2"
+  - "SDK Platform '33' is not installed."
+  - "Failed to find target with hash string 'android-32'"
+root_cause: |
+  Starting January 12, 2026, GitHub removed pre-installed Android SDK platforms and build
+  tools older than version 34 from the following runner images (runner-images#13469):
+
+  - Ubuntu 22.04
+  - macOS 14 (and macOS 14 Arm64)
+  - Windows Server 2022
+
+  Affected toolchain components:
+  - SDK Platforms: android-33 and older (Android 13 / API 33, API 32, etc.)
+  - Build Tools: versions older than 34.0.0
+
+  The removal was motivated by freeing up disk space. Projects that reference
+  `compileSdkVersion 33` (or lower) in their Gradle configuration, or that install
+  specific old build-tools versions, fail immediately because the expected directories are
+  absent from `$ANDROID_SDK_ROOT/platforms/` and `$ANDROID_SDK_ROOT/build-tools/`.
+
+  Note: Ubuntu 24.04, macOS 15, and Windows Server 2025 images were not affected because
+  they never carried the older SDK platforms.
+fix: |
+  Option A — Upgrade compileSdk and targetSdk to 34 or higher (recommended):
+    Updating to a supported API level removes the dependency on removed SDK packages.
+    API 34 (Android 14) is widely available and well-tested.
+
+  Option B — Install the required SDK platform at runtime:
+    Use `sdkmanager` in a workflow step to download and install the exact platform and
+    build tools version before the Gradle build runs. This adds ~30-60 seconds to the job.
+fix_code:
+  - language: yaml
+    label: "Upgrade compileSdk to 35 (recommended long-term fix)"
+    code: |
+      # In app/build.gradle.kts:
+      android {
+          compileSdk = 35        # upgraded from 33 — no SDK install step needed
+          targetSdk = 35
+          minSdk = 21
+      }
+  - language: yaml
+    label: "Install removed SDK platform at runtime (keeps compileSdk 33)"
+    code: |
+      steps:
+        - uses: actions/checkout@v4
+
+        - name: Install Android SDK Platform 33 and Build Tools 33.0.2
+          run: |
+            echo "y" | $ANDROID_SDK_ROOT/cmdline-tools/latest/bin/sdkmanager \
+              "platforms;android-33" \
+              "build-tools;33.0.2"
+
+        - name: Build
+          run: ./gradlew assembleDebug
+  - language: yaml
+    label: "Install SDK using android-actions/setup-android"
+    code: |
+      steps:
+        - uses: actions/checkout@v4
+        - uses: android-actions/setup-android@v3
+          with:
+            packages: >
+              platforms;android-33
+              build-tools;33.0.2
+        - run: ./gradlew assembleRelease
+  - language: yaml
+    label: "Matrix build: validate migration to newer API level"
+    code: |
+      jobs:
+        build:
+          strategy:
+            matrix:
+              compile-sdk: [33, 34, 35]
+          runs-on: ubuntu-22.04
+          steps:
+            - uses: actions/checkout@v4
+            - name: Install required SDK (only needed for API < 34)
+              if: matrix.compile-sdk < 34
+              run: |
+                echo "y" | $ANDROID_SDK_ROOT/cmdline-tools/latest/bin/sdkmanager \
+                  "platforms;android-${{ matrix.compile-sdk }}"
+            - run: ./gradlew assembleDebug
+              env:
+                COMPILE_SDK_VERSION: ${{ matrix.compile-sdk }}
+prevention:
+  - "Target `compileSdk` and `targetSdk` at API 34 or higher; Google Play requires API 35+ for new app submissions as of August 2025."
+  - "Audit your `build.gradle` files for hard-coded old `compileSdkVersion` values and migrate proactively during the announcement window."
+  - "Subscribe to runner-images GitHub Issues to see SDK removal announcements before they hit production workflows."
+  - "Add an explicit `sdkmanager` install step for any SDK version your build requires so the workflow is portable regardless of what's pre-installed."
+docs:
+  - url: "https://github.com/actions/runner-images/issues/13469"
+    label: "runner-images#13469 — Android SDK platforms and build tools < v34 removed on Jan 12, 2026"
+  - url: "https://developer.android.com/tools/sdkmanager"
+    label: "Android Docs — sdkmanager command-line tool"
+  - url: "https://developer.android.com/google/play/requirements/target-sdk"
+    label: "Google Play — target API level requirements"

package/errors/runner-environment/node24-action-self-hosted-runner-too-old.yml

@@ -0,0 +1,93 @@
+id: runner-environment-053
+title: "Node 24 Action Fails on Self-Hosted Runner — 'using: node24 is not supported'"
+category: runner-environment
+severity: error
+tags:
+  - node24
+  - self-hosted-runner
+  - runner-version
+  - node-runtime
+  - actions-checkout
+  - actions-cache
+patterns:
+  - regex: "'using: node24' is not supported"
+    flags: "i"
+  - regex: "Parameter.*using.*node24.*is not supported"
+    flags: "i"
+  - regex: "node24.*not supported.*use.*node12.*node16.*node20"
+    flags: "i"
+  - regex: "This version of the Actions runner is too old to run node24"
+    flags: "i"
+error_messages:
+  - "Specified argument was out of the range of valid values. (Parameter ''using: node24' is not supported, use 'docker', 'node12', 'node16' or 'node20' instead.')"
+  - "'using: node24' is not supported, use 'docker', 'node12', 'node16' or 'node20' instead."
+root_cause: |
+  GitHub Actions runner v2.327.1 (released July 25, 2025) was the first version to add
+  support for the `node24` runtime. Actions that bumped their major version to run on
+  Node.js 24 (including `actions/checkout@v5`, `actions/cache@v5`,
+  `actions/upload-artifact@v6`, and `actions/setup-node@v5`) specify `using: node24` in
+  their `action.yml`. When one of these actions runs on a self-hosted runner older than
+  v2.327.1, the runner's `ActionManifestManager` throws a `System.ArgumentOutOfRangeException`
+  because it does not recognise `node24` as a valid runtime identifier — it only knows
+  `docker`, `node12`, `node16`, and `node20`.
+
+  Common scenarios:
+  - Bumping a pinned `actions/checkout@v4` → `actions/checkout@v5` without first updating
+    the self-hosted runner.
+  - Relying on automatic runner self-update: runners sometimes auto-update the agent binary
+    but the worker process still runs under the old version, causing a mismatch
+    (actions/runner#4064).
+  - Using Dependabot or Renovate to auto-bump action versions across a repo.
+fix: |
+  Update all self-hosted runners to version 2.327.1 or later before upgrading any action
+  to a version that requires `node24`. Steps:
+
+  1. Download and install the latest runner from:
+     https://github.com/actions/runner/releases/latest
+  2. Verify the version with: `./run.sh --version` (Linux/macOS) or `.\run.cmd --version`
+     (Windows).
+  3. If automatic self-update is enabled but stuck, stop the runner service, delete the
+     cached `_work/_update` directory, and restart — or manually install the new version.
+  4. For containerised runners (ARC, summerwind/actions-runner-dind), update the base image
+     tag to a version that ships runner ≥ 2.327.1.
+
+  If you cannot update the runner immediately, pin the actions back to the last v4/v5
+  compatible release and schedule the runner upgrade.
+fix_code:
+  - language: yaml
+    label: "Pin to node24-compatible action versions — requires runner ≥ 2.327.1"
+    code: |
+      steps:
+        - uses: actions/checkout@v5         # node24 — runner must be ≥ 2.327.1
+        - uses: actions/cache@v5            # node24 — runner must be ≥ 2.327.1
+        - uses: actions/upload-artifact@v6  # node24 — runner must be ≥ 2.327.1
+        - uses: actions/setup-node@v5       # node24 — runner must be ≥ 2.327.1
+  - language: yaml
+    label: "Temporary pin to node20 versions while runner is being updated"
+    code: |
+      steps:
+        - uses: actions/checkout@v4         # still node20, compatible with older runners
+        - uses: actions/cache@v4            # still node20
+        - uses: actions/upload-artifact@v4  # still node20
+        - uses: actions/setup-node@v4       # still node20
+  - language: yaml
+    label: "Verify runner version in workflow (diagnostic)"
+    code: |
+      steps:
+        - name: Print runner version
+          run: echo "Runner version ${{ runner.version }}"
+        # runner.version must be >= 2.327.1 for node24 actions
+prevention:
+  - "Before bumping any action to a node24 major version, check all self-hosted runner versions and update them first."
+  - "Add a minimum runner version check step or GitHub Actions required runner version policy for your organisation."
+  - "Subscribe to runner-images and actions/runner release announcements to learn about node runtime changes in advance."
+  - "For Dependabot/Renovate auto-bumps, add a CI gate that blocks merging action version upgrades until runner compatibility is confirmed."
+docs:
+  - url: "https://github.com/actions/checkout/issues/2240"
+    label: "actions/checkout#2240 — Breaking change with v5: 'using: node24 is not supported' (27 reactions)"
+  - url: "https://github.com/actions/runner/releases/tag/v2.327.1"
+    label: "actions/runner v2.327.1 — First release with Node.js 24 support"
+  - url: "https://github.com/actions/runner/issues/4064"
+    label: "actions/runner#4064 — Auto-update doesn't take node20 → node24 into account, cascading failures"
+  - url: "https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/"
+    label: "GitHub Changelog — Deprecation of Node 20 on GitHub Actions runners"

package/errors/runner-environment/python39-removed-runner-images.yml

@@ -0,0 +1,97 @@
+id: runner-environment-054
+title: "Python 3.9 Removed from Runner Images — Version Not Found in Local Cache"
+category: runner-environment
+severity: error
+tags:
+  - python
+  - python-39
+  - runner-images
+  - toolcache
+  - setup-python
+  - eol
+patterns:
+  - regex: "Version '3\\.9[^']*' was not found in the local cache"
+    flags: "i"
+  - regex: "python.*3\\.9.*not found.*cache|not found.*python.*3\\.9"
+    flags: "i"
+  - regex: "Unable to find python version.*3\\.9"
+    flags: "i"
+  - regex: "Couldn't find a version that satisfies.*python.*3\\.9"
+    flags: "i"
+error_messages:
+  - "Version '3.9.x' was not found in the local cache"
+  - "Unable to find the requested Python version (3.9.x) in the local tool cache"
+  - "Error: Version 3.9 with arch x64 not found"
+root_cause: |
+  Python 3.9 reached end-of-life on October 5, 2025. Starting January 12, 2026, GitHub
+  removed the pre-cached Python 3.9 toolchain from all runner images (ubuntu-22.04,
+  ubuntu-24.04, macOS-14, macOS-15, Windows Server 2022/2025). Additionally, on
+  Windows-based images Python 3.12 replaced 3.9 as the default version
+  (runner-images#13468).
+
+  Workflows are affected when:
+  1. `actions/setup-python` is used with `python-version: '3.9'` without a fallback —
+     the action tries the local toolcache first and fails when the pre-cached entry is gone.
+  2. A workflow assumes the system `python` or `python3` binary is 3.9 on Windows
+     (where it was the previous default).
+  3. A workflow calls `python3.9` directly (e.g. `python3.9 manage.py …`) without
+     installing it first.
+fix: |
+  Option A — Install Python 3.9 at runtime via actions/setup-python (recommended):
+    Add `actions/setup-python` with a specific version. The action will download and
+    install Python 3.9 from the GitHub-managed toolcache CDN even though it is no longer
+    pre-cached on the image.
+
+  Option B — Migrate to a supported Python version:
+    Python 3.9 is EOL. Migrate to Python 3.11, 3.12, or 3.13 to benefit from active
+    security patches. Test your dependency set against the newer version.
+
+  Option C — Pin a newer default for Windows:
+    If you relied on the system default `python` being 3.9 on Windows, add an explicit
+    `actions/setup-python` step to pin the exact version you need.
+fix_code:
+  - language: yaml
+    label: "Install Python 3.9 at runtime (works despite toolcache removal)"
+    code: |
+      steps:
+        - uses: actions/checkout@v4
+        - uses: actions/setup-python@v5
+          with:
+            python-version: '3.9'   # downloaded from CDN — no longer pre-cached
+        - run: python --version
+  - language: yaml
+    label: "Migrate to Python 3.12 (recommended — actively supported)"
+    code: |
+      steps:
+        - uses: actions/checkout@v4
+        - uses: actions/setup-python@v5
+          with:
+            python-version: '3.12'
+        - run: pip install -r requirements.txt
+  - language: yaml
+    label: "Matrix across multiple Python versions"
+    code: |
+      jobs:
+        test:
+          strategy:
+            matrix:
+              python-version: ['3.11', '3.12', '3.13']
+          runs-on: ubuntu-latest
+          steps:
+            - uses: actions/checkout@v4
+            - uses: actions/setup-python@v5
+              with:
+                python-version: ${{ matrix.python-version }}
+            - run: pip install -r requirements.txt && pytest
+prevention:
+  - "Always use `actions/setup-python` with an explicit `python-version` — never rely on the system pre-cached version."
+  - "Subscribe to runner-images EOL announcements to plan Python version migrations before removal dates."
+  - "Add Python version to `.python-version` or `pyproject.toml` and let `actions/setup-python` read it via `python-version-file`."
+  - "Avoid hard-coding EOL Python versions; use `~3.12` or `>=3.11` range specifiers where the toolchain supports them."
+docs:
+  - url: "https://github.com/actions/runner-images/issues/13468"
+    label: "runner-images#13468 — Python 3.9 removed; Python 3.12 becomes default on Windows (Jan 12, 2026)"
+  - url: "https://github.com/actions/setup-python"
+    label: "actions/setup-python — installs any Python version at runtime from CDN"
+  - url: "https://devguide.python.org/versions/"
+    label: "Python Developer's Guide — supported versions and EOL dates"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@htekdev/actions-debugger",
-  "version": "1.0.20",
+  "version": "1.0.21",
   "description": "65+ real GitHub Actions errors, queryable by agents. MCP server + Copilot skills + error database.",
   "type": "module",
   "main": "./dist/index.js",