-
Notifications
You must be signed in to change notification settings - Fork 43
Update AWF to v0.13.0 and enable --enable-chroot #12827
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
… flag Co-authored-by: Mossaka <5447827+Mossaka@users.noreply.github.com>
🔍 PR Triage ResultsCategory: chore | Risk: medium | Priority: 45/100 Scores Breakdown
📋 Recommended Action: batch_reviewThis PR is part of Batch #4: Chore Updates (batch-chore-001) along with PR #12815. Review together for configuration consistency. Batch Review Strategy: Verify compatibility and test for regressions. Next Steps:
Triaged by PR Triage Agent on 2026-01-31 | Run #21540069309
|
🔍 PR Triage ResultsCategory: chore | Risk: high | Priority: 55/100 Scores Breakdown
📋 Recommended Action: Batch ReviewThis PR is recommended for batch review with similar PRs. Triaged by PR Triage Agent on 2026-01-31 12:17 UTC
|
🔍 PR Triage ResultsCategory: chore | Risk: high | Priority: 37/100 Scores Breakdown
📋 Recommended Action: batch_reviewBatch: batch-chore-001 (with PR #12574) This PR should be reviewed together with #12574 to assess combined infrastructure impact. Both PRs modify workflow generation and execution patterns. Blockers:
Strengths:
Review Notes:
Triaged by PR Triage Agent on 2026-01-31T18:14:11Z
|
🔍 PR Triage ResultsCategory: chore | Risk: high | Priority: 40/100 Scores Breakdown
📋 Recommended Action: batch_reviewWhy: High-risk infrastructure change needing careful review. Part of batch-chore-001 for coordinated infrastructure updates. Batch: batch-chore-001 (Infrastructure Updates) Next steps:
Triaged by PR Triage Agent on 2026-02-01
|
🔍 PR Triage ResultsCategory: chore | Risk: high | Priority: 43/100 Scores Breakdown
📋 Recommended Action: Fast-trackThis PR updates critical security infrastructure (AWF to v0.13.0) and enables chroot for transparent host binary execution. High-risk change requiring careful review. Next Steps:
Merge Conflict Status: Batch Info: Part of Triaged by PR Triage Agent on 2026-02-01
|
🔍 PR Triage ResultsCategory: chore | Risk: high | Priority: 62/100 Scores Breakdown
📋 Recommended Action: fast_trackThis PR requires priority review. The AWF version update to v0.13.0 with chroot enablement is a significant security enhancement that should be expedited once CI passes. Next steps:
Triaged by PR Triage Agent on 2026-02-01 - Run #21567753665
|
Updates the AWF (agentic-workflow-firewall) from v0.11.2 to v0.13.0 and enables the new
--enable-chrootflag for transparent host binary execution in the chroot environment.Changes
DefaultFirewallVersion→v0.13.0--enable-chrootflag to AWF invocations in all engines (copilot, claude, codex)--enable-chrootis included in AWF commandsWhat
--enable-chrootdoesEnables chroot to
/hostfor running host binaries (Python, Node, Go, etc.) inside the container using selective path mounts. Docker socket is hidden to prevent firewall bypass.Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.