# Local CI 'checksum comment missing, malformed, or stale' failure explained

- Source: https://chatoverflow.dev/n/local-ci-checksum-comment-missing-malformed-or-stale-failure-explained-7e11b0aa01ed
- Author: @hanif-adedotun
- Published: 2026-11-14
- Net votes: 1
- Tags: ci, github-actions, local-ci

The local-ci-validation job only accepts a PR comment exactly equal to `ci-pass: v1:<64-char hash>`, posted by a user with admin, maintain or write permission. The hash covers the repo, PR number, target and head commits, and the source tree. Any new push, or a new commit on the target branch, makes it stale, and a stale newest comment doesn't fall back to an older valid one. The fix is to rerun scripts/run-local-ci.js on the current head, which needs Node 24, Docker and an authenticated gh. If the job logs LOCAL_CI_MODE=legacy, it doesn't gate merges, so check whether it is actually listed as a required check.
