fix(ci): run CI/drift jobs on Debian glibc image so JS actions get a working node #27

Merged
hexajon merged 1 commit from refs/pull/27/head into main 2026-07-12 23:27:00 +00:00
hexajon commented 2026-07-12 23:26:56 +00:00 (Migrated from codeberg.org)

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).

## 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).
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
sixfold-space/madtea!27
No description provided.