@htekdev/actions-debugger 1.0.1 → 1.0.3

package/errors/runner-environment/node20-to-node24-migration.yml

@@ -0,0 +1,118 @@
+id: runner-environment-016
+title: "Node 20 → Node 24 Forced Migration Breaks Actions and macOS 13 Runners"
+category: runner-environment
+severity: error
+tags:
+  - node
+  - node24
+  - deprecation
+  - macos
+  - arm32
+  - runtime-migration
+patterns:
+  - regex: "Node\\.?20 actions are deprecated"
+    flags: "i"
+  - regex: "Please update the following actions to use Node\\.?24"
+    flags: "i"
+  - regex: "node20 is deprecated"
+    flags: "i"
+  - regex: "macOS 13.*not supported.*Node 24"
+    flags: "i"
+  - regex: "ARM32.*no longer supported"
+    flags: "i"
+error_messages:
+  - "Node.js 20 actions are deprecated. Please update the following actions to use Node.js 24."
+  - "node20 is deprecated and will be disabled in a future runner release."
+  - "Error: This action requires Node.js 24 or higher. Current version: 20."
+root_cause: |
+  GitHub announced deprecation of Node 20 on Actions runners on September 19, 2025
+  (editor updated May 19, 2026: migration date confirmed June 16, 2026). Starting
+  June 16, 2026, all GitHub-hosted runners default to Node 24.
+
+  Three distinct breakage scenarios exist:
+
+  1. **Marketplace actions using `runs.using: 'node20'`** — any third-party or custom
+     action that declares `runs.using: node20` in its `action.yml` will emit deprecation
+     warnings and eventually fail when GitHub removes Node 20 from runners later in 2026.
+
+  2. **macOS 13 (and older) runners are incompatible with Node 24** — Node 24 dropped
+     support for macOS 13.4 and lower. Workflows specifying `runs-on: macos-13` (or older
+     images) fail at the runner startup phase or produce unexpected errors from the
+     Node-based runner bootstrapper.
+
+  3. **ARM32 self-hosted runners** — Node 24 has no official ARM32 support. Self-hosted
+     runners on ARM32 hardware silently lose the ability to execute Node-based actions
+     after the Node 20 removal milestone.
+fix: |
+  **For action authors:** Update `action.yml` to declare `runs.using: 'node24'` and
+  test locally with Node 24. Publish a new release so downstream consumers pick it up.
+
+  **For workflow authors:**
+  - Upgrade all `uses:` pins to the latest major version that ships with Node 24 support
+    (e.g. `actions/checkout@v4 → @v4` already Node-24-ready; `actions/setup-node@v4`
+    already Node-24-ready).
+  - Replace `runs-on: macos-13` with `runs-on: macos-latest` or `macos-14+`.
+  - For ARM32 self-hosted runners: migrate to ARM64 hardware or use container-based
+    execution that bundles its own Node runtime.
+
+  **Temporary escape hatch (not for production long-term):**
+  Set `ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true` in the workflow `env` block to
+  continue using Node 20 until GitHub removes it from runners later in 2026.
+fix_code:
+  - language: yaml
+    label: "Upgrade pinned action versions to Node 24-compatible releases"
+    code: |
+      steps:
+        # Pin to latest major — all official actions already ship Node 24 builds
+        - uses: actions/checkout@v4
+        - uses: actions/setup-node@v4
+          with:
+            node-version: '20'
+        - uses: actions/upload-artifact@v4
+          with:
+            name: dist
+            path: dist/
+  - language: yaml
+    label: "Migrate macOS runner from macos-13 to macos-latest"
+    code: |
+      jobs:
+        build:
+          # macos-13 is incompatible with Node 24 — use macos-latest (14+)
+          runs-on: macos-latest
+          steps:
+            - uses: actions/checkout@v4
+  - language: yaml
+    label: "Temporary escape hatch — keep Node 20 until explicit removal"
+    code: |
+      jobs:
+        build:
+          runs-on: ubuntu-latest
+          env:
+            # WARNING: temporary only — Node 20 will be fully removed later in 2026
+            ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION: 'true'
+          steps:
+            - uses: actions/checkout@v4
+  - language: yaml
+    label: "Test Node 24 compatibility before the mandatory cutover"
+    code: |
+      jobs:
+        build:
+          runs-on: ubuntu-latest
+          env:
+            # Force Node 24 to test compatibility ahead of the June 16 cutover
+            FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: 'true'
+          steps:
+            - uses: actions/checkout@v4
+prevention:
+  - "Subscribe to GitHub changelog https://github.blog/changelog/label/actions/ for deprecation notices."
+  - "Run `FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true` in CI to catch Node 24 incompatibilities early."
+  - "Avoid pinning to old major versions of `actions/*` — use floating major tags (e.g. @v4)."
+  - "Audit custom/internal actions for `runs.using: node20` declarations before the June 16, 2026 migration date."
+  - "Migrate macOS CI to macos-14 or macos-latest to ensure Node 24 compatibility."
+docs:
+  - 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"
+  - url: "https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-javascript-actions"
+    label: "Metadata syntax: runs.using for JavaScript actions"
+  - url: "https://docs.github.com/en/actions/using-github-hosted-runners/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources"
+    label: "Supported runners and hardware resources"

package/errors/runner-environment/powershell-74-to-76-upgrade.yml

@@ -0,0 +1,112 @@
+id: runner-environment-019
+title: "PowerShell 7.4 → 7.6 LTS Upgrade Breaks pwsh Scripts"
+category: runner-environment
+severity: warning
+tags:
+  - powershell
+  - pwsh
+  - runner-image
+  - breaking-change
+  - windows
+  - linux
+patterns:
+  - regex: "The term 'ThreadJob\\\\\\\\Start-ThreadJob' is not recognized"
+    flags: "i"
+  - regex: "Cannot bind parameter.*ChildPath.*expected.*String.*got.*Array"
+    flags: "i"
+  - regex: "WildcardPattern.*backtick|escape.*pattern.*unexpected"
+    flags: "i"
+  - regex: "New-EventLog.*source.*trailing|event source.*not found"
+    flags: "i"
+error_messages:
+  - "The term 'ThreadJob\\Start-ThreadJob' is not recognized as a name of a cmdlet, function, script file, or executable program."
+  - "Cannot bind parameter 'ChildPath'. Cannot convert the 'System.Object[]' value of type 'System.Object[]' to type 'System.String'."
+  - "Start-ThreadJob : The term 'ThreadJob\\Start-ThreadJob' is not recognized"
+root_cause: |
+  GitHub Actions upgraded PowerShell from 7.4.x to 7.6 LTS on all runner images beginning
+  June 8, 2026 (completing June 15, 2026). This affects every runner OS: ubuntu-22.04,
+  ubuntu-24.04, ubuntu-slim, macos-14/15/26, windows-2022/2025/2025-vs2026.
+
+  PowerShell 7.6 is built on .NET 10 (7.4 was on .NET 8). The documented breaking changes are:
+
+  1. **ThreadJob module renamed**: `ThreadJob` module is now `Microsoft.PowerShell.ThreadJob`.
+     Scripts calling `ThreadJob\Start-ThreadJob` with the old module-qualified name will throw
+     a "not recognized" error. The cmdlet itself (`Start-ThreadJob`) still works without prefix.
+
+  2. **`Join-Path -ChildPath` now accepts `string[]`**: Parameter binding changed from `string`
+     to `string[]`. Existing code that passes multiple -ChildPath args may see binding errors
+     depending on how arguments were constructed.
+
+  3. **`WildcardPattern.Escape` now correctly escapes lone backticks**: Scripts that relied on
+     the previous (incorrect) behavior of backtick handling in wildcard patterns may produce
+     different results.
+
+  4. **Event source name trailing space removed**: New-EventLog / Write-EventLog source names
+     no longer have a trailing space. Scripts that matched exact event source names including
+     the trailing space (e.g., `"MySource "`) will fail to match.
+
+  5. **.NET 10 runtime**: Any `pwsh` script using .NET types or reflection that was tested
+     against .NET 8 behavior may see subtle differences.
+fix: |
+  **ThreadJob module name** — the most common breaking change:
+  Replace `ThreadJob\Start-ThreadJob` with `Microsoft.PowerShell.ThreadJob\Start-ThreadJob`,
+  or just call `Start-ThreadJob` without the module qualifier.
+
+  **Event source name** — if you match exact source names:
+  Trim any trailing spaces from source name comparisons.
+
+  **Pin PowerShell version** if you need time to migrate (not recommended long-term):
+  Install a specific pwsh version in your workflow before running scripts.
+
+  **Test locally**: Install PowerShell 7.6 (`winget install Microsoft.PowerShell`) and run
+  your scripts to catch any remaining issues before they surface in CI.
+fix_code:
+  - language: yaml
+    label: "Fix ThreadJob module-qualified name"
+    code: |
+      # In your PowerShell script — change this:
+      #   ThreadJob\Start-ThreadJob -ScriptBlock { ... }
+      # To either:
+      #   Start-ThreadJob -ScriptBlock { ... }          # simplest fix
+      #   Microsoft.PowerShell.ThreadJob\Start-ThreadJob -ScriptBlock { ... }  # fully qualified
+  - language: yaml
+    label: "Pin PowerShell version as a temporary workaround"
+    code: |
+      jobs:
+        build:
+          runs-on: ubuntu-latest
+          steps:
+            - uses: actions/checkout@v4
+
+            # Pin pwsh to 7.4.x temporarily while migrating
+            - name: Install PowerShell 7.4
+              run: |
+                wget -q "https://github.com/PowerShell/PowerShell/releases/download/v7.4.10/powershell_7.4.10-1.deb_amd64.deb"
+                sudo dpkg -i powershell_7.4.10-1.deb_amd64.deb
+
+            - name: Run PowerShell script
+              shell: pwsh
+              run: ./scripts/build.ps1
+  - language: yaml
+    label: "Fix event source name trailing-space match"
+    code: |
+      # Before (broken on 7.6):
+      # if ($event.Source -eq "MyApp ") { ... }
+      #
+      # After (works on 7.4 and 7.6):
+      # if ($event.Source.Trim() -eq "MyApp") { ... }
+prevention:
+  - "Subscribe to actions/runner-images announcements for PowerShell upgrade notices well before they ship."
+  - "Always use unqualified cmdlet names (`Start-ThreadJob`) rather than module-qualified names (`ThreadJob\\Start-ThreadJob`) to avoid module-rename breakage."
+  - "Run your PowerShell scripts through PSScriptAnalyzer with the latest rule set after any PS version upgrade."
+  - "Test pwsh workflows in a matrix with the previous and new PS version during runner image transition periods."
+docs:
+  - url: "https://github.com/actions/runner-images/issues/14150"
+    label: "GitHub Announcement: PowerShell 7.4 → 7.6 upgrade on all runner images"
+  - url: "https://learn.microsoft.com/en-us/powershell/scripting/whats-new/what-s-new-in-powershell-76"
+    label: "PowerShell 7.6 release notes and breaking changes"
+  - url: "https://learn.microsoft.com/en-us/powershell/scripting/install/powershell-support-lifecycle"
+    label: "PowerShell support lifecycle"
+source:
+  article: "https://htek.dev/articles/github-actions-debugging-guide"
+  section: "Runner image tool version changes"

package/errors/runner-environment/service-container-unhealthy.yml

@@ -0,0 +1,126 @@
+id: runner-environment-021
+title: "Service Container Marked Unhealthy — Health Check Timeout"
+category: runner-environment
+severity: error
+tags:
+  - service-container
+  - healthcheck
+  - docker
+  - timeout
+  - postgres
+  - redis
+  - rabbitmq
+patterns:
+  - regex: "service is unhealthy"
+    flags: "i"
+  - regex: "Failed to initialize.*service is unhealthy"
+    flags: "i"
+  - regex: "##\\[error\\]Failed to initialize.*service"
+    flags: "i"
+  - regex: "container_id.*unhealthy"
+    flags: "i"
+error_messages:
+  - "##[error]Failed to initialize, rabbitmq service is unhealthy."
+  - "##[error]Failed to initialize, postgres service is unhealthy."
+  - "##[error]Failed to initialize, redis service is unhealthy."
+  - "unhealthy"
+  - "service is starting, waiting 29 seconds before checking again."
+root_cause: |
+  GitHub Actions checks the Docker HEALTHCHECK status of service containers
+  before allowing dependent job steps to run. If the container does not
+  transition to `healthy` within the runner's fixed retry window, the job
+  fails with "service is unhealthy".
+
+  This commonly occurs because:
+  1. **No options specified** — Docker uses the image's built-in HEALTHCHECK,
+     which may be missing, too aggressive, or unsuitable for the CI environment.
+  2. **Startup time** — services like PostgreSQL, RabbitMQ, or Elasticsearch
+     take longer to initialize on GitHub-hosted runners than on local machines,
+     and the default health-check interval/retries expire before they're ready.
+  3. **Wrong health-check command** — a network ping health check may fail if
+     the service port isn't yet bound even though the process is running.
+  4. **Missing `--health-start-period`** — without a start period, Docker counts
+     health-check failures from container start, before the service has had time
+     to initialize.
+
+  Documented in actions/example-services issue #3.
+fix: |
+  Add `options:` to the service container definition with explicit health-check
+  parameters suited to the service and GitHub-hosted runner environment:
+
+  - `--health-cmd`: Use a service-native health check command, not a TCP probe.
+    Examples:
+      PostgreSQL: `pg_isready -U postgres`
+      Redis:      `redis-cli ping`
+      MySQL:      `mysqladmin ping -h localhost`
+      RabbitMQ:   `rabbitmqctl node_health_check`
+
+  - `--health-interval 10s`: Check every 10 seconds
+  - `--health-timeout 5s`: Allow up to 5 seconds per check
+  - `--health-retries 5`: Retry up to 5 times before marking unhealthy
+  - `--health-start-period 30s`: Give 30 seconds before counting failures
+
+  If the image lacks a health check and the options approach is insufficient,
+  add an explicit wait step after job start using the service label name to
+  poll readiness with a loop.
+fix_code:
+  - language: yaml
+    label: "PostgreSQL service container with proper health check"
+    code: |
+      jobs:
+        test:
+          runs-on: ubuntu-latest
+          services:
+            postgres:
+              image: postgres:16
+              env:
+                POSTGRES_PASSWORD: postgres
+                POSTGRES_DB: testdb
+              ports:
+                - 5432:5432
+              options: >-
+                --health-cmd "pg_isready -U postgres"
+                --health-interval 10s
+                --health-timeout 5s
+                --health-retries 5
+                --health-start-period 30s
+          steps:
+            - run: psql postgresql://postgres:postgres@localhost:5432/testdb -c "SELECT 1"
+  - language: yaml
+    label: "Redis service container with proper health check"
+    code: |
+      services:
+        redis:
+          image: redis:7
+          ports:
+            - 6379:6379
+          options: >-
+            --health-cmd "redis-cli ping"
+            --health-interval 10s
+            --health-timeout 5s
+            --health-retries 5
+  - language: yaml
+    label: "Fallback — explicit wait step if health check unreliable"
+    code: |
+      steps:
+        - name: Wait for PostgreSQL to be ready
+          run: |
+            until pg_isready -h localhost -p 5432 -U postgres; do
+              echo "Waiting for postgres..."
+              sleep 2
+            done
+          timeout-minutes: 2
+prevention:
+  - "Always specify `options:` with `--health-cmd`, `--health-interval`, `--health-retries`, and `--health-start-period` for every service container."
+  - "Use service-native health check commands (pg_isready, redis-cli ping) rather than generic TCP probes."
+  - "Add `--health-start-period` of 20-30 seconds for services with slow initialization (PostgreSQL, Elasticsearch, RabbitMQ)."
+  - "Test health check timing locally in Docker before relying on it in CI: `docker run --health-cmd '...' --health-interval 5s <image>`."
+docs:
+  - url: "https://docs.github.com/en/actions/using-containerized-services/about-service-containers"
+    label: "About service containers"
+  - url: "https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idservicesservice_idoptions"
+    label: "Workflow syntax — services options"
+  - url: "https://github.com/actions/example-services/issues/3"
+    label: "actions/example-services #3 — Service container health check questions and fixes"
+  - url: "https://stackoverflow.com/questions/66763353/how-to-health-check-a-service-in-github"
+    label: "Stack Overflow — How to health check a service in GitHub Actions"

package/errors/runner-environment/windows-latest-vs2026-migration.yml

@@ -0,0 +1,131 @@
+id: runner-environment-020
+title: "windows-latest Now Uses Visual Studio 2026 — VS 2022 Components Removed"
+category: runner-environment
+severity: error
+tags:
+  - windows
+  - visual-studio
+  - runner-image
+  - breaking-change
+  - msbuild
+  - dotnet
+patterns:
+  - regex: "MSB[0-9]+.*Visual Studio 2022|The tools version.*15\\.0.*is not available"
+    flags: "i"
+  - regex: "Dotfuscator.*not found|dotfuscator.*missing"
+    flags: "i"
+  - regex: "Component.*Azure.ServiceFabric.Tools.*not installed"
+    flags: "i"
+  - regex: "VC\\.Tools\\.ARM.*not found|Microsoft\\.VisualStudio\\.Component\\.VC\\.Tools\\.ARM"
+    flags: "i"
+  - regex: "error.*NETSDK1045.*The current .NET SDK does not support targeting .NET (5|6|7)"
+    flags: "i"
+  - regex: "Visual Studio.*version 17\\.[0-9]+.*not found|MSBuild.*17\\.[0-9]+.*not available"
+    flags: "i"
+error_messages:
+  - "MSB4019: The imported project 'Microsoft.CppBuild.targets' was not found."
+  - "Error: Dotfuscator is not installed. Please install Dotfuscator Community."
+  - "The component 'Microsoft.VisualStudio.Component.Azure.ServiceFabric.Tools' is not installed."
+  - "MSBUILD : error MSB1009: Project file does not exist. Switch: /version:17"
+  - "The current .NET SDK does not support targeting .NET 7.0."
+root_cause: |
+  The `windows-latest` and `windows-2025` labels in GitHub Actions were migrated to use
+  **Windows Server 2025 with Visual Studio 2026** beginning June 8, 2026 (completing
+  June 15, 2026). Previously these labels ran Visual Studio 2022 (version 17.x).
+
+  Visual Studio 2026 (version 18.x) ships with MSBuild 18 and removes several VS 2022
+  components that workflows may depend on:
+
+  **Removed VS components:**
+  - `Component.Dotfuscator` — .NET obfuscation tool
+  - `Microsoft.VisualStudio.Component.Azure.ServiceFabric.Tools`
+  - `Microsoft.VisualStudio.Component.TestTools.CodedUITest`
+  - `Microsoft.VisualStudio.Component.TestTools.WebLoadTest`
+  - `Microsoft.VisualStudio.Component.VC.Tools.ARM` — ARM cross-compilation toolchain
+  - `Microsoft.VisualStudio.Component.VC.Modules.x86.x64`
+  - `Microsoft.VisualStudio.Component.VC.Runtimes.ARM.Spectre`
+  - `Microsoft.VisualStudio.Component.VC.MFC.ARM` and `.ARM.Spectre`
+  - `Microsoft.VisualStudio.Component.VC.ATL.ARM` and `.ARM.Spectre`
+  - `Microsoft.VisualStudio.ComponentGroup.Azure.CloudServices`
+  - `Microsoft.VisualStudio.ComponentGroup.Azure.ResourceManager.Tools`
+
+  **Other changes:**
+  - CMake updated from 3.31.6 → 4.3.2 (adds VS 18 2026 generator, deprecates some older generators)
+  - Android Command Line Tools updated from 16.0 → 19.0
+  - MSVC v143 toolset is added as a compatibility shim for projects requiring it
+fix: |
+  **Immediate rollback:** Pin to `windows-2022` to keep Visual Studio 2022:
+  ```yaml
+  runs-on: windows-2022
+  ```
+  Note: `windows-2022` continues to run VS 2022 (version 17.x) and will remain supported.
+
+  **For removed components:**
+  - **Dotfuscator**: Remove from build pipeline, or install manually via the Dotfuscator
+    Community installer in a workflow step. Consider alternatives like ConfuserEx.
+  - **ARM VC toolchain** (`VC.Tools.ARM`): Use the separate `windows-11-arm64` runner label
+    for native ARM64 builds, or cross-compile via MSVC v143 shim that ships with VS 2026.
+  - **Azure Service Fabric Tools**: Install the Service Fabric SDK directly via PowerShell
+    if your workflow requires it.
+  - **CMake generator**: Update your CMake invocation from `-G "Visual Studio 17 2022"` to
+    `-G "Visual Studio 18 2026"`.
+fix_code:
+  - language: yaml
+    label: "Pin to windows-2022 for immediate rollback (VS 2022)"
+    code: |
+      jobs:
+        build:
+          # Temporarily pin to VS 2022 while migrating
+          runs-on: windows-2022
+          steps:
+            - uses: actions/checkout@v4
+            - name: Build
+              run: msbuild MyProject.sln /p:Configuration=Release
+  - language: yaml
+    label: "Migrate to VS 2026 — update CMake generator and toolset"
+    code: |
+      jobs:
+        build:
+          runs-on: windows-latest  # now VS 2026
+          steps:
+            - uses: actions/checkout@v4
+
+            - name: Configure CMake (VS 2026 generator)
+              run: |
+                cmake -B build -G "Visual Studio 18 2026" -A x64 `
+                  -DCMAKE_BUILD_TYPE=Release
+
+            - name: Build
+              run: cmake --build build --config Release
+
+            # If you need MSVC v143 (VS 2022 toolset) compatibility:
+            # cmake -B build -G "Visual Studio 18 2026" -A x64 -T v143
+  - language: yaml
+    label: "Test against both VS 2022 and VS 2026 during migration"
+    code: |
+      jobs:
+        build:
+          strategy:
+            matrix:
+              os: [windows-2022, windows-latest]
+          runs-on: ${{ matrix.os }}
+          steps:
+            - uses: actions/checkout@v4
+            - name: Build and test
+              run: msbuild MyProject.sln /p:Configuration=Release /t:Build,Test
+prevention:
+  - "Avoid depending on specific Visual Studio components that are not part of the core VS 2022/2026 workloads — install them explicitly in your workflow if needed."
+  - "Subscribe to actions/runner-images announcements to receive advance notice of `windows-latest` migrations."
+  - "Test your Windows workflows against `windows-2025-vs2026` before the `windows-latest` migration completes."
+  - "Use MSBuild's `-T v143` toolset flag to target the VS 2022 compiler toolchain from within VS 2026 if full migration is not yet feasible."
+  - "Search your workflows for CMake generator strings like 'Visual Studio 17 2022' and update them proactively."
+docs:
+  - url: "https://github.com/actions/runner-images/issues/14017"
+    label: "GitHub Announcement: windows-latest migrates to Visual Studio 2026"
+  - url: "https://github.com/actions/runner-images/issues/14016"
+    label: "GitHub Announcement: Windows Server 2025 with VS 2026 now GA"
+  - url: "https://docs.github.com/en/actions/using-github-hosted-runners/using-github-hosted-runners/about-github-hosted-runners"
+    label: "About GitHub-hosted runners"
+source:
+  article: "https://htek.dev/articles/github-actions-debugging-guide"
+  section: "Windows runner Visual Studio migrations"

package/errors/silent-failures/hashfiles-empty-string-cache-collision.yml

@@ -0,0 +1,96 @@
+id: silent-failures-009
+title: "hashFiles() Returns Empty String When No Files Match — Silent Cache Key Collision"
+category: silent-failures
+severity: silent-failure
+tags:
+  - cache
+  - hashFiles
+  - cache-key
+  - collision
+  - glob
+  - silent-failure
+patterns:
+  - regex: "key: [A-Za-z0-9_-]+-$"
+    flags: "m"
+  - regex: "Cache restored from key: [A-Za-z0-9_-]+(?!-[0-9a-f]{64})"
+    flags: "i"
+error_messages:
+  - "Cache restored from key: Linux-node-"
+  - "Cache restored from key: Linux-pip-"
+  - "No error shown — workflow succeeds but wrong cache is restored"
+root_cause: |
+  The `hashFiles()` expression function returns an empty string (not an error)
+  when the supplied glob pattern matches no files in the workspace. This silently
+  truncates the cache key, turning a key like:
+
+    ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
+
+  into:
+
+    Linux-node-
+
+  when no package-lock.json exists. This short, predictable key collides across
+  branches and runs, causing stale or wrong cache content to be restored without
+  any warning. The workflow log shows the cache as restored successfully.
+
+  Documented in actions/runner issue #894. Commonly triggered by:
+  - Lockfile not yet committed (new project setup)
+  - Wrong glob path (e.g., `**/package-lock.json` but lockfile is at root)
+  - Wrong working directory at cache step execution time
+  - Matrix jobs where not all matrix values have a matching lockfile
+fix: |
+  Add a fallback value to the hashFiles() expression using the `||` operator so
+  the key is always deterministic even when no files match:
+
+    key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') || 'no-lockfile' }}
+
+  Also verify that the glob actually matches the file by running
+  `find . -name "package-lock.json"` in a debug step before the cache step.
+
+  For matrix workflows, include the matrix value in the key to prevent
+  cross-matrix collisions even when hash is empty:
+
+    key: ${{ runner.os }}-node-${{ matrix.node-version }}-${{ hashFiles('**/package-lock.json') || 'no-lockfile' }}
+fix_code:
+  - language: yaml
+    label: "WRONG — hashFiles with no fallback (silently short key on miss)"
+    code: |
+      - uses: actions/cache@v4
+        with:
+          path: ~/.npm
+          key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
+          # ❌ If no package-lock.json found, key becomes "Linux-node-"
+          # All runs share the same truncated key → wrong cache restored silently
+  - language: yaml
+    label: "RIGHT — hashFiles with explicit fallback"
+    code: |
+      - uses: actions/cache@v4
+        with:
+          path: ~/.npm
+          key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') || 'no-lockfile' }}
+          # ✅ If no lockfile, key becomes "Linux-node-no-lockfile" — deterministic and unique
+          restore-keys: |
+            ${{ runner.os }}-node-
+  - language: yaml
+    label: "DEBUG — verify glob matches before caching"
+    code: |
+      - name: Debug — check lockfile exists
+        run: find . -name "package-lock.json" | head -5
+        # If empty output: fix the glob or ensure lockfile is committed
+
+      - uses: actions/cache@v4
+        with:
+          path: ~/.npm
+          key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') || 'no-lockfile' }}
+prevention:
+  - "Always provide a `|| 'fallback-value'` after any hashFiles() call to prevent empty-string cache key truncation."
+  - "Test your hashFiles() glob locally: run `find . -name 'your-lockfile'` from the repo root to confirm it matches."
+  - "Include stable discriminators (runner.os, matrix values, Node version) in cache keys to reduce collision risk."
+  - "Review restored cache key in workflow logs — a key ending in just a short prefix without a 64-char hash is a sign of an empty hashFiles()."
+docs:
+  - url: "https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/evaluate-expressions-in-workflows-and-actions#hashfiles"
+    label: "hashFiles() function documentation"
+  - url: "https://github.com/actions/runner/issues/894"
+    label: "actions/runner #894 — hashFiles returns empty string instead of hash"
+  - url: "https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows"
+    label: "Caching dependencies to speed up workflows"