refactor: host-based CI jobs with node-based actions #3
Loading…
Reference in a new issue
No description provided.
Delete branch "ci/gh-compatible"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Switches CI and release workflows from container-based jobs (shell-only actions) to host-based jobs using actions/checkout@v4 and actions/setup-python@v5.
Probe results (PR #2) verified: the runner host provides node, so node-based actions work without container blocks; setup-python provisions each matrix Python version independently of the host image. actions/cache@v4 remains unavailable on this Forgejo instance (no cache service), so dependency caching stays on scripts/ci-cache.sh (paths moved to $HOME-based locations).
Requires the ubuntu-latest runner label to point to an image with node (gitea/runner-images or catthehacker/ubuntu:act-latest, or a self-built equivalent) - tracked separately as a runner config change.
Pull request closed