aitbc1 c51d0d4d80 fix: implement aggressive nuclear fix with absolute paths ...

CRITICAL: Complete bypass of act_runner workspace handling

Issue:
- Runner still executing in hostexecutor despite workdir config
- npm install failing with ENOENT for package.json
- act_runner cache not cleared properly

Aggressive Nuclear Fix:
- Clear runner cache completely: rm -rf /opt/gitea-runner/.cache
- Force absolute workspace path: /opt/gitea-runner/workspace
- Complete workspace recreation each run
- Extensive debugging and verification
- Exit with error if package.json not found

Updated workflows:
- test.yml: Comprehensive nuclear fix with full debugging
- audit.yml: Nuclear fix for dependency auditing
- fix.yml: Nuclear fix for vulnerability fixing

This should finally bypass all act_runner host mode issues
by forcing absolute paths and complete workspace control.

2026-03-27 12:45:09 +01:00

..

audit.yml

fix: implement aggressive nuclear fix with absolute paths

2026-03-27 12:45:09 +01:00

ci-cd.yml

fix: enforce working-directory for act_runner host mode compatibility

2026-03-27 12:24:14 +01:00

ci.yml

fix: enforce working-directory for act_runner host mode compatibility

2026-03-27 12:24:14 +01:00

cli-level1-tests.yml

fix: enforce working-directory for act_runner host mode compatibility

2026-03-27 12:24:14 +01:00

fix.yml

fix: implement aggressive nuclear fix with absolute paths

2026-03-27 12:45:09 +01:00

security-scanning.yml

fix: enforce working-directory for act_runner host mode compatibility

2026-03-27 12:24:14 +01:00

test.yml

fix: implement aggressive nuclear fix with absolute paths

2026-03-27 12:45:09 +01:00