Files
aitbc/.gitea
aitbc1 e03e4edeaa
Some checks failed
audit / audit (push) Failing after 2s
ci-cd / build (push) Failing after 4s
ci / build (push) Failing after 4s
autofix / fix (push) Failing after 1s
security-scanning / audit (push) Failing after 2s
test / test (push) Successful in 2s
ci-cd / deploy (push) Has been skipped
fix: install Python and pip in workflows for proper environment
PROGRESS: Nuclear fix working perfectly! Python project detected correctly.

Issue: 'pip: command not found' - Python environment not properly set up
Root cause: Runner missing Python3 and pip installation

Solution:
- Add Python environment setup to all workflows
- Install python3, python3-pip, python3-venv if not available
- Upgrade pip to latest version
- Verify Python and pip versions before proceeding
- Maintain same nuclear fix approach for workspace control

Updated workflows:
- audit.yml: Python setup + poetry install + audit
- fix.yml: Python setup + poetry install + safety fixes
- security-scanning.yml: Python setup + poetry install + security scans

Expected results:
- Python 3 installed and available
- pip upgraded and working
- Poetry installed for dependency management
- Security scanning tools (safety, bandit) installed
- All workflows should complete successfully

This should resolve the 'command not found' errors and enable
proper Python dependency management and security scanning.
2026-03-27 12:55:48 +01:00
..