Skip to content

ci: move every codeql-action pin to v4.37.6 in one step - #52

Merged
AndresSaa merged 1 commit into
mainfrom
ci/move-codeql-action-pins-together
Aug 8, 2026
Merged

ci: move every codeql-action pin to v4.37.6 in one step#52
AndresSaa merged 1 commit into
mainfrom
ci/move-codeql-action-pins-together

Conversation

@AndresSaa

Copy link
Copy Markdown
Owner

Replaces #49, #50 and #51.

Why those three could not just be merged

Dependabot opened one pull request per action path for what is a single upgrade — all three resolve to the same commit. Two of them are red by construction:

##[error]Loaded a configuration file for version '4.37.4', but running version '4.37.6'

codeql.yml runs both github/codeql-action/init and github/codeql-action/analyze, and the action refuses to run when the two halves disagree. #51 bumps init and leaves analyze behind; #50 does the reverse. Neither can go green alone, and no amount of re-running changes that.

Merging them one after the other would also leave main carrying a broken CodeQL job in the window between the two merges.

#49 (upload-sarif, in scorecard.yml) was green only because it is the sole codeql-action step in its file.

What this does

Moves all three pins to 5595ccaf912efad79be6eef63a5619ff05969be3 in one commit — two lines in codeql.yml, one in scorecard.yml.

Verifying the pin

A comment saying # v4.37.6 proves nothing on its own, so the SHA was checked against the upstream tag:

$ gh api repos/github/codeql-action/git/ref/tags/v4.37.6
tag v4.37.6 -> 9e3211c9a3b9311dfe05da2ed48eea3386f042dd (tag)

$ gh api repos/github/codeql-action/commits/v4.37.6
resolved commit: 5595ccaf912efad79be6eef63a5619ff05969be3
date: 2026-08-04T13:33:02Z

The annotated tag dereferences to exactly the SHA pinned here.

grep -rn "f205ea1c…\|v4.37.4" .github/   → no matches (nothing left behind)
npm run lint                            → clean

The real proof is this pull request's own Analyze check: it runs init and analyze at the new version together, which is the exact combination the split pull requests could not produce.

Contract impact

None. CI configuration only.

Preventing the recurrence — grouping the github-actions ecosystem, which currently has no groups block at all — is deliberately a separate pull request: this one fixes the instance, that one fixes the cause.

Dependabot split this single upgrade into three pull requests, one per action
path, and two of them cannot pass on their own: `codeql.yml` runs both `init`
and `analyze`, and the action refuses a mismatch —

    Loaded a configuration file for version '4.37.4', but running version '4.37.6'

so each of those pull requests bumps one half and is red by construction.
Merging them in sequence would leave main with a broken CodeQL job between the
two merges.

All three paths ship from the same commit, so they move as one here. The pin
was verified rather than trusted: the annotated tag v4.37.6 dereferences to
5595ccaf912efad79be6eef63a5619ff05969be3, which is the SHA used below.

Closes the three split pull requests. The grouping that stops this recurring is
a separate change, since it fixes the cause rather than this instance.
Sign up for free to 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