Skip to content

build(ci): move both codeql-action steps to 4.37.7, and correct the pin comment - #58

Merged
bgard68 merged 1 commit into
mainfrom
deps/codeql-action-4.37.7
Aug 17, 2026
Merged

build(ci): move both codeql-action steps to 4.37.7, and correct the pin comment#58
bgard68 merged 1 commit into
mainfrom
deps/codeql-action-4.37.7

Conversation

@bgard68

Copy link
Copy Markdown
Owner

Supersedes #47 and #48. Neither can land alone without breaking main.

init and analyze must run the same version of github/codeql-action, or analyze fails with "Loaded a configuration file for version X, but running version Y". Dependabot raises one PR per sub-action — #47 moves analyze, #48 moves init — so whichever merges first leaves main mismatched until the other follows.

Both showed MERGEABLE, which makes this worse, not better: the breakage would have arrived on main rather than being caught on a branch. LotteryApp is the same story (#105), except there the PRs were already visibly failing.

c4dd10eff2f1c6, both steps, one commit.

Also: the pin comment was wrong

Dependabot's diff kept the trailing # v3 while bumping to a 4.x release. Corrected to # v4. The comment is the only human-readable part of a SHA pin — a stale one is exactly what makes the next reviewer distrust an otherwise correct SHA.

🤖 Generated with Claude Code

…in comment
Supersedes #47 and #48. Neither can land alone without breaking main.
init and analyze must run the SAME version of github/codeql-action, or analyze
fails with "Loaded a configuration file for version X, but running version Y".
Dependabot raises one pull request per sub-action, so #47 moves analyze and #48
moves init, and whichever merges first leaves main mismatched until the other
follows. Both showed mergeable, which makes this worse rather than better: the
breakage would have arrived on main, not on a branch. One commit moves both.
c4dd10e -> ff2f1c6, both steps.
Also corrects the trailing comment from "# v3" to "# v4". Dependabot's own diff
kept "# v3" while bumping to a 4.x release. The comment is the only human
readable part of a SHA pin, so a stale one is precisely what makes the next
reviewer distrust an otherwise correct SHA.
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@bgard68