@htekdev/actions-debugger 1.0.69 → 1.0.71

package/errors/known-unsolved/copilot-code-review-consumes-actions-minutes.yml

@@ -0,0 +1,103 @@
+id: known-unsolved-044
+title: 'Copilot code review consumes GitHub Actions minutes on private repositories — unexpected billing from June 1, 2026'
+category: known-unsolved
+severity: limitation
+tags:
+  - copilot
+  - copilot-code-review
+  - billing
+  - actions-minutes
+  - private-repos
+  - spending-limit
+patterns:
+  - regex: 'copilot.*code.*review.*actions.*minutes'
+    flags: 'i'
+  - regex: 'spending limit.*github actions'
+    flags: 'i'
+  - regex: 'exceeded.*spending limit.*copilot'
+    flags: 'i'
+error_messages:
+  - 'GitHub Actions minutes unexpectedly consumed by Copilot code review jobs'
+  - 'Actions billing spike after enabling Copilot code review on private repositories'
+root_cause: |
+  Starting June 1, 2026, GitHub Copilot code review shifted to an agentic tool-calling
+  architecture that runs on GitHub Actions using GitHub-hosted runners. As a result, each
+  Copilot code review on a private repository now consumes GitHub Actions minutes in addition
+  to Copilot AI Credits (under the new usage-based billing model).
+
+  This is not an error in your workflow — your existing workflows are unaffected. The issue
+  is an invisible, automatic Actions workflow that GitHub creates and runs internally for
+  each Copilot code review request on your private repos. The runner time shows up in your
+  Actions billing dashboard as unexpected consumption.
+
+  Affected plans:
+  - GitHub Copilot Pro
+  - GitHub Copilot Pro+
+  - GitHub Copilot Business
+  - GitHub Copilot Enterprise
+  This also includes Copilot code reviews from non-licensed users billed via direct org billing.
+
+  The behavior is by design and cannot be disabled — if Copilot code review is active on
+  private repos, Actions minutes will be consumed. The rate depends on the runner type:
+  - Standard GitHub-hosted runners: standard per-minute Actions rates apply
+  - Larger runners: billed at the larger runner rate
+  - Self-hosted runners: no additional Actions minute charges (self-hosted runner costs apply)
+
+  Organizations that had spending limits set low for Actions (or spending limits set to $0)
+  may find that Copilot code reviews start being blocked when the Actions spending limit is hit,
+  causing the review to fail or not run at all — without a clear error message explaining why.
+
+  There is no way to separate "Copilot code review Actions minutes" from regular workflow
+  Actions minutes in the billing dashboard — they are aggregated together.
+fix: |
+  There is no way to opt out of Actions minute consumption for Copilot code review on private
+  repos while keeping Copilot code review enabled. The available mitigations are:
+
+  1. **Use self-hosted runners**: Configure Copilot code review to use self-hosted runners.
+     Self-hosted runner usage does not count toward your GitHub Actions minute allowance.
+     This is the only way to eliminate the per-review Actions minute charge.
+
+  2. **Increase the Actions spending limit**: Review your organization's Actions spending limit
+     in Settings → Billing & Plans → Spending limits. Ensure the limit covers the expected
+     volume of Copilot code reviews in addition to your regular Actions usage.
+
+  3. **Set up budget controls**: Use GitHub's usage-based billing budget controls to set
+     per-user or organization-wide spending caps for Actions to prevent surprise overages.
+
+  4. **Monitor proactively**: Use GitHub Actions metrics and the Billing Usage Report to
+     track combined Actions + Copilot consumption before the end of the billing cycle.
+
+  5. **Public repositories**: Copilot code review on public repositories does not consume
+     Actions minutes (Actions minutes remain free for public repos).
+fix_code:
+  - language: yaml
+    label: 'No workflow change needed — this is a billing configuration issue, not a workflow error'
+    code: |
+      # There is no workflow YAML to change.
+      # To use self-hosted runners for Copilot code review, configure the runner
+      # in your organization or repository settings:
+      #   Settings → Actions → Runners → Add runner
+      # Then configure Copilot code review to use that runner label.
+      #
+      # To check your Actions spending limit:
+      #   Settings → Billing & Plans → Spending limits → GitHub Actions
+      #
+      # Example: setting up a budget alert for Actions usage
+      # (done in GitHub UI or via REST API, not workflow YAML)
+      #
+      # Regular workflows are unaffected — no changes needed to existing .yml files.
+prevention:
+  - 'Before enabling Copilot code review on private repositories, review your current GitHub Actions spending limit and adjust if needed'
+  - 'Monitor Actions usage in the first billing cycle after enabling Copilot code review to calibrate expected consumption'
+  - 'Configure self-hosted runners for Copilot code review to eliminate per-review Actions minute charges'
+  - 'Set an explicit Actions spending limit (not $0) to avoid Copilot reviews silently failing when the limit is hit'
+  - 'Public repositories are exempt — Copilot code review on public repos does not consume Actions minutes'
+docs:
+  - url: 'https://github.blog/changelog/2026-04-27-github-copilot-code-review-will-start-consuming-github-actions-minutes-on-june-1-2026/'
+    label: 'GitHub Changelog: Copilot code review will start consuming Actions minutes on June 1, 2026'
+  - url: 'https://github.blog/changelog/2026-06-01-updates-to-github-copilot-billing-and-plans/'
+    label: 'GitHub Changelog: Copilot billing updates — usage-based billing is active (June 1, 2026)'
+  - url: 'https://docs.github.com/en/billing/managing-billing-for-your-products/managing-billing-for-github-actions/about-billing-for-github-actions'
+    label: 'GitHub Docs: About billing for GitHub Actions'
+  - url: 'https://docs.github.com/en/copilot/github-copilot-enterprise/copilot-code-review/using-github-copilot-code-review'
+    label: 'GitHub Docs: Using GitHub Copilot code review'

package/errors/known-unsolved/ubuntu-arm64-images-frozen-github-transition.yml

@@ -0,0 +1,114 @@
+id: known-unsolved-045
+title: 'ubuntu-24.04-arm and ubuntu-22.04-arm runner images paused during GitHub Arm64 takeover — no package updates during transition'
+category: known-unsolved
+severity: limitation
+tags:
+  - arm64
+  - ubuntu-arm
+  - runner-images
+  - partner-runner-images
+  - package-updates
+  - security-updates
+patterns:
+  - regex: 'ubuntu-24\.04-arm'
+    flags: 'i'
+  - regex: 'ubuntu-22\.04-arm'
+    flags: 'i'
+  - regex: 'partner-runner-images'
+    flags: 'i'
+error_messages:
+  - 'No recent runner-images release notes for ubuntu-24.04-arm during migration period'
+  - 'Package version pinned to stale ubuntu-arm runner image during GitHub transition'
+root_cause: |
+  In May 2026, GitHub announced it was taking ownership of the Arm64 runner images for
+  GitHub Actions hosted runners, transitioning them away from Arm Limited, LLC (previously
+  maintained in the actions/partner-runner-images repository).
+
+  During this transition period:
+  - ubuntu-24.04-arm and ubuntu-22.04-arm images WILL NOT receive updates
+  - No new release notes appear in actions/runner-images for these images during migration
+  - The actions/partner-runner-images repository is being archived
+  - All open issues and future support are moving to actions/runner-images
+
+  This means workflows running on ubuntu-24.04-arm or ubuntu-22.04-arm during the
+  transition period (May 2026 until migration completes) are running on stale images that
+  may have:
+  - Unpatched security vulnerabilities (CVEs disclosed after the freeze date)
+  - Missing package versions that were released after the freeze date
+  - Outdated tool versions (e.g., Docker, Node.js, Python) compared to the x86 equivalents
+
+  The exact duration of the freeze is not published — GitHub states "during the transition."
+  Developers who pin specific package or tool versions that are only available in newer
+  releases may find those versions unavailable on arm runners while they are available on
+  the x86 equivalents.
+
+  This is a known, intentional operational decision by GitHub during the infrastructure
+  migration. There is no error message — workflows simply run on stale images silently.
+fix: |
+  There is no immediate fix since the image freeze is a deliberate infrastructure choice
+  during the migration. Available mitigations:
+
+  1. **Track the migration status**: Monitor the actions/runner-images repository for
+     announcements about when the Ubuntu Arm64 images resume updates. GitHub has indicated
+     the partner-runner-images repo will be archived after the transition completes.
+
+  2. **Report critical issues directly**: For CVEs or critical vulnerabilities in the arm
+     images during the transition, open an issue in actions/runner-images (NOT
+     actions/partner-runner-images, which is being archived).
+
+  3. **Avoid pinning to specific recent package versions on arm runners**: If your workflow
+     installs packages with exact version pinning, add a fallback or use the latest available
+     version rather than a specific recent release that may not be in the frozen image.
+
+  4. **Use self-hosted Arm64 runners**: If the image freeze causes unacceptable security or
+     tool-version risk, consider switching to self-hosted Arm64 runners where you control
+     the image update cadence.
+
+  5. **Test cross-architecture differences**: If workflows behave differently on x86 vs arm
+     during this period, check whether the discrepancy is due to the arm image being stale
+     rather than a genuine architecture difference.
+fix_code:
+  - language: yaml
+    label: 'Use self-hosted Arm64 runner to bypass the frozen GitHub-hosted arm image'
+    code: |
+      jobs:
+        arm-build:
+          # Temporarily use a self-hosted arm runner if the GitHub-hosted arm image
+          # is missing security patches or required packages during the migration period.
+          # Replace with ubuntu-24.04-arm once GitHub resumes image updates.
+          runs-on: self-hosted-arm64
+
+          steps:
+            - uses: actions/checkout@v4
+
+            - name: Build on Arm64
+              run: make build
+
+  - language: yaml
+    label: 'Avoid pinning exact recent package versions on arm runners during the transition'
+    code: |
+      jobs:
+        arm-build:
+          runs-on: ubuntu-24.04-arm
+          steps:
+            - uses: actions/checkout@v4
+
+            # AVOID: pinning to a very recent package version that may not be in frozen image
+            # - run: apt-get install -y libexample=2.6.3-1
+
+            # PREFER: install latest available version from the frozen image's apt cache
+            - run: |
+                sudo apt-get update
+                sudo apt-get install -y libexample
+prevention:
+  - 'Monitor actions/runner-images (not actions/partner-runner-images) for Ubuntu Arm64 image update resumption announcements'
+  - 'For security-sensitive workloads on arm runners, track CVE advisories against the frozen image versions until the transition completes'
+  - 'Avoid cross-architecture version pinning assumptions — package versions on arm images may lag x86 images during the transition period'
+  - 'Open issues for Arm64 runner image problems in actions/runner-images — the partner-runner-images repository is being archived and will no longer receive support'
+docs:
+  - url: 'https://github.blog/changelog/2026-05-14-github-actions-upcoming-image-migrations/'
+    label: 'GitHub Changelog: GitHub Actions Upcoming image migrations — Arm64 takeover (May 2026)'
+  - url: 'https://github.com/actions/runner-images'
+    label: 'actions/runner-images — new home for all runner image issues including Arm64'
+  - url: 'https://github.com/actions/partner-runner-images'
+    label: 'actions/partner-runner-images — being archived after Arm64 transition completes'

package/errors/permissions-auth/create-github-app-token-expires-one-hour.yml

@@ -0,0 +1,124 @@
+id: permissions-auth-046
+title: 'actions/create-github-app-token output token expires after 1 hour — long-running jobs hit 401 Unauthorized'
+category: permissions-auth
+severity: error
+tags:
+  - github-app
+  - installation-token
+  - token-expiry
+  - create-github-app-token
+  - long-running-jobs
+patterns:
+  - regex: '401 Unauthorized'
+    flags: 'i'
+  - regex: 'Bad credentials'
+    flags: 'i'
+  - regex: 'installation.*token.*expired'
+    flags: 'i'
+  - regex: 'HttpError: Bad credentials'
+    flags: 'i'
+error_messages:
+  - '401 Unauthorized'
+  - 'Bad credentials'
+  - 'HttpError: Bad credentials'
+  - 'Installation tokens expire one hour from the time you create them'
+root_cause: |
+  GitHub App installation tokens — generated by actions/create-github-app-token — have a fixed
+  1-hour expiry enforced by the GitHub platform. The token is generated once at the step where
+  the action runs, stored as a step output, and typically exported to an env var. If subsequent
+  steps take longer than 60 minutes to reach the point where the token is used, all GitHub API
+  calls and authenticated git operations will return 401 Unauthorized or "Bad credentials".
+
+  From GitHub's REST API docs:
+  "Installation tokens expire one hour from the time you create them. Using an expired token
+  produces a status code of 401 - Unauthorized, and requires creating a new installation token."
+
+  Common affected patterns:
+  - Long test suites (>60 min) where a GitHub App token is generated upfront for a final
+    PR comment or status check post at the end.
+  - Build pipelines that generate an app token for private package registry authentication
+    at the start, then run a multi-hour compilation and upload step at the end.
+  - Self-hosted runners on slow networks where upload + deploy sequences exceed 60 minutes.
+  - Jobs that poll or sleep mid-run (e.g., waiting for an external deployment to stabilize).
+
+  Important: The built-in GITHUB_TOKEN is NOT subject to this expiry — it remains valid for
+  the entire job duration (up to the job's timeout-minutes). Only tokens from
+  actions/create-github-app-token or direct GitHub App JWT exchanges expire after 1 hour.
+fix: |
+  Generate a fresh GitHub App token immediately before the step that needs it rather than
+  once at the beginning of the job. For jobs that have multiple distinct phases requiring
+  the token, generate a separate token for each phase. Alternatively, split long-running
+  work into shorter jobs — each job generates its own fresh token on startup.
+fix_code:
+  - language: yaml
+    label: 'Generate token immediately before the step that needs it (not at job start)'
+    code: |
+      jobs:
+        long-build:
+          runs-on: ubuntu-latest
+          steps:
+            - name: Checkout
+              uses: actions/checkout@v4
+
+            - name: Run long test suite
+              # This may run for over an hour
+              run: make test
+
+            # Generate a fresh token just before the API call — never stale
+            - name: Generate GitHub App token
+              id: app-token
+              uses: actions/create-github-app-token@v2
+              with:
+                app-id: ${{ vars.APP_ID }}
+                private-key: ${{ secrets.APP_PRIVATE_KEY }}
+
+            - name: Post PR comment
+              env:
+                GH_TOKEN: ${{ steps.app-token.outputs.token }}
+              run: |
+                gh pr comment ${{ github.event.pull_request.number }} \
+                  --body "Tests completed successfully"
+
+  - language: yaml
+    label: 'Split into sub-jobs so each job generates its own short-lived token'
+    code: |
+      jobs:
+        long-tests:
+          runs-on: ubuntu-latest
+          steps:
+            - uses: actions/checkout@v4
+            - run: make test
+
+        notify:
+          runs-on: ubuntu-latest
+          needs: [long-tests]
+          steps:
+            # Each job generates a token on startup — always fresh
+            - name: Generate GitHub App token
+              id: app-token
+              uses: actions/create-github-app-token@v2
+              with:
+                app-id: ${{ vars.APP_ID }}
+                private-key: ${{ secrets.APP_PRIVATE_KEY }}
+
+            - name: Post PR comment
+              env:
+                GH_TOKEN: ${{ steps.app-token.outputs.token }}
+              run: |
+                gh pr comment ${{ github.event.pull_request.number }} \
+                  --body "Tests completed successfully"
+prevention:
+  - "Never store a GitHub App installation token at job start assuming it stays valid — generate it immediately before use"
+  - "For jobs expected to run longer than 45 minutes, split into sub-jobs so each generates its own fresh token"
+  - "Prefer the built-in GITHUB_TOKEN for operations within the same repository — it is valid for the entire job duration"
+  - "Set job-level timeout-minutes to catch unexpectedly long jobs and keep total runtime well under the 1-hour token expiry"
+  - "The actions/create-github-app-token README prominently warns: 'An installation access token expires after 1 hour'"
+docs:
+  - url: 'https://docs.github.com/en/apps/creating-github-apps/authenticating-with-a-github-app/generating-an-installation-access-token-for-a-github-app'
+    label: 'Generating an installation access token — expires after 1 hour (GitHub Docs)'
+  - url: 'https://github.com/actions/create-github-app-token'
+    label: 'actions/create-github-app-token — README warning about 1-hour expiry'
+  - url: 'https://github.com/actions/create-github-app-token/issues/128'
+    label: 'actions/create-github-app-token#128 — token only lasts 1 hour, long-running jobs fail'
+  - url: 'https://docs.github.com/en/actions/security-for-github-actions/security-guides/automatic-token-authentication'
+    label: 'GITHUB_TOKEN automatic token authentication — valid for entire job duration'

package/errors/runner-environment/actions-core-v3-esm-only-require-fails.yml

@@ -0,0 +1,136 @@
+id: runner-environment-131
+title: '@actions/core 3.0.0 is ESM-only — custom JavaScript actions using require() fail with ERR_REQUIRE_ESM'
+category: runner-environment
+severity: error
+tags:
+  - esm
+  - commonjs
+  - actions-core
+  - custom-action
+  - javascript
+  - toolkit
+patterns:
+  - regex: 'ERR_REQUIRE_ESM'
+    flags: 'i'
+  - regex: 'No "exports" main defined in @actions/core'
+    flags: 'i'
+  - regex: 'require\(\) of ES Module.*@actions/core'
+    flags: 'i'
+  - regex: 'Must use import to load ES Module'
+    flags: 'i'
+error_messages:
+  - 'Error [ERR_REQUIRE_ESM]: require() of ES Module .../node_modules/@actions/core/lib/core.js not supported'
+  - 'No "exports" main defined in @actions/core/package.json @v3'
+  - 'Must use import to load ES Module: .../node_modules/@actions/core/lib/core.js'
+root_cause: |
+  @actions/core version 3.0.0 (published January 29, 2026) converted the package from CommonJS
+  to ESM-only. Before v3, the package shipped as CommonJS and was consumable with:
+
+    const core = require('@actions/core');
+
+  With v3.0.0 and later, the package is ESM-only. CommonJS callers that use require() receive
+  one of these errors at runtime:
+
+    - ERR_REQUIRE_ESM: Node.js refuses to require() an ES module
+    - "No 'exports' main defined in @actions/core/package.json @v3" — the ESM package.json
+      exports map does not expose a CommonJS entry point
+
+  This affects any custom JavaScript or TypeScript action that:
+  1. Uses require('@actions/core') — e.g., const core = require('@actions/core');
+  2. Uses TypeScript compiled to CommonJS (the default 'module': 'commonjs' in tsconfig.json)
+     even when source code uses import syntax — the compiled output uses require() calls
+  3. Bundles with webpack/ncc in CommonJS mode without transpiling the ESM dependency
+
+  The actions/typescript-action template and thousands of published community actions that
+  were written for @actions/core v1–v2 are affected when their dependencies are updated.
+
+  Note: This is a Node.js runtime error — the workflow definition is valid YAML. The failure
+  appears in the step log when Node.js tries to load the bundled action.
+fix: |
+  There are two approaches depending on whether you control the action source code:
+
+  Option A — Migrate the action to ESM (recommended for new actions):
+  Update the action's package.json to "type": "module", convert all require() calls to
+  import statements, and recompile/rebundle. Use "module": "ESNext" or "module": "NodeNext"
+  in tsconfig.json for TypeScript actions.
+
+  Option B — Pin @actions/core to v2.x (quick fix for existing actions):
+  Pin to the last CommonJS-compatible version: @actions/core@^2.0.3 in package.json.
+  This avoids the ESM migration but misses v3 improvements (new APIs, performance).
+
+  For third-party community actions you don't control: check if the action maintainer has
+  published an updated version. If not, pin the action to the last working version tag
+  (before they upgraded to @actions/core v3).
+fix_code:
+  - language: yaml
+    label: 'Pin @actions/core to v2 in package.json (quick fix for existing CommonJS actions)'
+    code: |
+      # In the action's package.json, pin to v2 (last CommonJS-compatible release)
+      # {
+      #   "dependencies": {
+      #     "@actions/core": "^2.0.3"
+      #   }
+      # }
+      jobs:
+        build-action:
+          runs-on: ubuntu-latest
+          steps:
+            - uses: actions/checkout@v4
+
+            - uses: actions/setup-node@v4
+              with:
+                node-version: '20'
+
+            - name: Install pinned dependencies
+              run: npm ci
+
+            - name: Bundle action
+              run: npm run build
+
+  - language: yaml
+    label: 'Migrate action to ESM — update tsconfig and entry point for @actions/core v3'
+    code: |
+      # tsconfig.json for ESM TypeScript action:
+      # {
+      #   "compilerOptions": {
+      #     "module": "NodeNext",
+      #     "moduleResolution": "NodeNext",
+      #     "target": "ES2020"
+      #   }
+      # }
+      #
+      # package.json:
+      # {
+      #   "type": "module",
+      #   "dependencies": { "@actions/core": "^3.0.0" }
+      # }
+      #
+      # In source, use ESM imports (not require):
+      # import * as core from '@actions/core';
+      jobs:
+        build-esm-action:
+          runs-on: ubuntu-latest
+          steps:
+            - uses: actions/checkout@v4
+            - uses: actions/setup-node@v4
+              with:
+                node-version: '20'
+            - name: Build ESM action
+              run: npm ci && npm run build
+prevention:
+  - 'Always check the @actions/core RELEASES.md when upgrading — v3.0.0 is an ESM-only breaking change requiring migration'
+  - 'TypeScript actions compiled with "module": "commonjs" in tsconfig.json will produce require() calls even if source uses import — set "module": "NodeNext" for ESM compatibility'
+  - 'Use Dependabot or Renovate with a major version constraint so @actions/core upgrades are reviewed before merging'
+  - 'Bundle your action with ncc using --esm flag or use esbuild with format=esm to produce ESM-compatible bundles'
+  - 'Test bundled actions locally with node dist/index.js before publishing to catch ERR_REQUIRE_ESM before CI fails'
+docs:
+  - url: 'https://github.com/actions/toolkit/blob/main/packages/core/RELEASES.md'
+    label: '@actions/core RELEASES.md — v3.0.0 ESM-only breaking change'
+  - url: 'https://github.com/actions/toolkit/issues/2294'
+    label: 'actions/toolkit #2294 — No "exports" main defined in @actions/core/package.json @v3 (8 reactions)'
+  - url: 'https://github.com/actions/toolkit/issues/2287'
+    label: 'actions/toolkit #2287 — Outdated require() docs for ESM packages (5 reactions)'
+  - url: 'https://github.com/actions/typescript-action/issues/1165'
+    label: 'actions/typescript-action #1165 — Example for @actions/core >= 3 migration'
+  - url: 'https://nodejs.org/api/esm.html#interoperability-with-commonjs'
+    label: 'Node.js docs — ESM/CommonJS interoperability'

package/errors/silent-failures/steps-conclusion-always-success-with-continue-on-error.yml

@@ -0,0 +1,90 @@
+id: silent-failures-068
+title: 'steps.<id>.conclusion is always success when continue-on-error: true — using conclusion to detect step failure never triggers'
+category: silent-failures
+severity: silent-failure
+tags:
+  - continue-on-error
+  - steps-context
+  - outcome
+  - conclusion
+  - if-condition
+  - step-failure
+patterns:
+  - regex: 'steps\.\w+\.conclusion\s*==\s*[''"]failure[''"]'
+    flags: 'i'
+  - regex: 'continue-on-error.*true'
+    flags: 'i'
+error_messages:
+  - 'steps.<id>.conclusion == ''failure'' never evaluates to true'
+  - 'cleanup step silently skipped despite step failure'
+root_cause: |
+  GitHub Actions provides two properties on the `steps` context for inspecting a completed step:
+
+  - `steps.<id>.outcome` — the raw result BEFORE `continue-on-error` is applied. Values:
+    `success`, `failure`, `cancelled`, `skipped`.
+  - `steps.<id>.conclusion` — the final result AFTER `continue-on-error` is applied. When
+    `continue-on-error: true` and the step fails, `conclusion` is `success` (not `failure`).
+
+  When a step has `continue-on-error: true` set, a step failure does NOT propagate to
+  `conclusion`. Developers who write:
+
+    if: steps.my-step.conclusion == 'failure'
+
+  expecting to detect when `my-step` failed will find that this condition is NEVER true — even
+  when the step actually failed — because `continue-on-error` overwrites the conclusion to
+  `success`. The downstream step silently never runs.
+
+  This commonly affects:
+  - Cleanup steps that should run when a flaky test step fails (continue-on-error: true)
+  - Notification steps that should alert on specific step failures in a pipeline
+  - Conditional logic that differentiates between "step was skipped" and "step failed"
+fix: |
+  Use `steps.<id>.outcome` (not `conclusion`) to detect the raw result of a step that has
+  `continue-on-error: true`. The `outcome` property reflects the actual step result before
+  the error suppression is applied and correctly returns `failure` even when the final
+  conclusion is `success`.
+fix_code:
+  - language: yaml
+    label: 'WRONG: conclusion is always success when continue-on-error is true — cleanup never runs'
+    code: |
+      steps:
+        - name: Run flaky tests
+          id: tests
+          continue-on-error: true
+          run: pytest tests/
+
+        - name: Send failure notification
+          # NEVER RUNS — conclusion is 'success' even when tests fail
+          if: steps.tests.conclusion == 'failure'
+          run: echo "Tests failed — notifying team"
+
+  - language: yaml
+    label: 'CORRECT: use outcome to detect the raw step result before continue-on-error'
+    code: |
+      steps:
+        - name: Run flaky tests
+          id: tests
+          continue-on-error: true
+          run: pytest tests/
+
+        - name: Send failure notification
+          # CORRECT — outcome reflects the raw result before continue-on-error override
+          if: steps.tests.outcome == 'failure'
+          run: echo "Tests failed — notifying team"
+
+        - name: Always-run cleanup
+          # For cleanup that must run regardless, use always() + outcome check
+          if: always() && steps.tests.outcome != 'success'
+          run: echo "Running cleanup after non-success outcome"
+prevention:
+  - "When a step has continue-on-error: true, always use steps.<id>.outcome (not conclusion) to detect failures in downstream if conditions"
+  - "steps.<id>.conclusion == 'success' is always true when continue-on-error: true — it is safe for 'did this step not skip?' checks only"
+  - "The failure() status function is also bypassed by continue-on-error — use steps.<id>.outcome != 'success' instead"
+  - "Review GitHub Docs context reference table to understand outcome vs conclusion semantics before writing conditional cleanup steps"
+docs:
+  - url: 'https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs#steps-context'
+    label: 'steps context — outcome vs conclusion properties with continue-on-error (GitHub Docs)'
+  - url: 'https://github.com/actions/runner/blob/main/docs/adrs/0274-step-outcome-and-conclusion.md'
+    label: 'actions/runner ADR: outcome vs conclusion design — why two separate properties exist'
+  - url: 'https://stackoverflow.com/questions/71433926/how-do-to-run-the-next-github-action-step-even-if-the-previous-step-failed-whil'
+    label: 'Stack Overflow: using steps.outcome vs steps.conclusion with continue-on-error'

package/errors/triggers/release-published-fires-on-prerelease-creation-and-promotion.yml

@@ -0,0 +1,106 @@
+id: triggers-049
+title: 'on.release types: [published] fires for pre-release creation AND pre-release-to-full promotion — deploy workflows run twice'
+category: triggers
+severity: silent-failure
+tags:
+  - release
+  - published
+  - prerelease
+  - on-release
+  - double-trigger
+  - deploy
+patterns:
+  - regex: 'github\.event\.action.*prereleased'
+    flags: 'i'
+  - regex: 'github\.event\.release\.prerelease.*true'
+    flags: 'i'
+error_messages:
+  - 'github.event.action: prereleased'
+  - 'github.event.action: released'
+  - 'github.event.release.prerelease: true'
+root_cause: |
+  The GitHub `release` event supports multiple activity types: `created`, `published`,
+  `prereleased`, `released`, `edited`, `deleted`, and `unpublished`. The `published` type
+  is frequently misunderstood:
+
+  - `published` fires whenever ANY release is made public — this includes both pre-releases
+    (action=prereleased) and full releases (action=released). It is a superset, not a
+    specific activity type for "final" releases.
+
+  A typical release lifecycle that triggers `on.release.types: [published]` twice:
+  1. Developer creates a pre-release (e.g., v1.2.0-rc.1) and clicks "Publish release"
+     → workflow fires (github.event.action=prereleased, github.event.release.prerelease=true)
+  2. Developer edits the release and unchecks "Set as a pre-release" to promote it to a
+     full release → workflow fires again (github.event.action=released, github.event.release.prerelease=false)
+
+  Additionally, the GitHub docs note that `prereleased` does NOT fire for pre-releases
+  published from a draft release, but `published` DOES fire — creating another asymmetry.
+
+  Workflows using `on.release.types: [published]` for deployment, package publishing,
+  or Docker image tagging will run twice for the same version tag, potentially creating
+  duplicate deployments, duplicate npm/PyPI publishes, or conflicting artifact versions.
+fix: |
+  For production deploy workflows that should only run on final (non-pre-release) releases,
+  add an `if:` condition to check `github.event.release.prerelease == false`. Alternatively,
+  use `types: [released]` — which fires only when a stable release is published directly
+  or when a pre-release is promoted to full release, but NOT on initial pre-release creation.
+
+  To target pre-releases explicitly, use `types: [prereleased]`, but note it does not fire
+  for pre-releases published from drafts (use `published` + `if: github.event.release.prerelease == true`
+  in that case).
+fix_code:
+  - language: yaml
+    label: 'Guard with if condition to skip pre-release publishes'
+    code: |
+      on:
+        release:
+          types: [published]
+
+      jobs:
+        deploy:
+          runs-on: ubuntu-latest
+          # Only deploy for final (non-pre-release) releases
+          if: github.event.release.prerelease == false
+          steps:
+            - name: Deploy release
+              run: echo "Deploying ${{ github.event.release.tag_name }}"
+
+  - language: yaml
+    label: 'Use released type to target only final releases (not pre-release creation)'
+    code: |
+      on:
+        release:
+          # released: fires when a release is published as final, OR when a pre-release
+          # is promoted to a full release. Does NOT fire on initial pre-release creation.
+          types: [released]
+
+      jobs:
+        deploy:
+          runs-on: ubuntu-latest
+          steps:
+            - name: Deploy release
+              run: echo "Deploying ${{ github.event.release.tag_name }}"
+
+  - language: yaml
+    label: 'Log release event fields at the start of release workflows for debugging'
+    code: |
+      jobs:
+        release-info:
+          runs-on: ubuntu-latest
+          steps:
+            - name: Debug release event
+              run: |
+                echo "action: ${{ github.event.action }}"
+                echo "prerelease: ${{ github.event.release.prerelease }}"
+                echo "tag: ${{ github.event.release.tag_name }}"
+                echo "draft: ${{ github.event.release.draft }}"
+prevention:
+  - "Prefer types: [released] over types: [published] for production deployment workflows"
+  - "Always guard release deploy steps with: if: github.event.release.prerelease == false"
+  - "Make deployment and publish workflows idempotent so accidental double-runs cannot cause irreversible side effects"
+  - "Log github.event.action and github.event.release.prerelease at workflow start when debugging unexpected runs"
+docs:
+  - url: 'https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#release'
+    label: 'release event activity types — published fires for both prereleased and released (GitHub Docs)'
+  - url: 'https://stackoverflow.com/questions/78085080/how-to-limit-a-github-action-to-fire-only-once-on-a-release-trigger'
+    label: 'Stack Overflow: release action triggered 3 times for pre-release — limit using types and if conditions'

package/errors/yaml-syntax/paths-and-paths-ignore-combined-on-same-event.yml

@@ -0,0 +1,97 @@
+id: yaml-syntax-045
+title: 'Using paths and paths-ignore together on the same event trigger causes a workflow validation error'
+category: yaml-syntax
+severity: error
+tags:
+  - paths
+  - paths-ignore
+  - trigger-filter
+  - on-push
+  - validation-error
+patterns:
+  - regex: "You can't use both 'paths' and 'paths-ignore'"
+    flags: 'i'
+  - regex: 'Invalid workflow file.*paths.*paths-ignore'
+    flags: 'i'
+  - regex: 'paths.*and.*paths-ignore.*cannot.*same event'
+    flags: 'i'
+error_messages:
+  - "Invalid workflow file: You can't use both 'paths' and 'paths-ignore' for the same event trigger"
+  - "You can't use both 'paths' and 'paths-ignore' for the same event trigger"
+  - "Path and Path-ignore cannot be added in the same event"
+root_cause: |
+  GitHub Actions enforces a mutual exclusivity rule: `paths` and `paths-ignore` cannot be
+  specified simultaneously for the same event trigger. The same rule applies to:
+  - `branches` and `branches-ignore`
+  - `tags` and `tags-ignore`
+
+  `paths` is an allowlist — the trigger only fires when at least one of the listed patterns
+  matches a changed file. `paths-ignore` is a denylist — the trigger is suppressed when ALL
+  changed files match patterns in the list. Because their semantics are complementary, GitHub
+  disallows combining them to avoid ambiguous filter behavior.
+
+  Attempting to use both results in a validation error at workflow parse time:
+  "Invalid workflow file: You can't use both 'paths' and 'paths-ignore' for the same event trigger"
+
+  Developers commonly hit this when they want to trigger on a specific directory but exclude
+  documentation or test-only changes within that directory, assuming both filters can be
+  stacked like CSS selectors.
+
+  Example of the problematic pattern:
+    on:
+      push:
+        paths:
+          - 'src/**'
+        paths-ignore:          # INVALID: cannot combine with paths
+          - 'src/**/*.md'
+fix: |
+  Use only one of `paths` or `paths-ignore`. To achieve both include and exclude behavior
+  within a single filter:
+  - Use the `paths` filter with `!` negation patterns to explicitly exclude paths from an
+    allowlist. List all positive patterns before negative patterns — order matters.
+  - Alternatively, use `paths-ignore` alone if you just need to exclude a small set of paths
+    and want the workflow to run for everything else.
+fix_code:
+  - language: yaml
+    label: 'WRONG: paths and paths-ignore combined (validation error)'
+    code: |
+      # This is INVALID — causes "You can't use both" validation error
+      on:
+        push:
+          paths:
+            - 'src/**'
+          paths-ignore:
+            - 'src/**/*.md'
+
+  - language: yaml
+    label: 'CORRECT: use paths with negation pattern to exclude within an allowlist'
+    code: |
+      # Use ! negation in paths to exclude specific sub-paths from the allowlist
+      on:
+        push:
+          paths:
+            - 'src/**'          # include all changes under src/
+            - '!src/**/*.md'    # but exclude markdown files within src/
+
+  - language: yaml
+    label: 'CORRECT: use only paths-ignore to suppress trigger for specific paths'
+    code: |
+      # If the workflow should run for everything EXCEPT docs, use paths-ignore alone
+      on:
+        push:
+          paths-ignore:
+            - 'docs/**'
+            - '**/*.md'
+            - '**/*.txt'
+prevention:
+  - "Never combine paths with paths-ignore (or branches/branches-ignore, or tags/tags-ignore) for the same event"
+  - "To include a directory but exclude sub-paths: use paths with ! negation entries"
+  - "Use actionlint to validate workflow YAML locally before pushing — it catches this misconfiguration"
+  - "The same mutual exclusivity rule applies to branches/branches-ignore and tags/tags-ignore"
+docs:
+  - url: 'https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpaths'
+    label: 'on.push.paths — cannot be used with paths-ignore for the same event (GitHub Docs)'
+  - url: 'https://stackoverflow.com/questions/64896276/github-action-trigger-pipeline-for-root-folder-except-one-sub-folder'
+    label: 'Stack Overflow: "Path and Path-ignore cannot be added in the same event" — use ! negation in paths instead'
+  - url: 'https://github.com/rhysd/actionlint'
+    label: 'actionlint — static checker for GitHub Actions workflow files'

package/errors/yaml-syntax/schedule-timezone-actionlint-unknown-key.yml

@@ -0,0 +1,135 @@
+id: yaml-syntax-046
+title: 'on.schedule timezone field causes actionlint and third-party parsers to report "expected cron key" syntax error'
+category: yaml-syntax
+severity: warning
+tags:
+  - schedule
+  - cron
+  - timezone
+  - actionlint
+  - linting
+  - scorecard-action
+patterns:
+  - regex: 'expected "cron" key for element of "schedule" section but got "timezone"'
+    flags: 'i'
+  - regex: 'unable to parse github workflow.*timezone'
+    flags: 'i'
+  - regex: 'workflow verification failed.*timezone.*syntax-check'
+    flags: 'i'
+  - regex: '\[syntax-check\].*timezone'
+    flags: 'i'
+error_messages:
+  - 'expected "cron" key for element of "schedule" section but got "timezone" [syntax-check]'
+  - 'error sending scorecard results to webapp: http response 400, status: 400 Bad Request, error: {"code":400,"message":"workflow verification failed: unable to parse github workflow: [:9:7: expected \"cron\" key for element of \"schedule\" section but got \"timezone\" [syntax-check]]"}'
+  - 'on.schedule[0]: unexpected key "timezone"'
+root_cause: |
+  GitHub Actions added IANA timezone support for scheduled workflows in March 2026
+  (announced in the Late March 2026 changelog). The new syntax allows specifying a timezone
+  alongside the cron expression:
+
+    on:
+      schedule:
+        - cron: '30 5 * * 1-5'
+          timezone: "America/New_York"
+
+  However, this feature was not immediately recognized by external workflow-parsing tools:
+
+  1. **actionlint** — The widely-used GitHub Actions linting tool (used in many CI pipelines
+     as a pre-commit or CI check) did not support the timezone key until version 0.7.4
+     (released March 30, 2026). Earlier versions report the error:
+       expected "cron" key for element of "schedule" section but got "timezone" [syntax-check]
+     This causes actionlint-based CI checks to fail even though the workflow is valid.
+
+  2. **ossf/scorecard-action** — The OpenSSF Scorecard action verifies workflow structure
+     using an internal parser that did not recognize the timezone key. When scorecard-action
+     runs on a workflow that contains `timezone:`, it returns HTTP 400 from the Scorecard API:
+       workflow verification failed: unable to parse github workflow: [...timezone [syntax-check]]
+     This causes the scorecard CI job to fail on otherwise-valid workflows.
+
+  3. **GitHub VS Code extension** — The vscode-github-actions extension (v0.29.1 and earlier)
+     marks timezone as an "unexpected value" in the schema validation overlay, producing
+     squiggly underlines even though the workflow runs correctly.
+
+  The root issue is that the new timezone key was added to GitHub's workflow syntax faster
+  than third-party tooling could update their schema definitions.
+fix: |
+  Upgrade the affected tools to versions that support the timezone key:
+
+  1. **actionlint**: Upgrade to version 0.7.4 or later. Pin the actionlint version in your
+     CI workflow to avoid surprise failures on future schema changes.
+
+  2. **ossf/scorecard-action**: Upgrade to the latest version. The Scorecard API was updated
+     to recognize the timezone key. If you cannot upgrade, temporarily remove the timezone
+     field from your schedule — or use the @latest tag to stay on the most recent release.
+
+  3. **GitHub VS Code extension**: Upgrade to the latest version from the VS Code marketplace.
+     The false-positive schema warning has no runtime effect and does not affect workflow
+     execution.
+
+  If you are blocked from upgrading tools (e.g., in a corporate environment), you can work
+  around the linting error by keeping the cron in UTC and removing the timezone field,
+  adjusting the cron expression offset manually for the desired local time.
+fix_code:
+  - language: yaml
+    label: 'Pin actionlint to v0.7.4+ in CI to support the timezone key'
+    code: |
+      jobs:
+        lint:
+          runs-on: ubuntu-latest
+          steps:
+            - uses: actions/checkout@v4
+
+            # Pin actionlint to v0.7.4+ which supports timezone in on.schedule
+            - name: Lint GitHub Actions workflows
+              uses: rhysd/actionlint@v0.7.4
+              with:
+                shellcheck: 'false'
+
+  - language: yaml
+    label: 'Valid on.schedule with timezone (requires actionlint 0.7.4+ and updated scorecard-action)'
+    code: |
+      on:
+        schedule:
+          # Run at 9 AM Eastern (UTC-5 in winter, UTC-4 in summer)
+          # With timezone support: specify local time directly
+          - cron: '0 9 * * 1-5'
+            timezone: "America/New_York"
+
+      jobs:
+        scheduled-job:
+          runs-on: ubuntu-latest
+          steps:
+            - uses: actions/checkout@v4
+            - run: echo "Running at 9 AM Eastern"
+
+  - language: yaml
+    label: 'Workaround — use UTC offset in cron expression (no timezone key, works with all tool versions)'
+    code: |
+      on:
+        schedule:
+          # 9 AM Eastern Standard Time = 14:00 UTC (winter)
+          # Adjust manually for DST when needed
+          - cron: '0 14 * * 1-5'
+
+      jobs:
+        scheduled-job:
+          runs-on: ubuntu-latest
+          steps:
+            - uses: actions/checkout@v4
+            - run: echo "Running at approximately 9 AM Eastern"
+prevention:
+  - 'When adopting new GitHub Actions syntax features, check that your CI linting tools (actionlint, mega-linter, super-linter) support the new key before adding it to workflows'
+  - 'Pin actionlint to a specific version in CI and bump intentionally — use rhysd/actionlint@v0.7.4 or later for timezone support'
+  - 'The vscode-github-actions extension schema squiggly-underline for "timezone" is cosmetic only — the workflow runs correctly on GitHub regardless'
+  - 'If using ossf/scorecard-action, always pin to a tagged release rather than @main to avoid unexpected parser failures from scorecard API schema changes'
+docs:
+  - url: 'https://github.blog/changelog/2026-03-19-github-actions-late-march-2026-updates/#github-actions-timezone-support-for-scheduled-workflows'
+    label: 'GitHub Changelog: Timezone support for scheduled workflows (March 2026)'
+  - url: 'https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#onschedule'
+    label: 'GitHub Docs: on.schedule syntax including timezone field'
+  - url: 'https://github.com/rhysd/actionlint/issues/638'
+    label: 'actionlint #638 — Add support for timezone for schedule triggers (13 reactions, fixed in 0.7.4)'
+  - url: 'https://github.com/ossf/scorecard-action/issues/1645'
+    label: 'scorecard-action #1645 — Upload fails if schedule:timezone is used in a workflow'
+  - url: 'https://github.com/github/vscode-github-actions/issues/577'
+    label: 'vscode-github-actions #577 — schedule timezone marked as unknown in VS Code extension'

package/package.json

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