Firewall Issue Dispatcher

Durable reports produced by .github/workflows/firewall-issue-dispatcher.md in github/gh-aw-firewall.

standalone

.github/workflows/firewall-issue-dispatcher.md

View authored workflow

Reports

0 Open 3 Resolved

[aw] Firewall Issue Dispatcher has stale lock file

Workflow Failure Workflow: Firewall Issue Dispatcher Branch: main Run: https://github.com/github/gh-aw-firewall/actions/runs/32608081965 [!WARNING] Lock File Out of Sync: The workflow could not start because its compiled lock file no longer matches the source markdown. This means the workflow's .md file was edited but gh aw compile was not run afterwards to regenerate the corresponding .lock.yml file. The agent is prevented from running against a stale configuration to avoid unexpected behaviour. To fix, recompile the workflow: Then commit and push the updated .lock.yml file. <details> <summary>More ways to recompile</summary> Using the gh-aw MCP server (if configured): Recompile all work...

closed live issue

Comment on [aw] Firewall Issue Dispatcher has stale lock file

Agent job 32639561411 failed. [!WARNING] Lock File Out of Sync: The workflow could not start because its compiled lock file no longer matches the source markdown. This means the workflow's .md file was edited but gh aw compile was not run afterwards to regenerate the corresponding .lock.yml file. The agent is prevented from running against a stale configuration to avoid unexpected behaviour. To fix, recompile the workflow: Then commit and push the updated .lock.yml file. <details> <summary>More ways to recompile</summary> Using the gh-aw MCP server (if configured): Recompile all workflows at once: Verify the result: </details> <details> <summary>How to investigate the mismatch</summary> T...

closed live comment

[awf] security: gh-aw-node image contains vulnerable packages (OpenSSL, musl)

Problem A final-image scan of artifacts selected by gh-aw v0.82.14 found vulnerable packages in the gh-aw-owned gh-aw-node image (ghcr.io/github/gh-aw-node@sha256:529d02eb...). Key findings: libcrypto3/libssl3 3.5.6-r0 (fix: 3.5.7+) and musl 1.2.6-r2 (fix pending). Additionally, gh-aw-mcpg v0.4.3 remains affected — updating from v0.4.1 to v0.4.3 did not resolve MCP gateway findings. Context Original report: https://github.com/github/gh-aw/issues/47396 Root Cause The gh-aw-node base image (Alpine-based) is pinned to a digest that includes outdated versions of OpenSSL and musl. Release cadence does not automatically pull updated Alpine packages. Proposed Solution In the gh-aw-node Dockerfil...

closed review issue