@htekdev/actions-debugger 1.0.2 → 1.0.4

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"

package/errors/triggers/environment-protection-rules-silent-block.yml

@@ -0,0 +1,105 @@
+id: triggers-006
+title: "Job Blocked Silently by Environment Protection Rules — No Clear Log Message"
+category: triggers
+severity: warning
+tags:
+  - environment
+  - protection-rules
+  - deployment
+  - approval
+  - branch-restriction
+  - silent-wait
+patterns:
+  - regex: "Waiting for.*environment.*approval"
+    flags: "i"
+  - regex: "Branch '.*' is not allowed to deploy to .* due to environment protection rules"
+    flags: "i"
+  - regex: "Expected.*Waiting for status to be reported"
+    flags: "i"
+error_messages:
+  - "Branch 'feature/my-branch' is not allowed to deploy to production due to environment protection rules."
+  - "Waiting for approval — This workflow run requires approval from the environment's configured reviewers."
+  - "Expected — Waiting for status to be reported"
+root_cause: |
+  GitHub Environments can have protection rules that gate job execution:
+  - **Required reviewers**: A human must approve the deployment before the job runs.
+  - **Branch/tag restrictions**: Only specific branches or tags are allowed to
+    deploy to the environment (e.g., only `main` can deploy to `production`).
+  - **Required status checks**: External status checks must pass first.
+  - **Wait timers**: A mandatory delay before the job can proceed.
+
+  When a job targets an environment with unsatisfied protection rules, it enters
+  a waiting state in the GitHub UI. The **workflow log may not show a clear
+  failure message** — the job simply appears as pending or "Expected — Waiting
+  for status to be reported." This is a common source of confusion for teams
+  that enable environment protection rules for the first time, especially in
+  forks or feature-branch workflows where the branch is not in the allowed list.
+
+  Documented in GitHub Community discussions #39054 and #26698.
+fix: |
+  1. **Check environment settings**: Repository Settings → Environments → select
+     the environment → review protection rules (required reviewers, deployment
+     branches, required checks, wait timers).
+
+  2. **For branch restriction failures**: Add the branch that the workflow runs
+     on to the environment's "Deployment branches and tags" list, or change the
+     policy to "No restriction" for non-production environments.
+
+  3. **For pending approval**: A configured reviewer must approve the deployment
+     in the GitHub UI (Actions tab → select the run → click "Review deployments").
+
+  4. **For automated CI**: Use a separate environment with no protection rules
+     for automated test deployments, and reserve protected environments for
+     production deployments that require human approval.
+
+  5. **For fork PRs**: Environments with protection rules can silently block
+     fork PRs since the fork branch is not in the allowed branch list — use a
+     separate no-protection environment for fork PR validation jobs.
+fix_code:
+  - language: yaml
+    label: "Use separate environments for CI vs production"
+    code: |
+      jobs:
+        deploy-staging:
+          runs-on: ubuntu-latest
+          environment: staging    # ✅ no protection rules — runs immediately
+          steps:
+            - run: ./deploy.sh staging
+
+        deploy-production:
+          needs: deploy-staging
+          runs-on: ubuntu-latest
+          environment: production  # 🔒 has required reviewers — waits for approval
+          if: github.ref == 'refs/heads/main'  # ✅ only main is in allowed branch list
+          steps:
+            - run: ./deploy.sh production
+  - language: yaml
+    label: "Check branch restriction: ensure workflow branch is in allowed list"
+    code: |
+      # In GitHub UI: Settings → Environments → production → Deployment branches
+      # Add "main" or change policy to match your workflow's ref.
+      #
+      # In workflow: use github.ref_name to verify before targeting environment
+      jobs:
+        deploy:
+          runs-on: ubuntu-latest
+          # Only run on main — matches production environment's branch restriction
+          if: github.ref == 'refs/heads/main'
+          environment: production
+          steps:
+            - run: ./deploy.sh
+prevention:
+  - "Document environment protection rules in your repository's CONTRIBUTING.md so all developers know which branches can deploy where."
+  - "Test protection rules in a staging environment before applying them to production — the silent-wait behavior is surprising on first encounter."
+  - "For automated CI workflows that run on feature branches, use environments without branch restrictions or required reviewers."
+  - "After enabling environment protection rules, verify the workflow can actually trigger by running a test deployment from an allowed branch."
+  - "Monitor for stuck jobs in the Actions tab — a job sitting in 'waiting' or 'Expected' state usually means an environment protection rule is blocking it."
+docs:
+  - url: "https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment"
+    label: "Using environments for deployment — protection rules"
+  - url: "https://github.com/orgs/community/discussions/39054"
+    label: "GitHub Community #39054 — Branch not allowed to deploy due to environment protection rules"
+  - url: "https://github.com/orgs/community/discussions/26698"
+    label: "GitHub Community #26698 — Job stuck in Expected / Waiting for status to be reported"
+  - url: "https://stackoverflow.com/questions/72109150/github-action-avoid-approval-on-same-environment-rule-within-same-workflow"
+    label: "Stack Overflow — Avoiding approval in same environment within same workflow"

package/errors/yaml-syntax/env-context-unavailable-job-level.yml

@@ -0,0 +1,109 @@
+id: yaml-syntax-014
+title: "env Context Not Available at Job-Level if or Reusable Workflow Positions"
+category: yaml-syntax
+severity: error
+tags:
+  - env
+  - context
+  - job-if
+  - reusable-workflow
+  - expression
+  - context-availability
+patterns:
+  - regex: "Unrecognized named-value: 'env'"
+    flags: "i"
+  - regex: "The workflow is not valid.*Unrecognized named-value: 'env'"
+    flags: "i"
+  - regex: "Located at position \\d+ within expression.*env\\."
+    flags: "i"
+error_messages:
+  - "The workflow is not valid. .github/workflows/<workflow>.yml (Line: X, Col: Y): Unrecognized named-value: 'env'. Located at position Z within expression: <expression>"
+  - "Unrecognized named-value: 'env'. Located at position 1 within expression"
+root_cause: |
+  GitHub Actions evaluates job-level expressions (jobs.<job_id>.if, certain
+  jobs.<job_id>.with: inputs for reusable workflows) before any steps run and
+  before step-level env values are available. Because the `env` context is
+  only populated at step execution time, using `env.MY_VAR` inside a job-level
+  `if:` condition or inside a reusable workflow's `jobs:` block triggers a
+  validation error at parse time rather than a runtime failure.
+
+  This affects:
+  - `jobs.<job_id>.if: ${{ env.MY_VAR == 'foo' }}`
+  - `jobs.<job_id>.with:` fields referencing `env.*` in a reusable workflow call
+  - Any top-level workflow expression that attempts to read `env` context
+
+  Documented in actions/runner issues #1189, #1661, and #2372.
+fix: |
+  Replace env context references in job-level positions with contexts that are
+  available at job evaluation time:
+  - Use `vars.*` (repository/environment variables) for static configuration values
+  - Use `github.*` context for event-driven values
+  - Use `inputs.*` for values passed into reusable workflows
+  - Use job outputs (`needs.<job_id>.outputs.<name>`) to pass dynamic values
+    computed in earlier steps to downstream job `if:` conditions
+
+  If the value is truly dynamic and set in a previous step, emit it as a step
+  output → job output → needs output chain so downstream jobs can reference it.
+fix_code:
+  - language: yaml
+    label: "WRONG — env context in job-level if (fails validation)"
+    code: |
+      jobs:
+        deploy:
+          if: ${{ env.DEPLOY_ENV == 'production' }}  # ❌ env not available here
+          runs-on: ubuntu-latest
+          steps:
+            - run: echo "Deploying"
+  - language: yaml
+    label: "RIGHT — use vars context or job outputs instead"
+    code: |
+      # Option 1: use vars (repository/environment variables) for static config
+      jobs:
+        deploy:
+          if: ${{ vars.DEPLOY_ENV == 'production' }}  # ✅ vars available at job level
+          runs-on: ubuntu-latest
+          steps:
+            - run: echo "Deploying"
+
+      # Option 2: compute in a preceding job, emit as output
+      jobs:
+        compute-env:
+          runs-on: ubuntu-latest
+          outputs:
+            deploy_env: ${{ steps.set-env.outputs.deploy_env }}
+          steps:
+            - id: set-env
+              run: echo "deploy_env=production" >> $GITHUB_OUTPUT
+
+        deploy:
+          needs: compute-env
+          if: ${{ needs.compute-env.outputs.deploy_env == 'production' }}
+          runs-on: ubuntu-latest
+          steps:
+            - run: echo "Deploying"
+  - language: yaml
+    label: "RIGHT — reusable workflow: pass value via inputs not env"
+    code: |
+      # Caller workflow
+      jobs:
+        call-deploy:
+          uses: ./.github/workflows/deploy.yml
+          with:
+            environment: production  # ✅ pass via inputs, not env
+          secrets: inherit
+prevention:
+  - "Consult the GitHub docs context availability table before writing expressions — not all contexts are available at every YAML key position."
+  - "For job-level if conditions, use `vars.*`, `github.*`, or `needs.<job>.outputs.*` — never `env.*`."
+  - "For reusable workflow inputs, pass values explicitly through `with:` inputs rather than relying on caller env context."
+  - "Use `vars` (repository/environment variables) as a replacement for env-based feature flags that need to be available at job evaluation time."
+docs:
+  - url: "https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs#context-availability"
+    label: "Context availability — which contexts are available at each YAML key"
+  - url: "https://github.com/actions/runner/issues/1189"
+    label: "actions/runner #1189 — Unrecognized named-value: 'env' for job conditional"
+  - url: "https://github.com/actions/runner/issues/1661"
+    label: "actions/runner #1661 — env unrecognised in job-level if when calling reusable workflow"
+  - url: "https://github.com/actions/runner/issues/2372"
+    label: "actions/runner #2372 — Unrecognized named-value: 'env' in reusable workflow jobs"
+  - url: "https://stackoverflow.com/questions/76471787/why-is-env-context-not-available-in-github-action-job-level-if-statement"
+    label: "Stack Overflow — Why is env context not available in job level if statement?"

package/package.json

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