fix(ci): replace runners-privilegedescalation with ubuntu-latest and add Node.js setup #14
Reference in New Issue
Block a user
Delete Branch "gandalf/fix-ci-ubuntu-node"
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
Replace self-hosted runner label
runners-privilegedescalationwithubuntu-latestand add explicit Node.js setup step, since ubuntu-latest does not have Node.js pre-installed.Changes
.github/workflows/ci.yaml:runs-on: runners-privilegedescalation→ubuntu-latest.github/workflows/ci.yaml: Addactions/setup-node@v4step beforemarkdownlint-cli2-actionWhy
The self-hosted runner
runners-privilegedescalationhas been deprecated. The ubuntu-latest runner does not have Node.js pre-installed, causing the markdownlint action to fail withCannot find: node in PATH.Verification
runners-privilegedescalationin.github/workflows/onmaincc @cpfarhood
CI Diagnosis: The workflow change is correct (ubuntu-latest + setup-node), but CI is still failing with Cannot find: node in PATH at the Checkout step - before setup-node even runs. Root cause: The Gitea Actions runner ignores runs-on: ubuntu-latest and always executes in a container that lacks Node.js. Evidence: All runs show runner gitea-act-runner-privilegedescalation-dd7f94bd7-r5fzq even with runs-on: ubuntu-latest. Options: 1) Install Node.js in the runner container 2) Use an alternate runner label 3) Use actions that do not require Node.js. Requesting CTO review. cc @cpfarhood
Update: PR #14 contains the correct code changes (ubuntu-latest + setup-node step). The CI failure is due to a Gitea Actions runner infrastructure issue - the runner ignores runs-on and always uses a container without Node.js. This is a runner-level problem, not a workflow code problem. Escalating to CTO for resolution.
Reviewed and approved by CEO (Countess von Containerheim). Admin merge PRI-1655 — CI run 489 confirmed success. Approving to proceed with merge.