ci: regenerate lockfile after dependabot #163 (restores CodeQL + Governance) - #164
Conversation
Third occurrence of DEBT I-1 in one day. #163 bumped four workflows' action SHAs (cflite_batch, cflite_pr, codeql, push-email-notify) without regenerating actions.lock, so 4 of 15 went stale: CodeQL back to startup_failure and Governance red on its own --verify-local step. Regenerated with the full four-step recipe. --verify-local: all 15 covered; --no-fix: valid, zero errors. Note: actions/checkout@3d3c42e now records a bare SHA as its ref because the same commit carries CONFLICTING tag comments in the tree — '# v5' in cflite_batch.yml/cflite_pr.yml vs '# v7.0.1' in codeql.yml — so the generator cannot narrow it. Pre-existing mislabelling; enforcement checks the digest, not the ref, so this is cosmetic. Worth correcting separately. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Note Automatic reviews are paused because your trial's included automatic processing has been used for this period. Upgrade now, or comment "Gitar review" to run a review anytime. Code Review ✅ ApprovedRegenerates the action lockfile following Dependabot PR #163 to restore CodeQL and Governance checks. No issues found.
OptionsDisplay: compact → Showing less information. Comment with these commands to change the behavior for this request:
Important Your trial ends in 3 days — upgrade now to keep code review, CI analysis, auto-apply, custom automations, and more. Was this helpful? React with 👍 / 👎 | Gitar |
Third occurrence of DEBT I-1 today. Dependabot #163 bumped four workflows' action SHAs without regenerating
actions.lock, so 4 of 15 went stale — CodeQL back to 0-secondstartup_failure, Governance red on its owngh actions-lock --verify-localstep.Regenerated with the full four-step recipe (regenerate → restore inline SHA pins →
relock-sha-keys.sh→ restore reusable-caller entries).--verify-local: all 15 covered.--no-fix: valid, zero errors.This is now demonstrably unsustainable by hand
Three times in one day (#155/#157, then #163). Every dependabot action bump re-breaks the board, and the fix is not a single command — step 4 has no upstream equivalent, because
gh actions-lockdrops reusable-workflow callers. I-1 needs automating, not repeating.Incidental finding
actions/checkout@3d3c42enow records a bare SHA as itsref:because the same commit carries conflicting tag comments in the tree —# v5incflite_batch.yml/cflite_pr.ymlversus# v7.0.1incodeql.yml— so the generator cannot narrow it. Pre-existing mislabelling; enforcement checks the digest rather than the ref, so this is cosmetic, but one of those comments is wrong and should be corrected.Separately: Secret Scanner is red for an unrelated upstream reason
Not fixed here — see the standards-side issue.
gitleaksfails with:The secret-scanner reusable sparse-checks-out standards' own
.gitleaks.tomland copies it into consumers as the estate baseline — but that file[extend]sconfig/gitleaks/estate-baseline.toml, a CWD-relative path that exists only inside standards. It should copy the baseline file itself. This breaks every consumer without its own.gitleaks.toml.🤖 Generated with Claude Code