build(deps): move every codeql-action to 4.37.7 in one commit (frontend) - #122
Merged
Merged
Conversation
Frontend-branch counterpart of the same fix on main and dapper. Supersedes #96, #99 and #101, which cannot pass individually. codeql-action requires init, analyze and upload-sarif to run the same version; mixing them fails with "Loaded a configuration file for version X, but running version Y". Dependabot opens one pull request per sub-action, and this branch has all three open at once - #96 moves init, #101 moves analyze, #99 moves upload-sarif - so it is a three-way split that cannot converge no matter which order they land in. #96 is red with exactly that error today. The branch itself is fine: all three pins are currently 4.37.4 and consistent, so nothing is broken until one of them moves alone. init f205ea1c -> ff2f1c62 analyze f205ea1c -> ff2f1c62 upload-sarif f205ea1c -> ff2f1c62 This does not unblock the frontend pull requests on its own. They are also held by `npm audit --audit-level=high` in deploy.yml failing on a real advisory in nanoid, which is addressed separately. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
bgard68
force-pushed
the
deps/codeql-action-4.37.7-frontend
branch
from
August 17, 2026 13:29
791bc13 to
e9645cb
Compare
Contributor
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://salmon-field-054249810-122.centralus.7.azurestaticapps.net |
This was referenced Aug 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Frontend-branch counterpart of #118 and #119. Supersedes #96, #99 and #101.
Targets
frontendand stays there — same fix as the other two branches, made separately, no merge across.Why these cannot be separate pull requests
codeql-actionrequiresinit,analyzeandupload-sarifto run the same version. Mixing them fails with:That is #96's actual error today. This branch has all three sub-actions open as separate Dependabot pull requests at once — #96
init, #101analyze, #99upload-sarif— so it is a three-way version split that cannot converge whichever order they land in.The branch itself is currently healthy: all three pins are 4.37.4 and consistent. Nothing is broken until one of them moves alone, which is precisely what each of those pull requests does.
The change
initf205ea1c(4.37.4)ff2f1c62(4.37.7)analyzef205ea1c(4.37.4)ff2f1c62(4.37.7)upload-sariff205ea1c(4.37.4)ff2f1c62(4.37.7)Three lines. Tag SHAs verified against
github/codeql-action, not taken from the pull request titles — they say 4.37.6, but 4.37.7 is current and4.37.6is5595ccaf, a different commit.This does not unblock the frontend queue on its own
The five Dependabot pull requests on this branch are also held by
npm audit --audit-level=highindeploy.yml, which fails on a genuine high-severity advisory innanoid(GHSA-2v37-7h3g-55p8, patched in 3.3.18; the lock file pins 3.3.16 via postcss). That is addressed in a separate pull request — it is a real finding, not CI rot, and the gate is behaving correctly.🤖 Generated with Claude Code