build(deps): bump github/codeql-action from 4 to 4.37.3

[dependabot]

Bumps github/codeql-action from 4 to 4.37.3.

Release notes

Sourced from github/codeql-action's releases.

v4.37.3

No user facing changes.

v4.37.2

• The new address format for the config-file input that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, the remote= prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #4023
• The CodeQL Action can now make use of configured private registries in Default Setup to retrieve CodeQL configuration files from remote repositories that require authentication. This will allow customers to store their CodeQL configuration in a single repository that can then be referenced by Default Setup workflows in other repositories. We expect to roll this and other, related changes out to everyone in July. #4007

v4.37.1

• Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. #3956
• Update default CodeQL bundle version to 2.26.1. #4019

v4.37.0

• Update default CodeQL bundle version to 2.26.0. #3995
• In addition to the existing input format, the config-file input for the codeql-action/init step will soon support a new [owner/]repo[@ref][:path] format. All components except the repository name are optional. If omitted, owner defaults to the same owner as the repository the analysis is running for, ref to main, and path to .github/codeql-action.yaml. Support for this format ships in this version of the CodeQL Action, but will only be enabled over the coming weeks. #3973

v4.36.3

No user facing changes.

v4.36.2

• Cache CodeQL CLI version information across Actions steps. #3943
• Reduce requests while waiting for analysis processing by using exponential backoff when polling SARIF processing status. #3937
• Update default CodeQL bundle version to 2.25.6. #3948

v4.36.1

No user facing changes.

v4.36.0

• Breaking change: Bump the minimum required CodeQL bundle version to 2.19.4. #3894
• Add support for SHA-256 Git object IDs. #3893
• Update default CodeQL bundle version to 2.25.5. #3926

v4.35.5

• We have improved how the JavaScript bundles for the CodeQL Action are generated to avoid duplication across bundles and reduce the size of the repository by around 70%. This should have no effect on the runtime behaviour of the CodeQL Action. #3899
• For performance and accuracy reasons, improved incremental analysis will now only be enabled on a pull request when diff-informed analysis is also enabled for that run. If diff-informed analysis is unavailable (for example, because the PR diff ranges could not be computed), the action will fall back to a full analysis. #3791
• If multiple inputs are provided for the GitHub-internal analysis-kinds input, only code-scanning will be enabled. The analysis-kinds input is experimental, for GitHub-internal use only, and may change without notice at any time. #3892
• Added an experimental change which, when running a Code Scanning analysis for a PR with improved incremental analysis enabled, prefers CodeQL CLI versions that have a cached overlay-base database for the configured languages. This speeds up analysis for a repository when there is not yet a cached overlay-base database for the latest CLI version. We expect to roll this change out to everyone in May. #3880

v4.35.4

• Update default CodeQL bundle version to 2.25.4. #3881

v4.35.3

• Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.19.3 and earlier. These versions of CodeQL were discontinued on 9 April 2026 alongside GitHub Enterprise Server 3.15, and will be unsupported by the next minor release of the CodeQL Action. #3837
• Configurations for private registries that use Cloudsmith or GCP OIDC are now accepted. #3850
• Best-effort connection tests for private registries now use GET requests instead of HEAD for better compatibility with various registry implementations. For NuGet feeds, the test is now always performed against the service index. #3853
• Fixed a bug where two diagnostics produced within the same millisecond could overwrite each other on disk, causing one of them to be lost. #3852
• Update default CodeQL bundle version to 2.25.3. #3865

v4.35.2

• The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable is deprecated and will be removed in May 2026. If you are affected by this, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #3795
• The Git version 2.36.0 requirement for improved incremental analysis now only applies to repositories that contain submodules. #3789

... (truncated)

Changelog

Sourced from github/codeql-action's changelog.

4.37.3 - 22 Jul 2026

No user facing changes.

4.37.2 - 21 Jul 2026

• The new address format for the config-file input that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, the remote= prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #4023
• The CodeQL Action can now make use of configured private registries in Default Setup to retrieve CodeQL configuration files from remote repositories that require authentication. This will allow customers to store their CodeQL configuration in a single repository that can then be referenced by Default Setup workflows in other repositories. We expect to roll this and other, related changes out to everyone in July. #4007

4.37.1 - 16 Jul 2026

• Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. #3956
• Update default CodeQL bundle version to 2.26.1. #4019

4.37.0 - 08 Jul 2026

• Update default CodeQL bundle version to 2.26.0. #3995
• In addition to the existing input format, the config-file input for the codeql-action/init step will soon support a new [owner/]repo[@ref][:path] format. All components except the repository name are optional. If omitted, owner defaults to the same owner as the repository the analysis is running for, ref to main, and path to .github/codeql-action.yaml. Support for this format ships in this version of the CodeQL Action, but will only be enabled over the coming weeks. #3973

4.36.3 - 01 Jul 2026

No user facing changes.

Commits

• e4fba86 Merge pull request #4031 from github/update-v4.37.3-72f6a9da0
• fb50ab5 Update changelog for v4.37.3
• 72f6a9d Merge pull request #4030 from github/mbg/fix/no-proxy
• 3b5ee58 Use default request options instead of undefined
• bfb6be4 Merge pull request #4028 from github/mergeback/v4.37.2-to-main-e0647621
• 526ab84 Rebuild
• d6217b9 Update changelog and version after v4.37.2
• e064762 Merge pull request #4027 from github/update-v4.37.2-385bcdc5a
• e0faed8 Add a couple of change notes
• 73aad0e Update changelog for v4.37.2
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[clawsweeper]

Codex review: needs maintainer review before merge. Reviewed August 1, 2026, 7:48 PM ET / 23:48 UTC.

ClawSweeper review

What this changes

Pins the CodeQL workflow’s initialization and analysis actions from the floating v4 tag to the released v4.37.3 tag.

Merge readiness

⚠️ Ready for maintainer review - 4 items remain

This PR remains necessary: current main and the latest release still use the floating CodeQL v4 action tag, while this branch pins both CodeQL steps to v4.37.3. The focused update is correct and PR-head scans succeeded, but the declared workflow code owner should make the normal acceptance decision because it changes the runtime used for future security scans.

Priority: P3
Reviewed head: 93bbb076cc88873c0830a6be5319c07eb80211cd
Owner decision: Required. See Decision needed.

Review scores

Measure	Result	What it means
Overall readiness	🦞 diamond lobster (5/6)	A narrow, internally consistent workflow dependency update with direct successful CodeQL runtime proof and no actionable patch defect.
Proof confidence	🦞 diamond lobster (5/6)	Sufficient (live_output): The PR-head CodeQL check completed successfully, directly demonstrating that the updated initialization and analysis actions ran in this repository’s workflow.
Patch quality	🦞 diamond lobster (5/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Verified	Sufficient (live_output): The PR-head CodeQL check completed successfully, directly demonstrating that the updated initialization and analysis actions ran in this repository’s workflow.
Evidence reviewed	6 items	Current main still needs the update: Current main uses github/codeql-action/init@v4 and github/codeql-action/analyze@v4, so the requested v4.37.3 pin is not already implemented. Branch change is narrow and paired: The PR changes exactly the two paired CodeQL action references, keeping initialization and analysis on the same v4.37.3 release. Workflow origin and ownership trail: The CodeQL workflow, including its original v4 references, was introduced by the shared-pipeline migration commit authored by Peter Steinberger.
Findings	None	None.
Security	None	None.

How this fits together

The CodeQL GitHub Actions workflow runs on pull requests, pushes, scheduled scans, and manual dispatches to analyze the repository’s Go code and publish security results. This PR changes the version of the external CodeQL action that performs its initialization and analysis steps.

flowchart LR
  A[GitHub events] --> B[CodeQL workflow]
  B --> C[CodeQL initialization]
  C --> D[Go code analysis]
  D --> E[Security scan results]
  F[Action version pin] --> C
  F --> D

Loading

Decision needed

Question	Recommendation
Should the workflow owner accept pinning both CodeQL steps to v4.37.3 instead of continuing to follow the floating v4 tag?	Approve the v4.37.3 pin: Accept the tested released runtime for both paired CodeQL steps and retain the normal rollback path if later scheduled scans reveal an upstream regression.

Why: The patch is mechanically sound and has successful PR-head scan evidence, but it intentionally changes the security-scanning runtime and freezes future v4 patch movement until another update lands.

Before merge

• Resolve merge risk (P1) - Merging changes the external CodeQL runtime used by future push and scheduled security scans; a later upstream incompatibility would require reverting or updating this workflow.
• Resolve merge risk (P1) - Pinning to v4.37.3 stops the workflow from automatically following later v4 patch-tag moves until a subsequent dependency update is merged.
• Complete next step (P2) - A declared workflow owner must accept the operational trade-off of freezing CodeQL at v4.37.3; no narrow repair is needed.

Agent review details

Security

None.

Review metrics

Metric	Value	Why it matters
Workflow references	2 changed, 0 added, 0 removed	Both halves of the CodeQL workflow move together to the same released action version.
Affected workflows	1 workflow changed	The update affects the security scanner invoked by pull-request, push, scheduled, and manual workflow runs.

Merge-risk options

Maintainer options:

1. Approve the tested CodeQL runtime pin (recommended)
   Merge the two-reference update after the workflow owner accepts v4.37.3 as the runtime for future scheduled and push scans, with normal rollback available if upstream behavior regresses.
2. Retain floating v4 behavior
   Pause or close the update if automatic movement within CodeQL Action v4 is an intentional operational policy for this repository.

Technical review

Best possible solution:

Approve the paired v4.37.3 pin after the workflow owner accepts the normal rollback responsibility, then continue consuming future CodeQL action updates through focused dependency PRs.

Do we have a high-confidence way to reproduce the issue?

Not applicable—the PR is a dependency-maintenance update rather than a bug report; the successful PR-head CodeQL run directly exercises the changed workflow path.

Is this the best way to solve the issue?

Yes—the two references are the complete CodeQL action surface in this workflow, and updating them together to one released version is the narrowest maintainable change.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 8141387a4f95.

Labels

Label justifications:

• P3: This is a routine dependency-maintenance update with successful checks and no reported user-facing regression.
• merge-risk: 🚨 automation: The change alters the third-party runtime used by an automated CodeQL security-scanning workflow.
• rating: 🦞 diamond lobster: Overall readiness is 🦞 diamond lobster; proof is 🦞 diamond lobster and patch quality is 🦞 diamond lobster.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (live_output): The PR-head CodeQL check completed successfully, directly demonstrating that the updated initialization and analysis actions ran in this repository’s workflow.
• proof: sufficient: Contributor real behavior proof is sufficient. The PR-head CodeQL check completed successfully, directly demonstrating that the updated initialization and analysis actions ran in this repository’s workflow.

Evidence

What I checked:

• Current main still needs the update: Current main uses github/codeql-action/init@v4 and github/codeql-action/analyze@v4, so the requested v4.37.3 pin is not already implemented. (.github/workflows/codeql.yml:32, 8141387a4f95)
• Branch change is narrow and paired: The PR changes exactly the two paired CodeQL action references, keeping initialization and analysis on the same v4.37.3 release. (.github/workflows/codeql.yml:32, 93bbb076cc88)
• Workflow origin and ownership trail: The CodeQL workflow, including its original v4 references, was introduced by the shared-pipeline migration commit authored by Peter Steinberger. (.github/workflows/codeql.yml:32, 4f3017c8188d)
• Released baseline also lacks the pin: Release v0.11.10 contains the workflow-introduction commit and still uses the floating v4 references, confirming this is an outstanding maintenance update rather than an already-shipped fix. (.github/workflows/codeql.yml:32, 4f3017c8188d)
• After-change behavior proof: The provided PR-head check data reports successful CodeQL analysis along with successful lint, test, dependency, Docker, release-check, and secret-scan checks. (.github/workflows/codeql.yml:37, 93bbb076cc88)
• Declared review boundary: The repository CODEOWNERS file assigns .github/workflows/ to the openclaw/openclaw-secops team. (.github/CODEOWNERS:4, 8141387a4f95)

Likely related people:

• openclaw/openclaw-secops: CODEOWNERS assigns the entire .github/workflows/ directory, including the changed CodeQL workflow, to this team. (role: declared workflow code owner; confidence: high; files: .github/CODEOWNERS, .github/workflows/codeql.yml)
• Peter Steinberger: Introduced the current CodeQL workflow and its original action references in the shared-pipeline migration. (role: workflow introducer; confidence: high; commits: 4f3017c8188d; files: .github/workflows/codeql.yml)

Rating scale

Score	Internal tier	Crab rank	Meaning
6/6	S	🦀 challenger crab	Exceptional readiness
5/6	A	🦞 diamond lobster	Very strong readiness
4/6	B	🐚 platinum hermit	Good normal PR; ordinary maintainer review
3/6	C	🦐 gold shrimp	Useful, but confidence is limited
2/6	D	🦪 silver shellfish	Proof or implementation needs work
1/6	F	🧂 unranked krab	Not merge-ready
N/A	NA	🌊 off-meta tidepool	Rating does not apply

Overall follows the weaker of proof and patch quality.
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

Workflow

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

History

Review history (5 earlier review cycles)

• reviewed 2026-08-01T13:00:04.511Z sha 93bbb07 :: needs maintainer review before merge. :: none
• reviewed 2026-08-01T14:52:30.625Z sha 93bbb07 :: needs maintainer review before merge. :: none
• reviewed 2026-08-01T16:17:48.733Z sha 93bbb07 :: needs maintainer review before merge. :: none
• reviewed 2026-08-01T18:44:18.613Z sha 93bbb07 :: needs maintainer review before merge. :: none
• reviewed 2026-08-01T22:12:37.549Z sha 93bbb07 :: needs maintainer review before merge. :: none

[steipete]

This PR is already one patch behind: CodeQL Action v4.37.4 was released on 2026-07-30, while this branch targets v4.37.3.

#158 updates both CodeQL steps to the current v4.37.4 release and includes the rest of the repository's dependency refresh, with full local gates and live CLI proof.

Recommendation: close this PR as superseded by #158, then land #158 after its CI is green.

[dependabot]

Looks like github/codeql-action is up-to-date now, so this is no longer needed.

[steipete]

#158 landed as 48b28c60866c95e4c106ce998e0c227998ed185e with CodeQL v4.37.4, superseding this v4.37.3 update. Closing as described in the earlier note.