build(deps): bump the codeql-action group with 2 updates

[dependabot]

Bumps the codeql-action group with 2 updates: github/codeql-action/init and github/codeql-action/analyze.

Updates github/codeql-action/init from 4.37.4 to 4.37.6

Release notes

Sourced from github/codeql-action/init's releases.

v4.37.6

• Changed the default filepath for the new remote file address format that was introduced in CodeQL Action 4.37.0 / 3.37.0 to .github/codeql-config.yml to align it with the suggested path that is used elsewhere. #4070

v4.37.5

• Fixed a bug where a network error while streaming the download of the CodeQL bundle could terminate the init Action instead of falling back to downloading the bundle before extracting it. #4061

Changelog

Sourced from github/codeql-action/init's changelog.

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

[UNRELEASED]

No user facing changes.

4.37.6 - 04 Aug 2026

• Changed the default filepath for the new remote file address format that was introduced in CodeQL Action 4.37.0 / 3.37.0 to .github/codeql-config.yml to align it with the suggested path that is used elsewhere. #4070

4.37.5 - 03 Aug 2026

• Fixed a bug where a network error while streaming the download of the CodeQL bundle could terminate the init Action instead of falling back to downloading the bundle before extracting it. #4061

4.37.4 - 29 Jul 2026

• This version of the CodeQL Action adds support for the tools input for the codeql-action/init step to be specified using a github-codeql-tools repository property. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value to toolcache to always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided for tools in the workflow definition always takes precedence unless the value of the repository property starts with !. #4037
• Update default CodeQL bundle version to 2.26.2. #4051

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.

4.36.2 - 04 Jun 2026

• 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

... (truncated)

Commits

• 5595cca Merge pull request #4071 from github/update-v4.37.6-6a9359a1b
• ec9c757 Add change note for PR 4070
• 45c8742 Update changelog for v4.37.6
• 6a9359a Merge pull request #4070 from github/mbg/remote-address/change-file-default
• 065cdc0 Change DEFAULT_CONFIG_FILE_NAME
• f99dd5a Merge pull request #4066 from github/dependabot/npm_and_yarn/js-yaml-5.2.2
• 1804b21 Merge pull request #4068 from github/mergeback/v4.37.5-to-main-d1ba80a1
• 3020a2f Rebuild
• 93c3a5a Update changelog and version after v4.37.5
• d1ba80a Merge pull request #4067 from github/update-v4.37.5-1cd4d01d5
• Additional commits viewable in compare view

Updates github/codeql-action/analyze from 4.37.4 to 4.37.6

Release notes

Sourced from github/codeql-action/analyze's releases.

v4.37.6

• Changed the default filepath for the new remote file address format that was introduced in CodeQL Action 4.37.0 / 3.37.0 to .github/codeql-config.yml to align it with the suggested path that is used elsewhere. #4070

v4.37.5

• Fixed a bug where a network error while streaming the download of the CodeQL bundle could terminate the init Action instead of falling back to downloading the bundle before extracting it. #4061

Changelog

Sourced from github/codeql-action/analyze's changelog.

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

[UNRELEASED]

No user facing changes.

4.37.6 - 04 Aug 2026

• Changed the default filepath for the new remote file address format that was introduced in CodeQL Action 4.37.0 / 3.37.0 to .github/codeql-config.yml to align it with the suggested path that is used elsewhere. #4070

4.37.5 - 03 Aug 2026

• Fixed a bug where a network error while streaming the download of the CodeQL bundle could terminate the init Action instead of falling back to downloading the bundle before extracting it. #4061

4.37.4 - 29 Jul 2026

• This version of the CodeQL Action adds support for the tools input for the codeql-action/init step to be specified using a github-codeql-tools repository property. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value to toolcache to always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided for tools in the workflow definition always takes precedence unless the value of the repository property starts with !. #4037
• Update default CodeQL bundle version to 2.26.2. #4051

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.

4.36.2 - 04 Jun 2026

• 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

... (truncated)

Commits

• 5595cca Merge pull request #4071 from github/update-v4.37.6-6a9359a1b
• ec9c757 Add change note for PR 4070
• 45c8742 Update changelog for v4.37.6
• 6a9359a Merge pull request #4070 from github/mbg/remote-address/change-file-default
• 065cdc0 Change DEFAULT_CONFIG_FILE_NAME
• f99dd5a Merge pull request #4066 from github/dependabot/npm_and_yarn/js-yaml-5.2.2
• 1804b21 Merge pull request #4068 from github/mergeback/v4.37.5-to-main-d1ba80a1
• 3020a2f Rebuild
• 93c3a5a Update changelog and version after v4.37.5
• d1ba80a Merge pull request #4067 from github/update-v4.37.5-1cd4d01d5
• 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[clawsweeper]

Codex review: needs maintainer review before merge. Reviewed August 7, 2026, 2:38 PM ET / 18:38 UTC.

ClawSweeper review

What this changes

The PR updates the pinned CodeQL initialization and analysis actions in the repository’s security-scanning workflow from v4.37.4 to v4.37.6.

Merge readiness

⛔ Blocked by patch quality or review findings - 4 items remain

Keep open: current main still pins CodeQL v4.37.4, so this focused v4.37.6 update remains useful, pending the normal maintainer trust decision for newly executed upstream action code.

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

Review scores

Measure	Result	What it means
Overall readiness	🧂 unranked krab (1/6)	PR readiness rating was derived from proof quality, review findings, security review, and reviewer confidence.
Proof confidence	🌊 off-meta tidepool	Not applicable: Real behavior proof is not required for maintainer- or bot-authored pull requests.
Patch quality	🧂 unranked krab (1/6)	Security review found an item that needs attention.

Verification

Check	Result	Evidence
Real behavior	Not applicable	Not applicable: Real behavior proof is not required for maintainer- or bot-authored pull requests.
Evidence reviewed	5 items	Current main remains on v4.37.4: Both CodeQL steps on current main use the v4.37.4 immutable action commit, so the requested update has not already landed. Focused PR patch: The PR changes only the two CodeQL action pins, from v4.37.4 to the immutable v4.37.6 commit. Prior workflow-update provenance: The current CodeQL pin was introduced by the prior merged security-actions refresh; its commit credits Peter Steinberger as co-author alongside Dependabot.
Findings	None	None.
Security	Needs attention	Verify the updated CodeQL action revision: Both workflow steps move to a new upstream action commit that executes in CI; validate its provenance before accepting the supply-chain change.

How this fits together

GitHub Actions runs the repository’s CodeQL workflow on source changes. The pinned CodeQL actions obtain the scanning toolchain and upload security-analysis results to GitHub.

flowchart LR
  A[Source changes] --> B[CodeQL workflow]
  B --> C[Pinned CodeQL actions]
  C --> D[CodeQL toolchain]
  D --> E[Security analysis]
  E --> F[GitHub security results]

Loading

Decision needed

Question	Recommendation
Should crawlkit accept github/codeql-action commit 5595ccaf912efad79be6eef63a5619ff05969be3 for its CodeQL workflow?	Accept the verified update: Approve the v4.37.6 immutable action revision after checking its upstream provenance and release notes.

Why: The patch is mechanically narrow, but it changes third-party code executed within the repository security workflow.

Before merge

• Resolve security concern: Verify the updated CodeQL action revision - Both workflow steps move to a new upstream action commit that executes in CI; validate its provenance before accepting the supply-chain change.
• Resolve merge risk (P1) - Merging replaces third-party action code executed by a workflow with security-events write permission; passing checks do not settle the upstream-action trust decision.
• Improve patch quality - Resolve the security review concern or explain why the changed path is safe.

Findings

• [medium] Verify the updated CodeQL action revision — .github/workflows/codeql.yml:25

Agent review details

Security

Needs attention: The diff changes third-party action code executed by a workflow with security-event upload permission, requiring normal maintainer supply-chain approval.

Review metrics

Metric	Value	Why it matters
Workflow pins	2 changed, 0 added, 0 removed	The PR is limited to the init and analyze CodeQL revisions in one workflow.

Merge-risk options

Maintainer options:

1. Verify and accept the new action revision (recommended)
   Review the v4.37.6 upstream source and release provenance, then merge if the repository accepts that third-party workflow code.
2. Hold the current CodeQL pin
   Pause this PR if the new upstream action revision has not received the repository’s normal supply-chain approval.

Technical review

Best possible solution:

Verify the upstream v4.37.6 release provenance and merge the two immutable pin updates only if the workflow code owner accepts that supply-chain change.

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

Not applicable: this PR updates CI action pins rather than reporting a user-facing bug; the supplied checks show the proposed workflow completed successfully.

Is this the best way to solve the issue?

Yes: updating both CodeQL steps to one immutable upstream release commit is the narrowest maintainable update, subject to maintainer supply-chain approval.

AGENTS.md: found and applied where relevant.

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

Labels

Label changes:

• add merge-risk: 🚨 security-boundary: The new third-party action revision executes in a workflow granted security-events write permission.
• add rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🌊 off-meta tidepool and patch quality is 🧂 unranked krab.
• remove rating: 🐚 platinum hermit: Current PR rating is rating: 🧂 unranked krab, so this older rating label is no longer current.

Label justifications:

• P3: This is a narrow, low-urgency update to CI security-scanning automation.
• merge-risk: 🚨 automation: The patch changes the actions that perform repository CodeQL analysis and result upload.
• merge-risk: 🚨 security-boundary: The new third-party action revision executes in a workflow granted security-events write permission.
• rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🌊 off-meta tidepool and patch quality is 🧂 unranked krab.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: Real behavior proof is not required for maintainer- or bot-authored pull requests.

Evidence

Security concerns:

• [medium] Verify the updated CodeQL action revision — .github/workflows/codeql.yml:25
  Both workflow steps move to a new upstream action commit that executes in CI; validate its provenance before accepting the supply-chain change.
  Confidence: 0.95

What I checked:

• Current main remains on v4.37.4: Both CodeQL steps on current main use the v4.37.4 immutable action commit, so the requested update has not already landed. (.github/workflows/codeql.yml:25, 931246004485)
• Focused PR patch: The PR changes only the two CodeQL action pins, from v4.37.4 to the immutable v4.37.6 commit. (.github/workflows/codeql.yml:25, a08c83dbbe07)
• Prior workflow-update provenance: The current CodeQL pin was introduced by the prior merged security-actions refresh; its commit credits Peter Steinberger as co-author alongside Dependabot. (.github/workflows/codeql.yml:25, 41c41f6ca172)
• Workflow ownership: Repository CODEOWNERS assigns all GitHub workflow files to the openclaw-secops team. (.github/CODEOWNERS:4, 931246004485)
• Branch execution: The supplied PR checks report successful CodeQL analysis, test, Windows test, and secret-scan runs on the proposed head. (.github/workflows/codeql.yml:25, a08c83dbbe07)

Likely related people:

• openclaw/openclaw-secops: CODEOWNERS assigns .github/workflows/ to this team. (role: workflow code owner; confidence: high; files: .github/CODEOWNERS, .github/workflows/codeql.yml)
• Peter Steinberger: The previous merged refresh of the same CodeQL workflow pins credits Peter Steinberger as co-author. (role: recent security-automation contributor; confidence: medium; commits: 41c41f6ca172; files: .github/workflows/codeql.yml)
• dependabot[bot]: The current CodeQL action revision was introduced by Dependabot’s prior merged security-actions refresh. (role: prior update author; confidence: high; commits: 41c41f6ca172; 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 (6 earlier review cycles)

• reviewed 2026-08-07T07:30:58.639Z sha a08c83d :: needs maintainer review before merge. :: none
• reviewed 2026-08-07T09:27:23.753Z sha a08c83d :: needs maintainer review before merge. :: none
• reviewed 2026-08-07T11:08:12.898Z sha a08c83d :: needs maintainer review before merge. :: none
• reviewed 2026-08-07T12:28:26.440Z sha a08c83d :: needs maintainer review before merge. :: none
• reviewed 2026-08-07T15:08:31.161Z sha a08c83d :: needs maintainer review before merge. :: none
• reviewed 2026-08-07T16:44:19.775Z sha a08c83d :: needs maintainer review before merge. :: none

[steipete]

Landed as 5c1729e after rebasing onto the SQLite update.

Verification:

• annotated upstream CodeQL v4.37.6 tag dereferences exactly to 5595ccaf912efad79be6eef63a5619ff05969be3
• reviewed the upstream v4.37.4-to-v4.37.6 source/release delta and accepted the security-events workflow trust change
• actionlint and make check passed, including vulnerability, ordinary, and race suites
• real built crawlctl reported its version/help without touching live archives
• exact-head Linux/Windows CI, CodeQL, and secret scans passed
• complete-branch Codex autoreview was clean with no accepted/actionable findings