Fix Gitea Actions: drop custom job container, use setup-python
CI / lint:ruff (push) Successful in 1m49s
CI / format:ruff (push) Successful in 7s
CI / typecheck:ty (push) Successful in 10s
CI / vulnerabilities:pip-audit (push) Failing after 9s
CI / test:pytest (push) Has been skipped

The python:3.11-slim job container lacked a Node.js runtime, so the
runner couldn't exec actions/checkout inside it. Run jobs on the
default runner image instead and pin Python via actions/setup-python.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
2026-07-23 13:13:17 +02:00
parent ea5ec680c5
commit f7294909a2
3 changed files with 23 additions and 28 deletions
+2 -2
View File
@@ -58,5 +58,5 @@ usable there at all, fall back to a crontab entry instead:
where you control a dedicated VM/server and need to serve the output yourself.
On the ETP login nodes there's no Docker daemon (Apptainer/Singularity only),
and `public_html` is already auto-served — running your own nginx there would
be redundant. Docker is still used for CI (`.gitea/workflows/ci.yml`) and
remains a fine option for anyone deploying this on their own server.
be redundant. It remains a fine option for anyone deploying this on their own
server.