Skip to content

chore(ci): CodeQL pin comment v3.28.1 -> v3 (SHA unchanged) - #86

Merged
hyperpolymath merged 2 commits into
mainfrom
fix/codeql-pin-comment
Jul 27, 2026
Merged

chore(ci): CodeQL pin comment v3.28.1 -> v3 (SHA unchanged)#86
hyperpolymath merged 2 commits into
mainfrom
fix/codeql-pin-comment

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Pushes a commit that was stranded on a local checkout (5b3f68b).

What this actually changes

Nothing functional. Despite the original commit message ("update CodeQL
actions to SHA-pinned v3 (29b1f65c)"), the diff leaves the pinned SHA
unchanged at 7188fc363630916deb702c7fdcf4e481b751f97a for both
codeql-action/init and codeql-action/analyze.

The only change is the trailing comment:

-  uses: github/codeql-action/init@7188fc36...  # v3.28.1
+  uses: github/codeql-action/init@7188fc36...  # v3

The SHA 29b1f65c referenced in the commit message does not appear in the diff.

Reviewer decision needed

This arguably makes the pin less informative — # v3.28.1 names the exact
release, # v3 does not. Options:

  1. Close this and drop the commit (CodeQL is currently green on main).
  2. Merge as-is for comment consistency with the rest of the estate.
  3. Amend it to genuinely re-pin onto the intended 29b1f65c, if that is the
    current codeql-action v3 SHA — this needs confirming, not guessing.

Opened as a draft because of the above. Raised during the BetLang sitrep;
see dev-notes/betlang-sitrep-2026-07-27.md.

🤖 Generated with Claude Code

@hyperpolymath
hyperpolymath marked this pull request as ready for review July 27, 2026 13:31
Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com>
@hyperpolymath
hyperpolymath merged commit 29abb4c into main Jul 27, 2026
30 checks passed
@hyperpolymath
hyperpolymath deleted the fix/codeql-pin-comment branch July 27, 2026 13:34
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