aitbc1
e1113d3c20
Some checks failed
audit / audit (push) Successful in 7s
ci / build (push) Successful in 9s
autofix / fix (push) Successful in 18s
test / test (push) Successful in 2s
ci / deploy (push) Successful in 1s
ci-cd / build (push) Failing after 5s
ci-cd / deploy (push) Has been skipped
security-scanning / audit (push) Successful in 2m2s
CRITICAL: ci.yml was still using old npm commands causing ENOENT errors Issue: ci.yml trying to run npm in wrong directory (hostexecutor) Root cause: ci.yml not updated with nuclear fix pattern Solution: Apply same nuclear fix + Python support to ci.yml Changes: - Apply nuclear fix: rm -rf workspace, git clone, cd repo - Add project type detection (Node.js vs Python) - Add Python environment setup (python3, pipx, poetry) - Add virtual environment creation and activation - Use poetry install --no-root for Python dependencies - Add pytest execution for Python testing - Update deploy job with nuclear fix pattern - Maintain Node.js support for projects with package.json Updated workflows: - ci.yml: Complete nuclear fix + Python + Node.js support - build job: Project detection + dependency installation + testing - deploy job: Nuclear fix pattern + deployment placeholder Expected results: - ci.yml works with both Python and Node.js projects - No more ENOENT errors for package.json - Python dependencies installed via poetry - Tests executed in proper environment - Deploy job has correct repository context This completes the workflow updates to ensure all CI/CD pipelines work correctly with the nuclear fix approach.