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.36.3 to 4.37.0

Release notes

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

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

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]

• 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

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
• 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

4.35.4 - 07 May 2026

• Update default CodeQL bundle version to 2.25.4. #3881

4.35.3 - 01 May 2026

• 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

... (truncated)

Commits

• 99df26d Merge pull request #3996 from github/update-v4.37.0-c7c896d71
• 31c2707 Add changenote for #3973
• 72df218 Update changelog for v4.37.0
• c7c896d Merge pull request #3995 from github/update-bundle/codeql-bundle-v2.26.0
• 3f34ff0 Add changelog note
• 43bec09 Update default bundle to codeql-bundle-v2.26.0
• f58f0d1 Merge pull request #3973 from github/mbg/repo-props/config-file-shorthands
• 7dc37cb Merge remote-tracking branch 'origin/main' into mbg/repo-props/config-file-sh...
• 8e22350 Thread ActionState to initConfig
• 69c9e8c Mark some status-report imports as type-only to avoid circular dependencies
• Additional commits viewable in compare view

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

Release notes

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

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

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]

• 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

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
• 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

4.35.4 - 07 May 2026

• Update default CodeQL bundle version to 2.25.4. #3881

4.35.3 - 01 May 2026

• 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

... (truncated)

Commits

• 99df26d Merge pull request #3996 from github/update-v4.37.0-c7c896d71
• 31c2707 Add changenote for #3973
• 72df218 Update changelog for v4.37.0
• c7c896d Merge pull request #3995 from github/update-bundle/codeql-bundle-v2.26.0
• 3f34ff0 Add changelog note
• 43bec09 Update default bundle to codeql-bundle-v2.26.0
• f58f0d1 Merge pull request #3973 from github/mbg/repo-props/config-file-shorthands
• 7dc37cb Merge remote-tracking branch 'origin/main' into mbg/repo-props/config-file-sh...
• 8e22350 Thread ActionState to initConfig
• 69c9e8c Mark some status-report imports as type-only to avoid circular dependencies
• 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 July 14, 2026, 9:12 AM ET / 13:12 UTC.

Summary
Updates both pinned CodeQL init and analyze actions from v4.36.3 to v4.37.0 in .github/workflows/codeql.yml.

Reproducibility: not applicable. This PR performs routine dependency maintenance rather than fixing a reported runtime bug.

Review metrics: 2 noteworthy metrics.

• Workflow scope: 1 workflow, 2 pins updated. The change is limited to the paired CodeQL init and analyze revisions.
• Reported checks: 8 successful, 0 failed. The updated workflow and repository validation completed without a reported failure.

Merge readiness
Overall: 🦞 diamond lobster
Proof: 🌊 off-meta tidepool
Patch quality: 🦞 diamond lobster
Result: ready for maintainer review.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Next step before merge

• [P2] No repair lane is needed because the patch has no actionable defect and only requires ordinary review and merge handling.

Security
Cleared: The patch retains immutable full-SHA pins for the official CodeQL Action, updates both phases consistently, and adds no permissions, secrets, dependency source, or execution step.

Review details

Best possible solution:

Merge the grouped full-SHA CodeQL update through normal repository review while continuing to keep init and analyze pinned to the same release.

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

Not applicable; this PR performs routine dependency maintenance rather than fixing a reported runtime bug.

Is this the best way to solve the issue?

Yes; updating both CodeQL phases together to the same immutable upstream revision is the narrowest maintainable solution and avoids the mismatch failures documented for the earlier split updates.

AGENTS.md: found, but no applicable review policy affected this item.

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

Label changes

Label justifications:

• P3: This is low-risk routine GitHub Actions dependency maintenance with a four-line diff and green checks.
• rating: 🦞 diamond lobster: Overall readiness is 🦞 diamond lobster; proof is 🌊 off-meta tidepool and patch quality is 🦞 diamond lobster.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: This Dependabot-authored workflow dependency PR is exempt from the external-contributor proof gate; the successful CodeQL run is the relevant validation signal.

Evidence reviewed

What I checked:

• Narrow grouped update: The PR changes exactly two immutable action pins in one workflow, keeping init and analyze on the same CodeQL Action release and avoiding the version mismatch observed in the earlier separate updates. (.github/workflows/codeql.yml:25, 4a7ff39988e7)
• Re-review continuity: The head SHA is unchanged from the previous completed ClawSweeper review, which reported no findings, so no prior blocker remains to be re-raised. (.github/workflows/codeql.yml:25, 4a7ff39988e7)
• Validation signal: All eight reported checks succeeded, including the updated CodeQL analysis, repository tests, Windows tests, secret scanning, and supply-chain reporting. (.github/workflows/codeql.yml:28, 4a7ff39988e7)

Likely related people:

• steipete: The workflow-specific author trail is ambiguous in the available history, making the primary adjacent repository owner the best low-confidence routing candidate for routine CI dependency approval. (role: adjacent repository owner; confidence: low; files: .github/workflows/codeql.yml)

What the crustacean ranks mean

• 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
• 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
• 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
• 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
• 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
• 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
• 🌊 off-meta tidepool: rating does not apply to this item.

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.

How this review workflow works

• 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.

Review history (1 earlier review cycle)

• reviewed 2026-07-10T10:24:04.434Z sha 4a7ff39 :: needs maintainer review before merge. :: none

[clawsweeper]

ClawSweeper status: review started.

I am starting a fresh review of this pull request: build(deps): bump the codeql-action group with 2 updates This is item 1/1 in the current shard. Shard 0/1.

This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking.

Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted.

[steipete]

Maintainer proof at exact head 4a7ff39988e7a098dbede64a6ba445805bc7552a:

• Upstream annotated tag v4.37.0 resolves to commit 99df26d4f13ea111d4ec1a7dddef6063f76b97e9, matching both immutable workflow pins.
• Exact-head hosted runs succeeded: CI 29076566793, CodeQL 29076566803, pull-request secret scan 29076566809, and push secret scan 29076564140.
• GOWORK=off go mod tidy plus git diff --exit-code -- go.mod go.sum: clean.
• GOWORK=off go vet ./...: passed.
• GOWORK=off go test -count=1 ./...: passed, 18 packages.
• AutoReview: clean; no accepted/actionable findings. Verdict: patch correct, confidence 0.99.

No repair needed. Land-ready at this exact head; not merged by this triage lane.