chore(deps): bump the actions group across 1 directory with 2 updates

[dependabot]

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

Updates github/codeql-action/init from 4.37.0 to 4.37.3

Release notes

Sourced from github/codeql-action/init'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

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]

• 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

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

4.36.1 - 02 Jun 2026

No user facing changes.

4.36.0 - 22 May 2026

• 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

4.35.5 - 15 May 2026

• 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

... (truncated)

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

Updates github/codeql-action/analyze from 4.37.0 to 4.37.3

Release notes

Sourced from github/codeql-action/analyze'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

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]

• 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

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

4.36.1 - 02 Jun 2026

No user facing changes.

4.36.0 - 22 May 2026

• 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

4.35.5 - 15 May 2026

• 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

... (truncated)

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

[clawsweeper]

Codex review: needs maintainer review before merge. Reviewed July 24, 2026, 1:30 PM ET / 17:30 UTC.

ClawSweeper review

What this changes

The PR updates the pinned github/codeql-action/init and github/codeql-action/analyze revisions in the CodeQL workflow from v4.37.0 to v4.37.3.

Merge readiness

⚠️ Ready for maintainer review - 2 items remain

This narrow Dependabot update advances the existing pinned CodeQL actions, but it is too recent for an age-based cleanup close and workflow validation is not yet clean: one Windows check failed and another remains in progress. Keep the PR open for ordinary CI review; no patch defect is established from the available evidence.

Priority: P3
Reviewed head: 6c5f3c6b1b1f17800110b6852d0872945352cab4

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	The patch is clean and tightly scoped, with one unresolved CI result still needing confirmation.
Proof confidence	🌊 off-meta tidepool	Not applicable: This bot-authored workflow dependency update is appropriately evidenced by the GitHub Actions results rather than external contributor runtime proof.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Not applicable	Not applicable: This bot-authored workflow dependency update is appropriately evidenced by the GitHub Actions results rather than external contributor runtime proof.
Evidence reviewed	3 items	Scoped workflow diff: The branch changes one workflow file and replaces the same SHA-pinned CodeQL Action revision in both the initialization and analysis steps. Workflow check evidence: The provided check state has successful CodeQL and workflow-lint jobs, but Node 24 check (windows-latest) failed and Node 22 check (windows-latest) was still running on the current head. Repository review policy: The checked repository policy treats GitHub Actions and package security changes conservatively; the proposed change remains limited to existing SHA-pinned actions.
Findings	None	None.
Security	None	None.

How this fits together

The CodeQL workflow runs static security analysis for this Node.js package on GitHub-hosted runners. It initializes language analysis and then uploads the analysis results to GitHub security reporting.

flowchart LR
  Source[Package source] --> Workflow[CodeQL workflow]
  Workflow --> Init[Initialize CodeQL]
  Init --> Matrix[Language matrix]
  Matrix --> Analyze[Analyze source]
  Analyze --> Results[GitHub security results]

Loading

Before merge

• Resolve merge risk (P1) - CodeQL v4.37.3 changes CI security-analysis runtime behavior; the failed Windows job should be confirmed unrelated to this action bump before merge.
• Complete next step (P2) - Wait for the current Windows validation result or its failure diagnosis; no specific repository repair is established for an automated work lane.

Agent review details

Security

None.

Review metrics

Metric	Value	Why it matters
Workflow pins	2 changed, 0 added, 0 removed	Both edits advance the same existing CodeQL Action revision.
Files affected	1 workflow file	The proposed automation change is tightly scoped.

Merge-risk options

Maintainer options:

1. Verify the Windows result before merge (recommended)
   Inspect or rerun the failed Windows job on the current head and merge once it is green or clearly unrelated to the CodeQL revision.
2. Pause for workflow diagnosis
   Hold the update if the Windows failure reproduces and is attributable to CodeQL Action v4.37.3.

Copy recommended automerge instruction

@clawsweeper automerge

Special instructions:
Verify the failed Windows check on the current head; merge only if it is green or clearly unrelated to the CodeQL action revision.

Technical review

Best possible solution:

Confirm the failed Windows job on the current head is unrelated or repair the workflow if it is caused by CodeQL v4.37.3, then land the two pinned action updates together.

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

Not applicable; this PR updates CI action pins rather than reporting a reproducible package defect. The relevant validation path is the workflow run on the proposed head.

Is this the best way to solve the issue?

Yes; advancing both CodeQL steps to the same upstream pinned v4.37.3 revision is the narrow supported maintenance path, provided the Windows validation result is resolved or explained.

AGENTS.md: found and applied where relevant.

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

Labels

Label changes:

• add P3: This is routine CI dependency maintenance with no demonstrated user-facing package regression.
• add merge-risk: 🚨 automation: The diff changes repository security automation and the current Windows validation state is not clean.
• add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
• add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: This bot-authored workflow dependency update is appropriately evidenced by the GitHub Actions results rather than external contributor runtime proof.

Label justifications:

• P3: This is routine CI dependency maintenance with no demonstrated user-facing package regression.
• merge-risk: 🚨 automation: The diff changes repository security automation and the current Windows validation state is not clean.
• rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: This bot-authored workflow dependency update is appropriately evidenced by the GitHub Actions results rather than external contributor runtime proof.

Evidence

What I checked:

• Scoped workflow diff: The branch changes one workflow file and replaces the same SHA-pinned CodeQL Action revision in both the initialization and analysis steps. (.github/workflows/codeql.yml:47, 6c5f3c6b1b1f)
• Workflow check evidence: The provided check state has successful CodeQL and workflow-lint jobs, but Node 24 check (windows-latest) failed and Node 22 check (windows-latest) was still running on the current head. (.github/workflows/codeql.yml:47, 6c5f3c6b1b1f)
• Repository review policy: The checked repository policy treats GitHub Actions and package security changes conservatively; the proposed change remains limited to existing SHA-pinned actions. (AGENTS.md:1, ab81352a7e80)

Likely related people:

• unknown: The available review material identifies the changed workflow but does not provide a reliable named current-main history owner for this file. (role: workflow-area contributor; confidence: low; files: .github/workflows/codeql.yml)

Rank-up moves

Optional improvements that raise the rating; they are not merge blockers.

• Confirm the failing Windows job is unrelated or repair the workflow before merging.

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.