@htekdev/actions-debugger 1.0.130 → 1.0.131

package/errors/permissions-auth/permissions-auth-076.yml

@@ -0,0 +1,158 @@
+id: permissions-auth-076
+title: '`docker push` to ghcr.io fails with 403 / "denied: permission_denied: write_package" — missing `packages: write` permission'
+category: permissions-auth
+severity: error
+tags:
+  - ghcr
+  - github-packages
+  - container-registry
+  - packages-write
+  - github-token
+  - docker-push
+  - 403
+  - permission-denied
+patterns:
+  - regex: 'denied: permission_denied: write_package'
+    flags: 'i'
+  - regex: 'Error response from daemon.*denied.*ghcr\.io.*403'
+    flags: 'i'
+  - regex: 'error parsing HTTP 403 response body.*ghcr\.io'
+    flags: 'i'
+  - regex: 'unauthorized.*ghcr\.io.*write'
+    flags: 'i'
+  - regex: 'The token provided does not match expected format for.*packages'
+    flags: 'i'
+error_messages:
+  - "Error response from daemon: denied: permission_denied: write_package"
+  - "error parsing HTTP 403 response body: unexpected end of JSON input: \"\""
+  - "denied: denied"
+  - "unauthorized: authentication required"
+  - "buildx failed with: ERROR [auth] ghcr.io token refreshing failed with status: 403 Forbidden"
+root_cause: |
+  GitHub Container Registry (ghcr.io) requires the `packages: write` permission
+  to be explicitly granted in the workflow job's `permissions:` block before
+  `GITHUB_TOKEN` can push (publish) images.
+
+  Since GitHub tightened default GITHUB_TOKEN permissions in 2023, new repositories
+  and organization workflows that set "Restrict GitHub Actions permissions" to
+  "Read repository contents and packages" have `packages: write` DISABLED by default.
+  Without this permission, any `docker push` or `docker buildx build --push` to
+  `ghcr.io` fails with a 403 at the registry level.
+
+  **Why this is confusing:**
+  - `docker login ghcr.io -u ${{ github.actor }} -p ${{ secrets.GITHUB_TOKEN }}`
+    SUCCEEDS (read/login is allowed) — the login step passes
+  - The failure occurs on `docker push`, not login
+  - The error message "denied: permission_denied: write_package" or the generic 403
+    does not directly mention the `packages: write` permission or how to add it
+  - The same workflow may work on repositories created before the permission
+    tightening (where `packages: write` was still the default)
+
+  **Additional requirement — linking the package to the repository:**
+  On first publish, the package is created as unlinked. If the workflow runs in a
+  fork or if the package visibility is set to Private with no repository link, the
+  GITHUB_TOKEN push will also fail even with `packages: write`. The package must be
+  linked to the source repository for GITHUB_TOKEN to authenticate.
+
+  Source: SO #70646920 (22 upvotes, 34k views), SO #78342148, GitHub Docs on
+  container registry permissions.
+fix: |
+  Add `packages: write` to the job's `permissions:` block. This is the most common
+  fix and resolves the majority of GHCR push 403 errors:
+
+  ```yaml
+  jobs:
+    build-and-push:
+      runs-on: ubuntu-latest
+      permissions:
+        contents: read
+        packages: write   # Required to push to ghcr.io
+  ```
+
+  **If login succeeds but push still fails:**
+  1. Verify the package is linked to the repository: go to the package on
+     `github.com/{owner}/{package}` → Package settings → "Add Repository"
+  2. Ensure the package visibility matches the repository (private repo → private
+     package, or set the package to public)
+  3. For organization repositories, confirm the organization has not blocked
+     GitHub Actions from creating packages (Org Settings → Actions → General)
+
+  **If using a separate PAT or App token:**
+  GITHUB_TOKEN with `packages: write` is sufficient for pushing to packages owned
+  by the same repository. For cross-repository or org-level package publishing,
+  use a Fine-Grained PAT with "Packages: Read and write" scope or a GitHub App
+  with "Packages: write" permission.
+fix_code:
+  - language: yaml
+    label: 'Correct job-level permissions for docker push to ghcr.io'
+    code: |
+      name: Build and Push Docker Image
+      on:
+        push:
+          branches: [main]
+      jobs:
+        build-push:
+          runs-on: ubuntu-latest
+          permissions:
+            contents: read
+            packages: write   # <-- Required for ghcr.io push
+          steps:
+            - uses: actions/checkout@v4
+
+            - name: Log in to GitHub Container Registry
+              uses: docker/login-action@v3
+              with:
+                registry: ghcr.io
+                username: ${{ github.actor }}
+                password: ${{ secrets.GITHUB_TOKEN }}
+
+            - name: Build and push
+              uses: docker/build-push-action@v6
+              with:
+                context: .
+                push: true
+                tags: ghcr.io/${{ github.repository }}:latest
+  - language: yaml
+    label: 'Workflow-level permissions fallback (if setting per-job is not possible)'
+    code: |
+      name: Build and Push Docker Image
+      on:
+        push:
+          branches: [main]
+
+      # Set at workflow level — applies to ALL jobs
+      permissions:
+        contents: read
+        packages: write
+
+      jobs:
+        build-push:
+          runs-on: ubuntu-latest
+          steps:
+            - uses: actions/checkout@v4
+            - name: Log in to ghcr.io
+              uses: docker/login-action@v3
+              with:
+                registry: ghcr.io
+                username: ${{ github.actor }}
+                password: ${{ secrets.GITHUB_TOKEN }}
+            - name: Push image
+              run: |
+                docker build -t ghcr.io/${{ github.repository }}:${{ github.sha }} .
+                docker push ghcr.io/${{ github.repository }}:${{ github.sha }}
+prevention:
+  - "Always add `packages: write` to the job permissions block for any job that pushes images to ghcr.io"
+  - "Note that docker login to ghcr.io succeeds without packages:write — always test the actual push step to validate permissions"
+  - "Check your organization's Actions general settings for any policies that restrict packages creation"
+  - "When using docker/build-push-action with push: true, the packages: write permission is required on the job"
+  - "For fork PRs, packages: write is unavailable — use conditional steps: `if: github.event.pull_request.head.repo.full_name == github.repository`"
+  - "Link the package to its source repository after first creation to enable GITHUB_TOKEN-based pushes in future runs"
+docs:
+  - url: 'https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry'
+    label: 'GitHub Docs: Working with the Container registry (ghcr.io)'
+  - url: 'https://docs.github.com/en/actions/security-for-github-actions/security-guides/automatic-token-authentication#permissions-for-the-github_token'
+    label: 'GitHub Docs: GITHUB_TOKEN permissions reference'
+  - url: 'https://stackoverflow.com/questions/70646920/github-token-permission-denied-write-package-when-build-and-push-docker-in-githu'
+    label: 'SO #70646920: GITHUB_TOKEN permission denied write_package (22 upvotes, 34k views)'
+  - url: 'https://docs.github.com/en/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility'
+    label: 'GitHub Docs: Configuring a package access control and visibility'

package/errors/runner-environment/runner-environment-245.yml

@@ -0,0 +1,160 @@
+id: runner-environment-245
+title: 'ARC ephemeral runner pod hangs indefinitely after workflow job cancellation — "Skipping message Job. Job message not found ... job was canceled"'
+category: runner-environment
+severity: error
+tags:
+  - arc
+  - kubernetes
+  - ephemeral-runner
+  - cancellation
+  - stuck-runner
+  - gha-runner-scale-set
+  - job-canceled
+patterns:
+  - regex: 'Skipping message Job\. Job message not found .+ job was canceled'
+    flags: 'i'
+  - regex: 'EphemeralRunner.*status.*Running.*canceled'
+    flags: 'i'
+  - regex: 'Registration .+ was not found\.'
+    flags: 'i'
+  - regex: 'POST request to .+acquirejob failed\. HTTP Status: Conflict'
+    flags: 'i'
+error_messages:
+  - "Skipping message Job. Job message not found 'e420db7b-c780-5ae4-8145-4eea09b87aea'. job was canceled"
+  - "POST request to https://run-actions-*.actions.githubusercontent.com/*/acquirejob failed. HTTP Status: Conflict"
+  - "Registration 470d6c87-f8c4-411f-87d0-6b069233ccc7 was not found."
+root_cause: |
+  When a GitHub Actions workflow job is canceled (manually or by concurrency group
+  cancellation) while an ARC ephemeral runner is in the process of starting up or
+  acquiring the job message, the runner pod enters a broken state:
+
+  1. The broker sends a "job was canceled" message on the runner's job socket.
+  2. The runner logs: "Skipping message Job. Job message not found 'X'. job was canceled"
+  3. **The runner process does not exit** — it waits for a new job message that
+     will never arrive, because ephemeral runners are single-use and the broker
+     considers this runner's slot exhausted.
+  4. The ARC controller sees the EphemeralRunner pod still in `Running` phase with
+     a live runner process. It does NOT delete and recreate the pod.
+  5. The runner slot is held indefinitely. No new job can be dispatched to this slot.
+     Workflows queue but cannot start, consuming queue capacity without making progress.
+
+  **Secondary failure mode**: After the canceled-job hang, the runner may also
+  attempt to re-acquire its registration token. Since the ephemeral runner's
+  registration was already consumed or expired, this fails with:
+  `Registration 'X' was not found.`
+  The BrokerServer then throws repeatedly, producing a growing error log.
+
+  **Impact**: In a scale set with `minRunners > 0`, each canceled job permanently
+  removes one runner slot from the pool until the pod is manually deleted or the
+  scale set is bounced. With frequent cancellations (e.g., PR pushes with concurrency
+  cancel-in-progress), the pool drains completely and CI halts.
+
+  Source: actions/actions-runner-controller#4307 (Nov 2025, 11 reactions, open).
+  Also related: ARC#4468 (scale set queuing delay during burst) — adjacent but distinct.
+fix: |
+  **Option 1 — Delete stuck EphemeralRunner objects manually (immediate relief):**
+  Identify stuck pods — they have been Running for longer than any expected job
+  duration and show "job was canceled" in their logs:
+
+  ```bash
+  kubectl get ephemerals -n arc-runners --sort-by=.metadata.creationTimestamp
+  kubectl logs <stuck-pod-name> -n arc-runners | grep "job was canceled"
+  kubectl delete ephemeralrunner <stuck-pod-name> -n arc-runners
+  ```
+
+  **Option 2 — Add a watchdog sidecar or CronJob to detect and kill stuck runners:**
+  Run a periodic job that identifies EphemeralRunner pods that have been in Running
+  phase beyond `maxRunnerLifetime` and have no active child processes (no build
+  tools, compilers, or test runners as descendants):
+
+  ```bash
+  # Detect hung runners: Running > 30 min with no CPU activity
+  kubectl get ephemerals -n arc-runners -o json | \
+    jq '.items[] | select(.status.phase=="Running") | .metadata.name'
+  ```
+
+  **Option 3 — Configure autoscaling to replace stuck runners via scale-down:**
+  Set `maxRunners` to a value that triggers KEDA scale-down when load is low.
+  Scale-down deletes idle pods, including stuck ones. Ephemeral runners in the
+  "stuck/waiting" state appear idle to KEDA and will be cleaned up on the next
+  scale-down cycle.
+
+  **Option 4 — Use concurrency groups carefully to reduce cancellations:**
+  Each job cancellation risks creating a stuck runner. Reduce cancellation frequency
+  by scoping concurrency groups more narrowly (per-branch rather than per-repo):
+
+  ```yaml
+  concurrency:
+    group: ${{ github.workflow }}-${{ github.ref }}
+    cancel-in-progress: true
+  ```
+
+  **Option 5 — Upgrade ARC and runner image:**
+  Track the upstream fix in ARC#4307. Check ARC release notes for a fix to the
+  runner's post-cancellation cleanup path. Ensure runner image is on the latest
+  minor version.
+fix_code:
+  - language: yaml
+    label: 'Kubernetes CronJob watchdog to delete stuck ARC ephemeral runners'
+    code: |
+      apiVersion: batch/v1
+      kind: CronJob
+      metadata:
+        name: arc-runner-watchdog
+        namespace: arc-runners
+      spec:
+        schedule: "*/10 * * * *"
+        jobTemplate:
+          spec:
+            template:
+              spec:
+                serviceAccountName: arc-runner-watchdog-sa
+                containers:
+                  - name: watchdog
+                    image: bitnami/kubectl:latest
+                    command:
+                      - /bin/sh
+                      - -c
+                      - |
+                        TIMEOUT_MINUTES=30
+                        NOW=$(date +%s)
+                        kubectl get ephemeralrunners -n arc-runners -o json | \
+                          jq -r --argjson now "$NOW" --argjson timeout "$((TIMEOUT_MINUTES * 60))" \
+                          '.items[] | select(.status.phase=="Running") |
+                          select(($now - (.metadata.creationTimestamp | fromdateiso8601)) > $timeout) |
+                          .metadata.name' | \
+                          xargs -r -I{} kubectl delete ephemeralrunner {} -n arc-runners
+                restartPolicy: OnFailure
+  - language: yaml
+    label: 'Narrow concurrency groups to reduce job cancellations hitting ARC'
+    code: |
+      name: CI
+      on:
+        push:
+          branches: ['**']
+        pull_request:
+      concurrency:
+        # Scope to branch — only cancels duplicate runs on the same branch,
+        # not across all branches (reduces how often ARC runners get hit by cancellations)
+        group: ${{ github.workflow }}-${{ github.ref }}
+        cancel-in-progress: true
+      jobs:
+        build:
+          runs-on:
+            group: my-scale-set
+          steps:
+            - uses: actions/checkout@v4
+            - run: make build
+prevention:
+  - "Monitor EphemeralRunner pod ages; any pod in Running phase beyond 2x your longest job duration is likely stuck"
+  - "Use narrow concurrency group scopes (per-branch) to minimize the frequency of job cancellations hitting ARC runners"
+  - "Configure KEDA scale-down (minRunners: 0 during off-hours) to naturally clear stuck runner pods"
+  - "Keep ARC controller and runner image on the latest stable release; the stuck-on-cancel bug has active upstream attention in ARC#4307"
+  - "For high-cancellation workflows (PR push loops), consider using GitHub-hosted runners which handle cancellation cleanup server-side"
+docs:
+  - url: 'https://github.com/actions/actions-runner-controller/issues/4307'
+    label: 'ARC#4307: Ephemeral Runners get stuck when job is canceled or interrupted (11 reactions, open)'
+  - url: 'https://github.com/actions/actions-runner-controller/blob/master/docs/gha-runner-scale-set-controller/README.md'
+    label: 'ARC: GitHub Actions Runner Scale Set documentation'
+  - url: 'https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/troubleshooting-actions-runner-controller-errors'
+    label: 'GitHub Docs: Troubleshooting ARC errors'

package/errors/silent-failures/silent-failures-120.yml

@@ -0,0 +1,132 @@
+id: silent-failures-120
+title: 'github.event.schedule returns stale cron expression for 1-2 runs after updating workflow schedule'
+category: silent-failures
+severity: silent-failure
+tags:
+  - schedule
+  - cron
+  - github.event.schedule
+  - stale-value
+  - routing
+  - trigger-payload
+patterns:
+  - regex: 'github\.event\.schedule.*[0-9\*\/\-\,]+'
+    flags: 'i'
+  - regex: 'Unknown schedule:\s+[0-9\*\/\-\, ]+'
+    flags: 'i'
+  - regex: 'Evaluating String.*=>\s+''[0-9\*\/\-\, ]+'''
+    flags: 'i'
+error_messages:
+  - "Error: Unknown schedule: 0 5 * * *"
+  - "##[debug]....=> '0 5 * * *'"
+  - "github.event.schedule evaluates to removed cron expression"
+root_cause: |
+  GitHub's schedule dispatcher caches the cron expression strings associated with
+  each workflow internally. When a workflow's `on.schedule` block is updated (cron
+  expression changed or removed) and pushed to the default branch, the dispatcher's
+  internal state does not immediately sync with the new YAML. For 1-2 scheduled runs
+  after the change, the dispatcher fires the workflow with the OLD cron expression
+  in `github.event.schedule`, even though the executed YAML already contains the
+  updated cron string.
+
+  This means:
+  - A workflow with routing logic such as `if: github.event.schedule == '0 5 * * 1-5'`
+    silently skips those steps during the transition window
+  - A `case`/`switch`-style step that branches on `github.event.schedule` hits an
+    "unknown schedule" branch and logs a confusing error
+  - Multi-schedule workflows that use `github.event.schedule` to dispatch different jobs
+    produce wrong results for 1-2 runs post-update
+
+  The stale value typically clears within the next scheduled trigger cycle once the
+  dispatcher re-reads the updated workflow YAML from the default branch. The actual
+  workflow code that runs is the CURRENT version — only the event payload is stale.
+
+  Source: actions/runner#4241 (Feb 2026) — real-world failure confirmed in
+  ava-labs/firewood with stale '0 5 * * *' firing after update to '0 5 * * 1-5',
+  with debug logs showing the old value in the evaluator.
+fix: |
+  **Option 1 — Use a fallback in cron-routing logic:**
+  When switching cron expressions, treat the transition period gracefully by adding
+  the OLD expression to your routing logic temporarily. After 2-3 scheduled cycles,
+  remove the old branch.
+
+  **Option 2 — Avoid routing on github.event.schedule entirely:**
+  Use separate workflow files for each schedule instead of branching inside one
+  workflow on `github.event.schedule`. Each schedule in its own file has an
+  independent dispatch state.
+
+  **Option 3 — Trigger a manual run after updating the schedule:**
+  After pushing the cron change, trigger the workflow via `workflow_dispatch` once.
+  This forces the dispatcher to re-evaluate the workflow file and typically clears
+  the stale state before the next real scheduled run.
+
+  **Option 4 — Accept and handle the stale run:**
+  Add a default/fallback case to your routing logic that gracefully handles an
+  unexpected `github.event.schedule` value rather than erroring:
+
+  ```yaml
+  - name: Route by schedule
+    run: |
+      case "${{ github.event.schedule }}" in
+        '0 5 * * 1-5') echo "Weekday run" ;;
+        '0 5 * * 6')   echo "Saturday run" ;;
+        *)             echo "Unknown schedule (possibly stale): ${{ github.event.schedule }}; skipping" ;;
+      esac
+  ```
+fix_code:
+  - language: yaml
+    label: 'Use separate workflows per schedule (avoids routing entirely)'
+    code: |
+      # weekday-job.yml
+      on:
+        schedule:
+          - cron: '0 5 * * 1-5'
+      jobs:
+        weekday:
+          runs-on: ubuntu-latest
+          steps:
+            - run: echo "Weekday build"
+
+      # saturday-job.yml
+      on:
+        schedule:
+          - cron: '0 5 * * 6'
+      jobs:
+        saturday:
+          runs-on: ubuntu-latest
+          steps:
+            - run: echo "Saturday build"
+  - language: yaml
+    label: 'Graceful fallback case when routing on github.event.schedule'
+    code: |
+      on:
+        schedule:
+          - cron: '0 5 * * 1-5'
+          - cron: '0 5 * * 6'
+      jobs:
+        dispatch:
+          runs-on: ubuntu-latest
+          steps:
+            - name: Route by schedule
+              run: |
+                case "${{ github.event.schedule }}" in
+                  '0 5 * * 1-5') echo "Weekday build" ;;
+                  '0 5 * * 6')   echo "Saturday build" ;;
+                  # Fallback handles stale values during transition window
+                  *)
+                    echo "Unrecognized schedule value: '${{ github.event.schedule }}'"
+                    echo "This may be a stale value from before a recent schedule update."
+                    echo "Skipping; next run should carry the updated expression."
+                    ;;
+                esac
+prevention:
+  - "Never rely on github.event.schedule routing immediately after updating a cron expression; allow 2-3 cycles for dispatcher state to sync"
+  - "Prefer separate workflow files per schedule rather than branching on github.event.schedule inside a single workflow"
+  - "When routing on github.event.schedule is necessary, always include a default/fallback case that handles unexpected values gracefully"
+  - "Trigger a workflow_dispatch run after updating a cron expression to force dispatcher re-evaluation before the next scheduled cycle"
+  - "Add a debug step that logs github.event.schedule at the start of scheduled workflows to surface stale values immediately"
+docs:
+  - url: 'https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#schedule'
+    label: 'GitHub Docs: schedule event'
+  - url: 'https://github.com/actions/runner/issues/4241'
+    label: 'actions/runner#4241: Cron scheduled returns stale cron expression after updating workflow schedule triggers'

package/errors/yaml-syntax/yaml-syntax-077.yml

@@ -0,0 +1,141 @@
+id: yaml-syntax-077
+title: 'VS Code GitHub Actions extension / languageservices emits false "Context access might be invalid" warning for secrets.*, vars.*, needs.* in valid regular workflows'
+category: yaml-syntax
+severity: warning
+tags:
+  - vscode
+  - languageservices
+  - false-positive
+  - secrets-context
+  - vars-context
+  - needs-context
+  - linting
+  - actionlint
+patterns:
+  - regex: 'Context access might be invalid:\s+secrets\.'
+    flags: 'i'
+  - regex: 'Context access might be invalid:\s+vars\.'
+    flags: 'i'
+  - regex: 'Context access might be invalid:\s+needs\.'
+    flags: 'i'
+  - regex: 'Unrecognized named-value:\s+''secrets'''
+    flags: 'i'
+error_messages:
+  - "Context access might be invalid: secrets.MY_SECRET"
+  - "Context access might be invalid: vars.MY_VAR"
+  - "Context access might be invalid: needs.build.outputs.artifact-path"
+  - "Unrecognized named-value: 'secrets'"
+root_cause: |
+  The VS Code GitHub Actions extension (github.vscode-github-actions) uses the
+  `@actions/languageservices` package for workflow linting and IntelliSense. The
+  language server performs static analysis without access to the repository's actual
+  secrets, variables, or environment configuration. It emits "Context access might
+  be invalid" warnings in several scenarios where the workflow is in fact correct:
+
+  1. **Repository-level secrets and variables**: The language server cannot query
+     the repository's secrets or variables store, so any `secrets.MY_SECRET` or
+     `vars.MY_VAR` reference triggers a warning. This affects every workflow that
+     uses custom secrets or variables — i.e., nearly all real-world workflows.
+
+  2. **Dynamic environment secrets**: When a workflow uses `environment: ${{ ... }}`
+     with an expression to select the environment at runtime, the language server
+     cannot statically resolve which environment's secrets are accessible. Even
+     validly scoped `secrets.*` references under dynamic environments are flagged.
+
+  3. **needs.* context across complex job dependency graphs**: The language server
+     sometimes flags `needs.X.outputs.Y` as invalid when job X is defined in the
+     same workflow but the graph is not trivially linear, or when `needs:` contains
+     a list of multiple dependencies.
+
+  **Why this is a false positive:**
+  The warnings are generated by the language server's static type system, which
+  requires compile-time knowledge of what secrets/variables exist. GitHub Actions
+  resolves these at runtime from the repository/organization secrets store — a
+  source the language server has no access to. The workflow runs correctly at
+  runtime; only the editor shows red squiggles.
+
+  This is an open known issue tracked in actions/languageservices#239 (assigned
+  to GitHub staff, reopened after partial fixes). Multiple VS Code extension issues
+  document the same root cause: vscode-github-actions#461, #452, #375, #533.
+
+  **Scope**: Affects anyone using the VS Code GitHub Actions extension
+  (github.vscode-github-actions) v0.x and v1.x with workflows using secrets,
+  variables, or multi-job dependency outputs. NOT an actionlint issue —
+  actionlint correctly handles these cases without false positives.
+fix: |
+  **Option 1 — Suppress per-line (extension-specific comment):**
+  The language server respects `# ignore` comments to suppress specific warnings.
+  Add a comment on the line preceding the flagged expression:
+
+  ```yaml
+  env:
+    # ignore: context-access-might-be-invalid
+    MY_VAR: ${{ secrets.MY_SECRET }}
+  ```
+
+  Note: This syntax is not standardized and may change with extension updates.
+
+  **Option 2 — Disable specific diagnostics in VS Code settings:**
+  In `.vscode/settings.json`, disable the diagnostic class:
+
+  ```json
+  {
+    "github-actions.workflows.pinned.refresh.enabled": true
+  }
+  ```
+
+  **Option 3 — Ignore and trust runtime behavior:**
+  This is a false positive — the workflow will run correctly. If the warning is
+  distracting, the safest approach is to acknowledge it as a known extension
+  limitation and verify by running the workflow. GitHub Actions runtime correctly
+  resolves secrets, vars, and needs contexts.
+
+  **Option 4 — Use actionlint for CI-level linting (no false positives for secrets):**
+  `actionlint` does not flag `secrets.*` references as invalid (it correctly
+  treats them as opaque strings). For CI integration, prefer actionlint over
+  the VS Code extension's linter for automated checks.
+fix_code:
+  - language: yaml
+    label: 'Workflow using secrets and vars — runs correctly despite VS Code warnings'
+    code: |
+      # This workflow is valid — VS Code warns but GitHub Actions runs it correctly.
+      # The "Context access might be invalid" warnings for secrets.* and vars.*
+      # are false positives from the languageservices static analyzer.
+      name: Deploy
+      on:
+        push:
+          branches: [main]
+      jobs:
+        deploy:
+          runs-on: ubuntu-latest
+          environment: production
+          steps:
+            - name: Use secret (VS Code may warn here — ignore it)
+              run: echo "Deploying..."
+              env:
+                API_KEY: ${{ secrets.API_KEY }}         # false positive warning
+                BASE_URL: ${{ vars.DEPLOY_BASE_URL }}   # false positive warning
+  - language: json
+    label: 'VS Code settings.json — disable noisy extension diagnostics'
+    code: |
+      {
+        "github-actions.workflows.pinned.refresh.enabled": true,
+        "github-actions.org-secrets.enabled": false
+      }
+prevention:
+  - "Do not suppress workflow secrets or variables based on VS Code warnings — verify by actually running the workflow"
+  - "Use actionlint for CI-integrated linting; it handles secrets/vars correctly without false positives"
+  - "Keep the VS Code GitHub Actions extension updated; GitHub staff are actively working on reducing false positives in languageservices"
+  - "Check the languageservices GitHub repo (actions/languageservices) for known false positive issues before filing new bugs"
+  - "When sharing workflow snippets, note that VS Code warnings do not necessarily indicate real problems — always confirm against actual run output"
+docs:
+  - url: 'https://github.com/actions/languageservices/issues/239'
+    label: 'actions/languageservices#239: Context access might be invalid is too aggressive (open, assigned)'
+  - url: 'https://github.com/github/vscode-github-actions/issues/461'
+    label: 'vscode-github-actions#461: Unrecognized Github Actions Secret Context (false positive)'
+  - url: 'https://github.com/github/vscode-github-actions/issues/452'
+    label: 'vscode-github-actions#452: False warning for actions/checkout: Context access might be invalid'
+  - url: 'https://github.com/github/vscode-github-actions/issues/375'
+    label: 'vscode-github-actions#375: false positive error on secrets context access in forks'
+  - url: 'https://github.com/rhysd/actionlint'
+    label: 'actionlint: alternative linter that handles secrets/vars without false positives'

package/package.json

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