chore(deps): bump github/codeql-action/analyze from 4.37.0 to 4.37.8

[dependabot]

Bumps github/codeql-action/analyze from 4.37.0 to 4.37.8.

Release notes

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

v4.37.8

No user facing changes.

v4.37.7

• Update default CodeQL bundle version to 2.26.3. #4085

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

v4.37.4

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

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]

No user facing changes.

4.37.8 - 21 Aug 2026

No user facing changes.

4.37.7 - 13 Aug 2026

• Update default CodeQL bundle version to 2.26.3. #4085

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

... (truncated)

Commits

• db488dd Merge pull request #4102 from github/update-v4.37.8-9ee088e13
• 1845f5b Update changelog for v4.37.8
• 9ee088e Merge pull request #4080 from github/henrymercer/studious-giggle
• 1aef003 Address review feedback on overlay disk flags
• 508b83b Merge main into overlay minimum disk feature branch
• d97b342 Merge pull request #4098 from github/mbg/permission-error-as-configuration-error
• 47fa622 Make EACCES a ConfigurationError
• 45693cc Refactor ENOSPC check into isDiskConfigurationError function
• c2fd8f5 Merge pull request #4081 from github/mario-campos/version-cache-to-disk
• c56f48e Log unexpected conditions during caching CLI output
• Additional commits viewable in compare view

[devin-ai-integration]

Devin Review found 2 potential issues.

[devin-ai-integration]

🔴 CodeQL init and analyze pinned to different versions

analyze was bumped to v4.37.8 while init stays at v4.37.0. CodeQL requires both to run the same version, and test_codeql_action_steps_use_one_version_per_workflow asserts a single ref per workflow, so analysis and the contract test both break.

Prompt for agents

The analyze step was bumped to github/codeql-action/analyze@db488ddef3bf6cb639b32c2e9a7c0a7ea8271d28 (v4.37.8) but the init steps at lines 93 and 200 still use github/codeql-action/init@99df26d4f13ea111d4ec1a7dddef6063f76b97e9 (v4.37.0). CodeQL requires init and analyze to run the same version, and tests/test_codeql_pr_workflow_contract.py::test_codeql_action_steps_use_one_version_per_workflow asserts every codeql-action init/analyze/upload-sarif ref in a workflow resolves to a single SHA. Bump the two init steps in codeql-pr.yml to the matching v4.37.8 SHA so all refs agree.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

🔴 CodeQL analyze version split from init and upload-sarif

analyze was bumped to v4.37.8 while init and upload-sarif stay at v4.37.5. CodeQL requires init and analyze to match, and test_codeql_action_steps_use_one_version_per_workflow asserts a single ref per workflow, so both analysis and the contract test break.

Prompt for agents

The analyze step was bumped to github/codeql-action/analyze@db488ddef3bf6cb639b32c2e9a7c0a7ea8271d28 (v4.37.8) but init (line 93) and upload-sarif (line 134) still use d1ba80a13dd99fba24a470575428917156a28b43 (v4.37.5). CodeQL requires init and analyze to run the same version, and tests/test_codeql_pr_workflow_contract.py::test_codeql_action_steps_use_one_version_per_workflow asserts a single codeql-action SHA per workflow. Bump init and upload-sarif in scheduled-security-scan.yml to the matching v4.37.8 SHA.

---

Was this helpful? React with 👍 or 👎 to provide feedback.