fix(ci): repoint codeql-action at a SHA that exists

[hyperpolymath]

github/codeql-action@29b1f65c1f735799893313399435a59f54045865 is pinned here but exists in no repository — the GitHub API returns 422 for it.

CodeQL therefore could not start: the run graph fails to build and the job reports startup_failure, so this repository has had no CodeQL scanning at all.

Repointed at 4187e74d05793876e9989daffde9c3e66b4acd07, which is what the v3 tag currently resolves to (v3.37.3), verified against the API.

Found while auditing the estate: the same non-existent SHA was pinned in 104 repositories, so CodeQL was dead across nearly all of them.

[gitar-bot]

CI failed: CI build failed because the governance check detected banned ReScript files in the repository (`vext-tools/src/hooks/Git.res`).

Overview

1 failure found across 1 analyzed log. The build failed during the repository governance check due to policy violations regarding banned programming languages.

Failures

Governance Check: Banned ReScript Files Detected (confidence: high)

• Type: build
• Affected jobs: 90325036100
• Related to change: unclear
• Root cause: The repository contains ReScript files (vext-tools/src/hooks/Git.res), which violate the governance rule cicd_rules/banned_language_file ("ReScript files - use AffineScript instead").
• Suggested fix: Remove or rewrite the ReScript file(s) in AffineScript, or declare an exemption via .hypatia-ignore / an inline # hypatia:ignore cicd_rules/banned_language_file pragma if intentional.

Summary

• Change-related failures: 1 governance/build failure due to banned ReScript files.
• Infrastructure/flaky failures: 0 failures.
• Recommended action: Remove the banned ReScript files, rewrite them in AffineScript, or add the appropriate ignore pragma if the files are required.

Code Review ✅ Approved

Repoints the CodeQL action to a valid commit SHA, resolving the startup failure that previously blocked security scanning. No issues found.

Auto-approved and auto-merge armed: No blocking issues found.
Please see Auto-approve Docs for details on setting custom approval criteria. — merges when pipeline and required approvals pass.

Tip

Comment Gitar fix CI or enable auto-apply: gitar auto-apply:on

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change the behavior for this request:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}

[gitar-bot]

⚠️ Gitar auto-approved this PR but could not enable auto-merge: auto-merge is disabled for this repository — enable "Allow auto-merge" in the repository settings.

[gitar-bot]

Gitar has auto-approved this PR and enabled auto-merge (configure)