[aw] EU CRA: has stale lock file #20155

Using the gh-aw MCP server (if configured):

{
  "tool": "compile",
  "arguments": {
    "validate": true
  }
}

Recompile all workflows at once:

gh aw compile --all

Verify the result:

gh aw compile --validate

The workflow run logs contain a verbose debug pass that shows exactly what was hashed. Search the Check workflow lock file step logs for lines starting with [hash-debug] to see:

• The raw frontmatter text that was used as input
• Any imported files that were included in the hash
• The canonical JSON that was fed to SHA-256
• The resulting hash value

This makes it easy to spot accidental whitespace changes, encoding differences, or import path drift.

This mismatch can also happen on a fresh install (even without any manual edits) if gh aw add <path>@<ref> could not resolve the ref to an exact commit SHA during installation. In that case, rerun the add command with an exact SHA (or retry when API/rate-limit conditions recover), then recompile:

gh aw add <path>@<exact-sha>
gh aw compile

[!CAUTION]
Disabling this check means the agent can run against an out-of-date compiled workflow. Only disable it if you have an alternative mechanism to keep lock files in sync.

Set stale-check: false in the on: section of your workflow frontmatter:

on:
  issues:
    types: [opened]
  stale-check: false

After editing, recompile the workflow: gh aw compile

Paste this into your coding agent:

Debug the agentic workflow "eu-cra-compliance" failure.
Follow https://raw.githubusercontent.com/github/gh-aw/main/debug.md
Failed run: https://github.com/githubnext/gh-cao/actions/runs/41643370946

If the repository includes the agentic-workflows skill, load it before investigating.

To stop creating failure issues for this workflow, set this in its frontmatter and recompile:

safe-outputs:
  report-failure-as-issue: false

This only disables issue reporting; it does not fix the failure.