FINAL FIX: Complete nuclear fix pattern for all workflows
Issue: ci-cd.yml and cli-level1-tests.yml still using old working-directory pattern
Root cause: These workflows weren't updated with nuclear fix approach
Solution: Apply complete nuclear fix + Python support to remaining workflows
Changes:
- ci-cd.yml: Complete nuclear fix + project type detection
- cli-level1-tests.yml: Nuclear fix + matrix testing + project detection
- Both workflows now support Python + Node.js projects
- Added full Python environment setup (poetry, venv, etc.)
- Removed working-directory pattern in favor of nuclear fix
- Added proper project detection and dependency management
Updated workflows:
- ci-cd.yml: Build + deploy jobs with nuclear fix
- cli-level1-tests.yml: Matrix testing with nuclear fix
Expected results:
- All workflows now use consistent nuclear fix pattern
- No more ENOENT errors for package.json
- Python projects fully supported with poetry
- Node.js projects maintained for compatibility
- Complete CI/CD pipeline functional
This completes the workflow updates to ensure ALL workflows
use the nuclear fix pattern and support both Python and Node.js projects.
CRITICAL FIX: Resolve act_runner host mode working directory issue
Problem:
- act_runner host mode does not persist working directory between steps
- Each 'cd repo' command was being lost due to isolated step execution
- npm install was still running in hostexecutor directory instead of repo
Solution:
- Add 'working-directory: repo' to every step after clone
- Enforce working directory at step level instead of inside run commands
- This bypasses act_runner host mode quirks completely
Changes:
- Update all 7 workflows to use working-directory: repo
- Remove 'cd repo' from run commands (redundant with working-directory)
- Keep git clone step outside working-directory (needs to run in default dir)
- Add verification steps to confirm correct working directory
Workflows updated:
- ci.yml, audit.yml, fix.yml, test.yml, security-scanning.yml
- cli-level1-tests.yml, ci-cd.yml
This should finally resolve the ENOENT: no such file or directory
errors for package.json by ensuring all npm commands execute in the
correct repository directory.
BREAKING CHANGE: Replace GitHub Actions checkout with explicit git clone
- Remove unreliable actions/checkout@v4 from all workflows
- Add manual git clone with HTTPS URL for deterministic behavior
- Explicit working directory control with 'cd repo' in each step
- Add debug verification steps to confirm repository context
- Fix npm install failures by ensuring correct working directory
- Update all 7 workflows: ci.yml, audit.yml, fix.yml, test.yml, security-scanning.yml, cli-level1-tests.yml, ci-cd.yml
- Use HTTPS clone URL for compatibility with Gitea runners
- Add 'rm -rf repo' to ensure clean clone each run
This resolves the issue where workflows were executing in hostexecutor directory
instead of repository workspace, causing npm install failures.
- Added actions/checkout@v4 step to cli-level1-tests.yml test and test-summary jobs
- Added actions/checkout@v4 and repository verification steps to test.yml
- Verification includes pwd, ls -la, and package.json check
- Ensures repository context is available before workflow execution
- Updated cli-level1-tests.yml test-summary job runs-on from ubuntu-latest to debian
- Aligns with repository-wide standardization to debian runner label
- Completes migration of all workflow jobs to consistent runner configuration
- Updated runs-on from gitea-runner to debian across all workflow files
- Changed audit.yml, ci-cd.yml, ci.yml, fix.yml, security-scanning.yml, and test.yml
- Updated cli-level1-tests.yml from gitea-runner to debian
- Fixed audit.yml workflow name from 'gitea-runnername' to 'debianname'
- Standardizes runner configuration to use debian label
- Updated runs-on from debian:host to gitea-runner across all workflow files
- Changed audit.yml, ci-cd.yml, ci.yml, fix.yml, security-scanning.yml, and test.yml
- Updated cli-level1-tests.yml from debian:host to gitea-runner
- Fixed audit.yml workflow name from 'name' to 'gitea-runnername'
- Standardizes runner configuration to use gitea-runner label
- Updated runs-on from incus-debian to debian:host across all workflow files
- Changed audit.yml, ci-cd.yml, ci.yml, fix.yml, security-scanning.yml, and test.yml
- Updated cli-level1-tests.yml from ubuntu-latest to debian:host
- Standardizes runner configuration across all CI/CD pipelines
