fix(ci): run CI/drift jobs on Debian glibc image so JS actions get a working node #27
No reviewers
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea!27
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "refs/pull/27/head"
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?
Summary
The Forgejo Actions runner injects a glibc node24 into the job container to run JS actions (checkout, cache, hashFiles). On the golang:1.26-alpine (musl) image that node cannot exec and every job dies with
node: not found(exit 127) before any step runs.Switch all CI jobs (.forgejo/workflows/ci.yml) and the drift job (.forgejo/workflows/drift.yml) to golang:1.26-trixie (Debian/glibc, pinned to digest). trixie also ships gcc (needed by go test -race), bash, python3, and git, so the per-job apk-add steps collapse to a single apt-get install jq (hook-tests) / nodejs npm (mcp-conformance).