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

[dependabot]

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

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

Release notes

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

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

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

4.36.1 - 02 Jun 2026

No user facing changes.

... (truncated)

Commits

• f205ea1 Merge pull request #4053 from github/update-v4.37.4-9130ce0f7
• e40d079 Update changelog for v4.37.4
• 9130ce0 Merge pull request #4051 from github/update-bundle/codeql-bundle-v2.26.2
• c62d824 Add changelog note
• da0c190 Update default bundle to codeql-bundle-v2.26.2
• 18420e3 Merge pull request #4043 from github/mbg/ts/changelog
• 7e8d897 Merge pull request #4046 from github/mbg/repo-prop/code-quality
• 2d4c474 Log !analysisKindSupported case
• 98c05a1 Fix argument validation in rollback-changelog.ts
• 8289a49 Ignore repository property for unsupported analysis kinds
• Additional commits viewable in compare view

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

Release notes

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

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

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

4.36.1 - 02 Jun 2026

No user facing changes.

... (truncated)

Commits

• f205ea1 Merge pull request #4053 from github/update-v4.37.4-9130ce0f7
• e40d079 Update changelog for v4.37.4
• 9130ce0 Merge pull request #4051 from github/update-bundle/codeql-bundle-v2.26.2
• c62d824 Add changelog note
• da0c190 Update default bundle to codeql-bundle-v2.26.2
• 18420e3 Merge pull request #4043 from github/mbg/ts/changelog
• 7e8d897 Merge pull request #4046 from github/mbg/repo-prop/code-quality
• 2d4c474 Log !analysisKindSupported case
• 98c05a1 Fix argument validation in rollback-changelog.ts
• 8289a49 Ignore repository property for unsupported analysis kinds
• 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 13, 2026, 4:33 PM ET / 20:33 UTC.

ClawSweeper review

What this changes

Updates the immutable pins for the CodeQL initialization and analysis actions from v4.37.3 to v4.37.4.

Merge readiness

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

Keep open for maintainer validation: this updates executable CodeQL action pins in a security-analysis workflow, but the supplied review context does not establish an enabled after-change workflow run and local read-only inspection could not start.

Priority: P3
Reviewed head: 191d18d3e3b7b2836d7bf7b91e84eb89e6e73eba
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	4 items	Submitted workflow diff: The PR changes only the two CodeQL action SHA pins, from e4fba868… to f205ea1…, in the conditional initialization and analysis steps. Dependency contract is directly in scope: The changed workflow directly executes github/codeql-action/init and github/codeql-action/analyze, so the upstream CodeQL Action revision is the relevant dependency contract. Prior review continuity: The latest completed review found no code finding but recorded that CodeQL is conditional and available checks did not demonstrate initialization and analysis at the new pins.
Findings	None	None.
Security	Needs attention	Validate the updated CodeQL action revisions: Both changed pins select code executed by the repository’s CodeQL workflow; confirm the conditional workflow runs successfully at these revisions before accepting the update.

How this fits together

The repository’s CodeQL workflow conditionally initializes and runs GitHub’s security scanner, then uploads analysis results to GitHub security reporting. This PR changes the exact third-party action revision executed in those steps.

flowchart LR
  A[Workflow trigger] --> B[CodeQL enabled check]
  B --> C[CodeQL initialization]
  C --> D[JavaScript and TypeScript analysis]
  D --> E[Security analysis results]
  F[Updated immutable action pins] --> C
  F --> D

Loading

Decision needed

Question	Recommendation
Should the repository accept the CodeQL v4.37.4 action revisions after an enabled workflow run confirms both pinned steps execute successfully?	Validate the enabled workflow: Run CodeQL with its repository enablement condition on this head and merge only after both updated action steps complete successfully.

Why: This update changes executable third-party automation in the security-analysis path, and the available context does not provide convincing after-change execution evidence for its conditional workflow path.

Before merge

• Resolve security concern: Validate the updated CodeQL action revisions - Both changed pins select code executed by the repository’s CodeQL workflow; confirm the conditional workflow runs successfully at these revisions before accepting the update.
• Resolve merge risk (P1) - Merging changes the externally supplied code executed by the repository’s security-analysis automation; the supplied evidence does not prove an enabled CodeQL run exercised both new pins.
• Resolve merge risk (P1) - The review sandbox could not execute even read-only checkout commands, so current-main equivalence, workflow permissions, local policy, and file history remain unverified.
• Complete next step (P2) - A maintainer must decide whether an enabled CodeQL run is required before accepting executable third-party security automation changes; there is no narrow code repair to dispatch.
• Improve patch quality - Resolve the security review concern or explain why the changed path is safe.

Findings

• [medium] Validate the updated CodeQL action revisions — .github/workflows/codeql.yml:41

Agent review details

Security

Needs attention: The immutable SHA update changes third-party code executed in the security-analysis workflow and needs an enabled-run verification before merge.

Review metrics

Metric	Value	Why it matters
Workflow action changes	2 action pins updated in 1 workflow file	Both updates affect executable CodeQL security-analysis steps.

Merge-risk options

Maintainer options:

1. Validate the new action pins (recommended)
   Run the conditional CodeQL workflow on this head and verify initialization, analysis, and result upload before merging.
2. Accept upstream-release risk
   Merge the official immutable SHA update without repository-specific enabled-run evidence, accepting the remaining security-automation uncertainty.

Technical review

Best possible solution:

Run the CodeQL workflow with its enabling condition on this exact head, confirm initialization, analysis, and result upload succeed at the two new immutable pins, then merge the focused dependency update.

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

Not applicable as a bug reproduction; the relevant verification is an enabled CodeQL execution of this workflow revision, which is not established by the supplied evidence.

Is this the best way to solve the issue?

Yes, conditionally: updating official immutable action pins is the narrow maintainable path, provided the enabled workflow run validates the new revisions before merge.

AGENTS.md: unclear because the file could not be read completely.

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

Labels

Label justifications:

• P3: This is a narrow routine dependency update, with no demonstrated user-facing regression.
• merge-risk: 🚨 security-boundary: The changed immutable pins select third-party code executed by the repository security-analysis workflow.
• merge-risk: 🚨 automation: The patch changes the behavior and executable revisions of CodeQL CI automation.
• rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🌊 off-meta tidepool and patch quality is 🧂 unranked krab.
• status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action. Not applicable: Real behavior proof is not required for maintainer- or bot-authored pull requests.

Evidence

Security concerns:

• [medium] Validate the updated CodeQL action revisions — .github/workflows/codeql.yml:41
  Both changed pins select code executed by the repository’s CodeQL workflow; confirm the conditional workflow runs successfully at these revisions before accepting the update.
  Confidence: 0.86

What I checked:

• Submitted workflow diff: The PR changes only the two CodeQL action SHA pins, from e4fba868… to f205ea1…, in the conditional initialization and analysis steps. (.github/workflows/codeql.yml:41, 191d18d3e3b7)
• Dependency contract is directly in scope: The changed workflow directly executes github/codeql-action/init and github/codeql-action/analyze, so the upstream CodeQL Action revision is the relevant dependency contract. (.github/workflows/codeql.yml:41, 191d18d3e3b7)
• Prior review continuity: The latest completed review found no code finding but recorded that CodeQL is conditional and available checks did not demonstrate initialization and analysis at the new pins. (.github/workflows/codeql.yml:41, 191d18d3e3b7)
• Local inspection failure: The required read-only repository search could not execute because the sandbox failed during bwrap network setup; no local files, AGENTS.md policy, or git history were inspected.

Likely related people:

• steipete: The provided timeline shows subscription to this PR, but repository-history ownership could not be established because local read-only inspection failed. (role: interested project participant; confidence: low; 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 (23 earlier review cycles; latest 8 shown)

• reviewed 2026-08-05T18:37:03.222Z sha 191d18d :: needs maintainer review before merge. :: none
• reviewed 2026-08-05T18:40:36.426Z sha 191d18d :: needs maintainer review before merge. :: none
• reviewed 2026-08-05T22:41:35.562Z sha 191d18d :: needs maintainer review before merge. :: none
• reviewed 2026-08-06T23:36:57.936Z sha 191d18d :: needs maintainer review before merge. :: none
• reviewed 2026-08-07T18:41:36.240Z sha 191d18d :: needs maintainer review before merge. :: none
• reviewed 2026-08-10T18:49:08.942Z sha 191d18d :: needs maintainer review before merge. :: none
• reviewed 2026-08-11T18:41:57.302Z sha 191d18d :: needs maintainer review before merge. :: none
• reviewed 2026-08-12T18:40:33.078Z sha 191d18d :: needs maintainer review before merge. :: none