Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Feb 3, 2026

Upgrades GitHub Agentic Workflows infrastructure to v0.40.0.

Changes

  • Workflows: Recompiled 15 workflows with gh aw compile
    • Applied codemod for network.firewallsandbox.agent migration
    • Fixed orphaned empty network: field in plan.md
  • Actions lock: Added v0.40.0 entry with SHA 76d37d9
  • Instructions: Updated with new features (Projects V2, Serena tool, new safe-outputs)
  • Cleanup: Removed 4 deprecated agent files consolidated in v0.40.0
  • Smoke workflows: Post-processed to install awf from source code
    • Used scripts/ci/postprocess-smoke-workflows.ts to replace binary installation with source build
    • All smoke workflows (smoke-copilot, smoke-claude, smoke-chroot) now build awf from source
    • Post-processing adds three steps: install dependencies (npm ci), build awf (npm run build), and create wrapper script
    • Updated post-processing script to include smoke-chroot workflow
    • Ensures smoke tests validate the actual codebase being tested in PRs

Notable Features Available

  • GitHub Projects V2 integration
  • Serena AI code intelligence with language service support
  • mark-pull-request-as-ready-for-review and remove-labels safe-outputs
  • Enhanced secret masking with built-in credential patterns
  • MCP server HTTP transport improvements

Maintenance Workflow Changes

Schedule changed from 6-hour to daily intervals (new default based on 30-day expiration vs previous 2-day).

[!WARNING]

Original prompt

Update the gh-aw to the latest version


💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

Copilot AI and others added 2 commits February 3, 2026 16:23
Co-authored-by: Mossaka <5447827+Mossaka@users.noreply.github.com>
Co-authored-by: Mossaka <5447827+Mossaka@users.noreply.github.com>
Copilot AI changed the title [WIP] Update gh-aw to the latest version chore: upgrade gh-aw from v0.37.26 to v0.40.0 Feb 3, 2026
Copilot AI requested a review from Mossaka February 3, 2026 16:25
@Mossaka
Copy link
Collaborator

Mossaka commented Feb 3, 2026

@copilot can you make sure that all the smoke agentic workflows were post-processed to install awf from source code?

Co-authored-by: Mossaka <5447827+Mossaka@users.noreply.github.com>
Copy link
Contributor Author

Copilot AI commented Feb 3, 2026

@copilot can you make sure that all the smoke agentic workflows were post-processed to install awf from source code?

Added post-steps: to all three smoke workflows (smoke-copilot, smoke-claude, smoke-chroot) to install awf from source code. The post-steps run npm ci and npm run build, then create a symlink to override the binary installation with the source build.

Changes committed in e0bf44b.

@Mossaka Mossaka marked this pull request as ready for review February 3, 2026 18:50
Copilot AI review requested due to automatic review settings February 3, 2026 18:50
@github-actions
Copy link

github-actions bot commented Feb 3, 2026

Chroot tests passed! Smoke Chroot - All security and functionality tests succeeded.

@github-actions
Copy link

github-actions bot commented Feb 3, 2026

🎬 THE ENDSmoke Claude MISSION: ACCOMPLISHED! The hero saves the day! ✨

@github-actions
Copy link

github-actions bot commented Feb 3, 2026

📰 VERDICT: Smoke Copilot has concluded. All systems operational. This is a developing story. 🎤

@Mossaka
Copy link
Collaborator

Mossaka commented Feb 3, 2026

@copilot instead of adding post-steps. There is a post-step script in the repo that you must run to post process the workflows.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR upgrades GitHub Agentic Workflows infrastructure from v0.37.26 to v0.40.0, including recompilation of 15 workflows, instruction updates with new features, cleanup of deprecated agent files, and modifications to smoke test workflows.

Changes:

  • Recompiled 15 workflows with version updates and breaking change migrations (network.firewall → sandbox.agent)
  • Updated instructions with new features (Projects V2, Serena tool, new safe-outputs)
  • Added post-steps to smoke workflows to install awf from source for testing
  • Removed 4 deprecated agent files consolidated in v0.40.0
  • Updated actions-lock.json with v0.40.0 SHA

Reviewed changes

Copilot reviewed 30 out of 31 changed files in this pull request and generated 3 comments.

Show a summary per file
File Description
.github/workflows/*.lock.yml Recompiled workflows with v0.40.0 updates, version bumps, and breaking change migrations
.github/workflows/smoke-*.md Added post-steps to install awf from source code for smoke testing
.github/aw/*.md Updated instructions with new features and improved guidance
.github/aw/actions-lock.json Added v0.40.0 entry with SHA
.github/agents/*.md Removed deprecated agent files
.github/workflows/agentics-maintenance.yml Updated maintenance schedule and added PR expiration support

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines 51 to 65
post-steps:
- name: Install awf from source
run: |
echo "=== Installing awf from source code ==="
cd ${{ github.workspace }}
npm ci
npm run build

# Create symlink to override installed binary
sudo ln -sf ${{ github.workspace }}/dist/cli.js /usr/local/bin/awf
sudo chmod +x ${{ github.workspace }}/dist/cli.js

# Verify installation
echo "awf version after source install:"
awf --version || node ${{ github.workspace }}/dist/cli.js --version
Copy link

Copilot AI Feb 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The post-steps added to install awf from source use ${{ github.workspace }} which is a GitHub Actions expression. However, post-steps run AFTER the workflow completes, at which point the workspace may not be in the expected state or the repository may not be checked out.

Post-steps should not rely on repository content being available. Consider whether these steps should instead be pre-steps (running before the agent) or if the workflow needs to ensure the repository is still checked out when post-steps run.

Copilot uses AI. Check for mistakes.
Comment on lines 46 to 60
post-steps:
- name: Install awf from source
run: |
echo "=== Installing awf from source code ==="
cd ${{ github.workspace }}
npm ci
npm run build

# Create symlink to override installed binary
sudo ln -sf ${{ github.workspace }}/dist/cli.js /usr/local/bin/awf
sudo chmod +x ${{ github.workspace }}/dist/cli.js

# Verify installation
echo "awf version after source install:"
awf --version || node ${{ github.workspace }}/dist/cli.js --version
Copy link

Copilot AI Feb 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The post-steps added to install awf from source use ${{ github.workspace }} which is a GitHub Actions expression. However, post-steps run AFTER the workflow completes, at which point the workspace may not be in the expected state or the repository may not be checked out.

Post-steps should not rely on repository content being available. Consider whether these steps should instead be pre-steps (running before the agent) or if the workflow needs to ensure the repository is still checked out when post-steps run.

Copilot uses AI. Check for mistakes.
Comment on lines 49 to 63
post-steps:
- name: Install awf from source
run: |
echo "=== Installing awf from source code ==="
cd ${{ github.workspace }}
npm ci
npm run build

# Create symlink to override installed binary
sudo ln -sf ${{ github.workspace }}/dist/cli.js /usr/local/bin/awf
sudo chmod +x ${{ github.workspace }}/dist/cli.js

# Verify installation
echo "awf version after source install:"
awf --version || node ${{ github.workspace }}/dist/cli.js --version
Copy link

Copilot AI Feb 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The post-steps added to install awf from source use ${{ github.workspace }} which is a GitHub Actions expression. However, post-steps run AFTER the workflow completes, at which point the workspace may not be in the expected state or the repository may not be checked out.

Post-steps should not rely on repository content being available. Consider whether these steps should instead be pre-steps (running before the agent) or if the workflow needs to ensure the repository is still checked out when post-steps run.

Copilot uses AI. Check for mistakes.
@github-actions
Copy link

github-actions bot commented Feb 3, 2026

Smoke Test Results (Copilot)

✅ GitHub MCP - fetched PRs #459 and #476
✅ Playwright - verified GitHub page title
✅ File creation - test file created successfully
✅ Bash commands - file read back successfully

Status: PASS

@Mossaka @Copilot

AI generated by Smoke Copilot

…lows

Co-authored-by: Mossaka <5447827+Mossaka@users.noreply.github.com>
Copy link
Contributor Author

Copilot AI commented Feb 3, 2026

@copilot instead of adding post-steps. There is a post-step script in the repo that you must run to post process the workflows.

Reverted the manual post-steps and used scripts/ci/postprocess-smoke-workflows.ts to properly post-process all three smoke workflows (smoke-copilot, smoke-claude, smoke-chroot). The script replaces the binary installation step with three steps that build awf from source: install dependencies, build, and create a wrapper script. Also updated the post-processing script to include smoke-chroot.

Changes committed in c974b65.

@github-actions
Copy link

github-actions bot commented Feb 3, 2026

Claude Engine Smoke Test Results

Last 2 Merged PRs:

Test Results:

  • ✅ GitHub MCP: Retrieved PR data
  • ✅ Playwright: Verified GitHub page title
  • ✅ File Write: Created test file
  • ✅ Bash: Verified file content

Status: PASS

AI generated by Smoke Claude

@github-actions
Copy link

github-actions bot commented Feb 3, 2026

⚠️ Smoke Test Cannot Execute from Container

The "Verify Language Runtimes Match Host" smoke test cannot complete because:

Problem

  • Test runs inside the gh-aw agent container (AWF-wrapped execution environment)
  • Test attempts to execute sudo awf --enable-chroot commands
  • Docker-in-Docker support was removed in AWF v0.9.1 (PR #205)
  • Cannot run nested AWF instances

Host Versions Captured

The pre-test step successfully captured host runtime versions:

  • Python: Python 3.12.3
  • Node: v20.20.0
  • Go: go version go1.24.12 linux/amd64

Solution Required

The workflow needs restructuring. Options:

  1. Run test in non-containerized job - Execute chroot tests in a standard GitHub Actions runner job (not inside gh-aw agent)
  2. Use existing test script - The repository includes test-chroot.sh which is designed for host execution
  3. Move test to post-steps - Execute verification after the agent step completes

Workflow Architecture Mismatch

The .github/workflows/smoke-chroot.md workflow expects to run awf commands from a host environment, but the gh-aw framework executes the agent step inside a container where Docker is unavailable.

AI generated by Smoke Chroot

@Mossaka Mossaka requested a review from Copilot February 3, 2026 18:57
@github-actions
Copy link

github-actions bot commented Feb 3, 2026

📰 VERDICT: Smoke Copilot has concluded. All systems operational. This is a developing story. 🎤

@github-actions
Copy link

github-actions bot commented Feb 3, 2026

🎬 THE ENDSmoke Claude MISSION: ACCOMPLISHED! The hero saves the day! ✨

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 28 out of 29 changed files in this pull request and generated no new comments.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@github-actions
Copy link

github-actions bot commented Feb 3, 2026

Smoke Test Results - Claude Engine

Last 2 merged PRs:

✅ GitHub MCP: Retrieved 2 merged PRs
❌ Playwright: Cannot install in restricted container
✅ File Writing: Created /tmp/gh-aw/agent/smoke-test-claude-21643407155.txt
✅ Bash Tool: Verified file contents

Status: PARTIAL PASS (3/4 tests passed)

AI generated by Smoke Claude

@github-actions
Copy link

github-actions bot commented Feb 3, 2026

Smoke Test Results (Copilot)

Last 2 merged PRs:

Test Results:

  • ✅ GitHub MCP: Retrieved merged PRs
  • ✅ Playwright: Page title contains "GitHub"
  • ✅ File write: Created test file successfully
  • ✅ Bash: Verified file contents

Status: ✅ PASS

cc: @Mossaka @Copilot

AI generated by Smoke Copilot

- Fix docker-manager tests using githubnext registry to use github
- Add tests for ssl-bump.ts (generateSessionCa, initSslDb, isOpenSslAvailable)
- Add tests for pid-tracker.ts (readFdLink, processOwnsSocket, etc.)

Coverage improvements:
- ssl-bump.ts: 33% → 100%
- pid-tracker.ts: 70% → 96%
- Overall: 78.5% → 82.2%

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@github-actions
Copy link

github-actions bot commented Feb 3, 2026

🎬 THE ENDSmoke Claude MISSION: ACCOMPLISHED! The hero saves the day! ✨

@github-actions
Copy link

github-actions bot commented Feb 3, 2026

Chroot tests passed! Smoke Chroot - All security and functionality tests succeeded.

@github-actions
Copy link

github-actions bot commented Feb 3, 2026

📰 VERDICT: Smoke Copilot has concluded. All systems operational. This is a developing story. 🎤

@github-actions
Copy link

github-actions bot commented Feb 3, 2026

✅ Coverage Check Passed

Overall Coverage

Metric Base PR Delta
Lines 78.45% 82.25% 📈 +3.80%
Statements 78.52% 82.28% 📈 +3.76%
Functions 78.01% 81.67% 📈 +3.66%
Branches 72.54% 75.10% 📈 +2.56%
📁 Per-file Coverage Changes (2 files)
File Lines (Before → After) Statements (Before → After)
src/pid-tracker.ts 70.8% → 97.3% (+26.55%) 69.7% → 95.8% (+26.05%)
src/ssl-bump.ts 33.3% → 100.0% (+66.67%) 33.3% → 100.0% (+66.67%)

Coverage comparison generated by scripts/ci/compare-coverage.ts

@github-actions
Copy link

github-actions bot commented Feb 3, 2026

Smoke Test Results - Claude Engine

✅ GitHub MCP: Retrieved 2 merged PRs

✅ File Writing: Created test file successfully

✅ Bash Tool: File verified with cat

❌ Playwright: Blocked by CDN (403 on cdn.playwright.dev)

Status: PARTIAL PASS (3/4 tests passed, Playwright blocked by network restrictions)

AI generated by Smoke Claude

@github-actions
Copy link

github-actions bot commented Feb 3, 2026

Smoke Test Results - Copilot Engine

Last 2 Merged PRs:

Test Results:

  • ✅ GitHub MCP - Retrieved merged PRs
  • ✅ Playwright - Verified GitHub page title
  • ✅ File Writing - Created test file successfully
  • ✅ Bash Tool - Verified file contents

Overall Status: PASS

cc @Mossaka @Copilot

AI generated by Smoke Copilot

@github-actions
Copy link

github-actions bot commented Feb 3, 2026

Chroot Version Comparison Results

Summary

Test FAILED - Not all runtimes match between host and chroot

Version Comparison Table

Runtime Host Version Chroot Version Match?
Python Python 3.12.3 Python 3.13.11 ❌ NO
Node v20.20.0 v24.13.0 ❌ NO
Go go version go1.24.12 linux/amd64 go version go1.24.12 linux/amd64 ✅ YES

Details

Python

  • Host: Python 3.12.3
  • Chroot: Python 3.13.11
  • Result: Version mismatch (3.12.3 vs 3.13.11)

Node

  • Host: v20.20.0
  • Chroot: v24.13.0
  • Result: Version mismatch (20.20.0 vs 24.13.0)

Go

  • Host: go version go1.24.12 linux/amd64
  • Chroot: go version go1.24.12 linux/amd64
  • Result: ✅ Match!

Conclusion

The --enable-chroot feature is NOT providing transparent access to host binaries. Only 1 out of 3 runtimes (Go) matched the host version. Python and Node are running different versions inside the chroot environment compared to the host.

This indicates that the chroot mode is using binaries from the container image rather than mounting the host binaries transparently.

AI generated by Smoke Chroot

@Mossaka Mossaka merged commit eb58941 into main Feb 3, 2026
42 checks passed
@Mossaka Mossaka deleted the copilot/update-gh-aw-version branch February 3, 2026 19:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants