[aw] Dependency Update Node failed

[github-actions]

Workflow Failure

Workflow: Dependency Update Node
Branch: dgee2/fix-dependency-update-workflows
Run: https://github.com/dgee2/Menu/actions/runs/26437589763
Pull Request: #1080

🛡️ Protected Files: The code push was refused because the patch modifies protected files (package manifests, agent instruction files, or repository security configuration). This protection guards against unintended supply chain changes.

Target Pull Request: #1080

Blocked Operations:

• create_pull_request: Cannot create pull request: patch modifies protected files (package.json, pnpm-lock.yaml). Add them to the allowed-files configuration field or set protected-files: fallback-to-issue to create a review issue instead.
• create_pull_request: Cannot create pull request: patch modifies protected files (package.json, pnpm-lock.yaml). Add them to the allowed-files configuration field or set protected-files: fallback-to-issue to create a review issue instead.
• create_pull_request: Cannot create pull request: patch modifies protected files (package.json, pnpm-lock.yaml). Add them to the allowed-files configuration field or set protected-files: fallback-to-issue to create a review issue instead.
• create_pull_request: Cannot create pull request: patch modifies protected files (package.json, pnpm-lock.yaml). Add them to the allowed-files configuration field or set protected-files: fallback-to-issue to create a review issue instead.
• create_pull_request: Cannot create pull request: patch modifies protected files (package.json, pnpm-lock.yaml). Add them to the allowed-files configuration field or set protected-files: fallback-to-issue to create a review issue instead.
• create_pull_request: Cannot create pull request: patch modifies protected files (package.json, pnpm-lock.yaml). Add them to the allowed-files configuration field or set protected-files: fallback-to-issue to create a review issue instead.
• create_pull_request: Cannot create pull request: patch modifies protected files (package.json, pnpm-lock.yaml). Add them to the allowed-files configuration field or set protected-files: fallback-to-issue to create a review issue instead.

⚙️ Configure protected-files: fallback-to-issue

safe-outputs:
  create-pull-request:
    protected-files: fallback-to-issue

Action Required

Assign this issue to an agent to debug and fix the issue.

Debug with any coding agent

Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):

Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md

The failed workflow run is at https://github.com/dgee2/Menu/actions/runs/26437589763

Manually invoke the agent

Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.

• Start your agent
• Load the agentic-workflows prompt from .github/agents/agentic-workflows.agent.md or https://github.com/github/gh-aw/blob/main/.github/agents/agentic-workflows.agent.md
• Type debug the agentic workflow dependency-update-node failure in https://github.com/dgee2/Menu/actions/runs/26437589763

Tip

Stop reporting this workflow as a failure

To stop a workflow from creating failure issues, set report-failure-as-issue: false in its frontmatter:

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

Generated from Dependency Update Node · ● 16.4M · ◷

• expires on Jun 2, 2026, 7:16 AM UTC

[dgee2]

Fixed by adding protected-files override to dependency-update-node.md (commit be5206d on PR #1080). package.json and pnpm-lock.yaml are now excluded from the protected-files check so the workflow can create PRs normally.