ci(deps): bump github/codeql-action/analyze from 3.35.5 to 4.37.3

[dependabot]

Bumps github/codeql-action/analyze from 3.35.5 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

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/analyze's changelog.

CodeQL Action Changelog

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

[UNRELEASED]

• 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

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

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

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)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 45231b6202

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Keep CodeQL steps on one action version

This workflow still initializes CodeQL with the old v3 SHA in the Initialize CodeQL step, but this changed analysis step now runs a v4 SHA. CodeQL Action treats mixed versions in one workflow as unsupported and v3.30.4+ can fail later steps when they read an init configuration generated by a different action version, so CodeQL runs will stop at analysis instead of uploading results until the init and analyze pins are bumped or downgraded together.

Useful? React with 👍 / 👎.

[helebest]

Automated Dependabot review — ❌ blocked, not merging

Scope: github/codeql-action/analyze 3.35.5 → 4.37.3 (.github/workflows/codeql.yml, SHA-pinned).

Step 1 — Code review

The diff is a single-line SHA bump of the analyze step and is internally consistent. One cosmetic nit: the trailing version comment still reads # v3 and was not updated to # v4 — harmless (the SHA is authoritative) but slightly misleading.

Step 2/3 — CI verification (fail-fast)

The Analyze Python check fails. Job log:

Analysis upload status is failed.
CodeQL job status was configuration error.
##[warning]... github/codeql-action/init@458d36d7... target Node.js 20 but are being forced to run on Node.js 24

Root cause: this PR bumps only the analyze step to v4 while the init step in the same workflow is still pinned to v3 (458d36d7…). The CodeQL Action requires init and analyze to be from the same major version; the v4-analyze / v3-init mismatch produces a configuration error, so the analysis cannot complete. The bump cannot pass on its own.

Decision

Per fail-fast, I am stopping and not merging. This PR and #259 (which bumps init to 4.36.2) are two halves of the same upgrade and must land together, pinned to the same version — e.g. bump both init and analyze to a single v4 release (4.37.3). Recommend consolidating them (or ·@·d·ependabot r·ecreate once a grouped update is configured) rather than merging either standalone.

No further action taken. This is an automated review.

---

Generated by Claude Code

[helebest]

Automated Dependabot review — github/codeql-action/analyze 3.35.5 → 4.37.3

Step 1 — Code review

• Consistency: ✅ Diff matches the description — a single SHA-pin bump of the analyze step in .github/workflows/codeql.yml from 458d36d (v3.35.5) to e4fba86 (v4.37.3).
• Correctness / Effectiveness: The pin resolves to the v4.37.3 release tag; the change in isolation is valid.
• Security: SHA-pinned to an official github/codeql-action release; v4.x is the current supported major. No advisories against this bump.
• Conventions / Test coverage: N/A — CI workflow config only, no application code, so no unit tests apply; CI itself exercises the action.

Step 2/3 — Regression & CI
❌ The required Analyze Python (CodeQL) check fails:

CodeQL job status was configuration error.

Root cause: this PR bumps only the analyze step to v4, while the init step in the same workflow remains at v3.35.5 (458d36d). The CodeQL Action requires init and analyze to run the same version; the resulting v3/v4 mismatch is rejected as a configuration error (the failing run still loads github/codeql-action/init@458d36d…).

Step 4 — Merge: STOP, not merged (fail-fast).
A required check is red, so this PR is not merged. To land the update, init and analyze must be bumped together to the same version. Companion PR #259 bumps init, but to 4.36.2, which would still mismatch the 4.37.3 here. Recommended fix: bump both steps to v4.37.3 in one change (e.g. ·@·d·ependabot r·ecreate #259 so it targets 4.37.3, then land them together), and re-run CI.

---

Generated by Claude Code

[helebest]

Dependabot PR review — STOP (fail-fast)

Decision: not merging. A required check is failing and this PR cannot pass CI on its own.

Step 1 — Code review

• Change: github/codeql-action/analyze 3.35.5 → 4.37.3 (pinned SHA 458d36d… → e4fba86…) in .github/workflows/codeql.yml. One-line, matches the PR description.
• Consistency nit: the inline comment still reads # v3 after the SHA, but the new SHA e4fba86 is release v4.37.3. The comment is now misleading (Dependabot did not refresh it). Not the blocker, but worth correcting.
• Correctness — blocking: this repo's CodeQL workflow uses both codeql-action/init and codeql-action/analyze, and the CodeQL Action requires init and analyze to be the same major version. This PR bumps only analyze to v4 while init stays at v3, producing a v3/v4 mismatch.

Step 2/3 — Regression / CI

The Analyze Python check failed with:

CodeQL job status was configuration error.
##[warning] ... github/codeql-action/init@458d36d7… (v3) ...

i.e. v4 analyze running against a v3 init database → configuration error. This confirms the mismatch above.

Root cause & recommendation

Dependabot split the single github/codeql-action monorepo upgrade into two independent PRs — this one (analyze, #262) and #264 (init). Neither can go green alone, and merging either one by itself would break CodeQL on main. They must land together.

Recommended options for the maintainer:

1. Group codeql-action updates in .github/dependabot.yml (a groups: entry matching github/codeql-action*) so future bumps arrive as one PR, then recreate these; or
2. Combine ci(deps): bump github/codeql-action/analyze from 3.35.5 to 4.37.3 #262 + ci(deps): bump github/codeql-action/init from 3.35.5 to 4.37.3 #264 into a single branch (bump both init and analyze to e4fba86 / v4.37.3, and fix the # v3 → # v4 comments) and merge that.

Halting here per fail-fast; leaving the merge decision to a maintainer since it requires coordinating two PRs.

---

Generated by Claude Code