Skip to content

fix: recompile lock files with release action mode#527

Merged
Mossaka merged 1 commit intomainfrom
fix/recompile-release-mode
Feb 5, 2026
Merged

fix: recompile lock files with release action mode#527
Mossaka merged 1 commit intomainfrom
fix/recompile-release-mode

Conversation

@Mossaka
Copy link
Collaborator

@Mossaka Mossaka commented Feb 5, 2026

Summary

  • Recompile all 23 lock files with --action-mode release --action-tag v0.42.0
  • Fixes the ./actions/setupgithub/gh-aw/actions/setup@SHA reference

Problem

PR #526 was compiled in dev mode, which uses ./actions/setup (local path) instead of github/gh-aw/actions/setup@a7134347... (pinned remote action). Since the actions/setup directory doesn't exist in this repo, all activation jobs fail with:

Can't find 'action.yml' under 'actions/setup'

Test plan

  • Activation jobs pass (no more ./actions/setup errors)
  • Smoke Claude passes
  • Smoke Copilot passes

🤖 Generated with Claude Code

PR #526 accidentally compiled with dev action mode (`./actions/setup`)
instead of release mode (`github/gh-aw/actions/setup@SHA`). This
causes activation jobs to fail because the local actions/setup
directory doesn't exist in the firewall repo.

Recompile with --action-mode release --action-tag v0.42.0.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings February 5, 2026 20:43
@github-actions
Copy link
Contributor

github-actions bot commented Feb 5, 2026

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

@github-actions
Copy link
Contributor

github-actions bot commented Feb 5, 2026

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

@github-actions
Copy link
Contributor

github-actions bot commented Feb 5, 2026

✅ Coverage Check Passed

Overall Coverage

Metric Base PR Delta
Lines 82.10% 82.10% ➡️ +0.00%
Statements 82.14% 82.14% ➡️ +0.00%
Functions 81.95% 81.95% ➡️ +0.00%
Branches 75.44% 75.44% ➡️ +0.00%

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

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 recompiles all 23 workflow lock files to use release action mode with v0.42.0, fixing a critical issue from PR #526 where lock files were compiled in dev mode. The dev mode compilation used a local path reference ./actions/setup which doesn't exist in this repository, causing all activation jobs to fail with "Can't find 'action.yml' under 'actions/setup'" errors.

Changes:

  • Replace all local action references (./actions/setup) with pinned remote action references (github/gh-aw/actions/setup@a7134347103ecf66b4bd422c3e9ce6466d400c02)
  • Remove redundant "Checkout actions folder" steps that are no longer needed
  • Update repository checkout steps to use sparse checkout for only .github and .agents folders

Reviewed changes

Copilot reviewed 23 out of 23 changed files in this pull request and generated no comments.

Show a summary per file
File Description
update-release-notes.lock.yml Updated action references and checkout configuration
test-coverage-improver.lock.yml Updated action references and checkout configuration
smoke-copilot.lock.yml Updated action references, checkout configuration, and permissions
smoke-claude.lock.yml Updated action references, checkout configuration, and permissions
smoke-chroot.lock.yml Updated action references and checkout configuration
security-review.lock.yml Updated action references, checkout configuration, and permissions
security-guard.lock.yml Updated action references and checkout configuration
plan.lock.yml Updated action references, checkout configuration, permissions, and removed GH_AW_IS_PR_COMMENT logic
pelis-agent-factory-advisor.lock.yml Updated action references, checkout configuration, and permissions
issue-monster.lock.yml Updated action references, checkout configuration, and permissions
issue-duplication-detector.lock.yml Updated action references, checkout configuration, and permissions
doc-maintainer.lock.yml Updated action references, checkout configuration, and permissions
dependency-security-monitor.lock.yml Updated action references and checkout configuration
cli-flag-consistency-checker.lock.yml Updated action references and checkout configuration
ci-doctor.lock.yml Updated action references, checkout configuration, and permissions
ci-cd-gaps-assessment.lock.yml Updated action references and checkout configuration
build-test-rust.lock.yml Updated action references and checkout configuration
build-test-node.lock.yml Updated action references and checkout configuration
build-test-java.lock.yml Updated action references and checkout configuration
build-test-go.lock.yml Updated action references and checkout configuration
build-test-deno.lock.yml Updated action references and checkout configuration
build-test-cpp.lock.yml Updated action references and checkout configuration
build-test-bun.lock.yml Updated action references and checkout configuration

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

@github-actions
Copy link
Contributor

github-actions bot commented Feb 5, 2026

Smoke test results for run #21727792741:

Status: PASS 🎉

cc @Mossaka

AI generated by Smoke Copilot

@github-actions
Copy link
Contributor

github-actions bot commented Feb 5, 2026

C++ Build Test Results

Project CMake Build Status
fmt PASS
json PASS

Overall: PASS

All C++ projects built successfully.

AI generated by Build Test C++

@github-actions
Copy link
Contributor

github-actions bot commented Feb 5, 2026

Build Test: Deno - PASS ✅

All Deno tests passed successfully.

Project Tests Status
oak 1/1 ✅ PASS
std 1/1 ✅ PASS

Overall: PASS

AI generated by Build Test Deno

@github-actions
Copy link
Contributor

github-actions bot commented Feb 5, 2026

Go Build Test Results

Project Download Tests Status
color 1/1 PASS
env 1/1 PASS
uuid 1/1 PASS

Overall: PASS

All Go projects successfully downloaded dependencies and passed tests.

AI generated by Build Test Go

@github-actions
Copy link
Contributor

github-actions bot commented Feb 5, 2026

Build Test: Node.js - Results

Project Install Tests Status
clsx PASS PASS
execa PASS PASS
p-limit PASS PASS

Overall: PASS

All Node.js projects built and tested successfully.

AI generated by Build Test Node.js

@github-actions
Copy link
Contributor

github-actions bot commented Feb 5, 2026

Build Test: Bun - FAILED ❌

Test Results

Project Install Tests Status
elysia ⚠️ N/A (no deps) ❌ 0/0 FAIL
hono ⚠️ N/A (no deps) ❌ 0/0 FAIL

Overall: FAIL

Error Details

Both projects failed with the same error when running bun test:

bun test v1.3.8 (b64edcb4)
Aborted (core dumped)
Exit code: 134

Root cause: Bun test runner crashed with a segmentation fault (core dump) in the container environment. This appears to be a compatibility issue between Bun v1.3.8 and the container runtime.

Environment

  • Bun version: 1.3.8
  • OS: Linux (container)
  • Both projects have minimal test files (simple arithmetic assertions using bun:test)

Next Steps

This failure indicates that Bun's test runner is not compatible with the current container environment. Possible solutions:

  1. Try a different Bun version
  2. Investigate container runtime configuration
  3. Check for missing system dependencies required by Bun's test runner

AI generated by Build Test Bun

@Mossaka Mossaka merged commit 995a2ea into main Feb 5, 2026
76 of 79 checks passed
@Mossaka Mossaka deleted the fix/recompile-release-mode branch February 5, 2026 20:50
Mossaka added a commit that referenced this pull request Feb 6, 2026
Reverts the following PRs which introduced unnecessary complexity:

- #520: fix: enable Squid intercept mode for NAT-redirected traffic
- v0.13.5 release: chore(release): bump version to 0.13.5
- #524: fix: remove HTTP_PROXY/HTTPS_PROXY env vars from agent container
- #526: chore: recompile workflow lock files for AWF v0.13.5
- #527: fix: recompile lock files with release action mode
- #522: fix: mount /etc/hosts in chroot and fix HTTP blocking test
- #530: fix: restore HTTPS_PROXY, fix chroot hosts/permissions, fix Bun crash
- v0.13.6 release: chore(release): bump version to 0.13.6

The intercept mode (#520) was introduced to fix Codex failing with
HTTP_PROXY, but the simpler fix is to just not set HTTP_PROXY for
Codex. The intercept mode introduced a cascade of breakage:
- HTTPS can't be transparently intercepted (needs CONNECT method)
- Image version bumps required lock file recompilation
- host.docker.internal traffic crashed Squid under load
- Multiple PRs needed to fix each regression

This reverts to the pre-#520 explicit proxy mode (HTTP_PROXY/HTTPS_PROXY
pointing to Squid port 3128) which worked for all engines.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Mossaka added a commit that referenced this pull request Feb 6, 2026
Reverts the following PRs which introduced unnecessary complexity:

- #520: fix: enable Squid intercept mode for NAT-redirected traffic
- v0.13.5 release: chore(release): bump version to 0.13.5
- #524: fix: remove HTTP_PROXY/HTTPS_PROXY env vars from agent container
- #526: chore: recompile workflow lock files for AWF v0.13.5
- #527: fix: recompile lock files with release action mode
- #522: fix: mount /etc/hosts in chroot and fix HTTP blocking test
- #530: fix: restore HTTPS_PROXY, fix chroot hosts/permissions, fix Bun crash
- v0.13.6 release: chore(release): bump version to 0.13.6

The intercept mode (#520) was introduced to fix Codex failing with
HTTP_PROXY, but the simpler fix is to just not set HTTP_PROXY for
Codex. The intercept mode introduced a cascade of breakage:
- HTTPS can't be transparently intercepted (needs CONNECT method)
- Image version bumps required lock file recompilation
- host.docker.internal traffic crashed Squid under load
- Multiple PRs needed to fix each regression

This reverts to the pre-#520 explicit proxy mode (HTTP_PROXY/HTTPS_PROXY
pointing to Squid port 3128) which worked for all engines.

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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.

1 participant