build(deps): bump the github-actions group with 2 updates

[dependabot]

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

Updates github/codeql-action/init from 9e3211c9a3b9311dfe05da2ed48eea3386f042dd to 5595ccaf912efad79be6eef63a5619ff05969be3

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

... (truncated)

Commits

• See full diff in compare view

Updates github/codeql-action/analyze from 9e3211c9a3b9311dfe05da2ed48eea3386f042dd to 5595ccaf912efad79be6eef63a5619ff05969be3

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

... (truncated)

Commits

• See full diff 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]

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

[clawsweeper]

Codex review: needs maintainer review before merge. Reviewed August 10, 2026, 12:16 PM ET / 16:16 UTC.

ClawSweeper review

What this changes

The PR updates the immutable GitHub CodeQL action revisions for the workflow’s initialization and analysis steps.

Merge readiness

⚠️ Ready for maintainer review - 2 items remain

This is a clean, narrowly scoped Dependabot update with completed CI, but it changes a security-owned workflow and should remain open for the required code-owner review before merge.

Priority: P3
Reviewed head: 5e267486f4b6beeab4eaec2ff0beca7dfdce5e7b

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	A small, conventional pinned-action update with successful validation and no code-level finding.
Proof confidence	🌊 off-meta tidepool	Not applicable: This Dependabot-authored CI-only update is evidenced by successful workflow checks and does not require 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 Dependabot-authored CI-only update is evidenced by successful workflow checks and does not require contributor runtime proof.
Evidence reviewed	5 items	Minimal workflow diff: The PR changes exactly two full-SHA CodeQL action references and leaves workflow inputs, matrix configuration, and permissions unchanged. Security workflow boundary: The workflow has read-only contents access and security-events write access, and the changed init/analyze steps consume the TypeScript and Actions CodeQL profiles. Configured Dependabot scope: Repository policy explicitly groups all GitHub Actions dependencies for weekly Dependabot updates.
Findings	None	None.
Security	None	None.

How this fits together

The CodeQL workflow runs on repository events, initializes analysis for TypeScript and GitHub Actions code, then uploads security results. This PR changes only the pinned upstream revision used by those two action steps.

flowchart LR
A[Repository events] --> B[CodeQL workflow]
B --> C[Initialize analysis]
C --> D[Analyze two language profiles]
D --> E[Upload security results]

Loading

Before merge

• Resolve merge risk (P1) - Merging advances third-party code executed by a workflow with security-events write access; the references remain immutable SHA pins, but the security workflow’s code owner should verify the intended upstream revision.
• Complete next step (P2) - No repair is needed; retain this PR for normal security-workflow approval and merge handling.

Agent review details

Security

None.

Review metrics

Metric	Value	Why it matters
Workflow action pins	2 changed in 1 workflow	Both CodeQL stages move together to the same immutable upstream revision.

Merge-risk options

Maintainer options:

1. Complete security workflow review (recommended)
   Have the workflow code owner verify the new pinned CodeQL revision, then merge the already-successful narrow update.

Technical review

Best possible solution:

Retain the immutable SHA pins and merge after the security-workflow code owner confirms the intended CodeQL action revision.

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

Not applicable: this is a CI action revision update, and the proposed workflow completed its CodeQL and test checks successfully.

Is this the best way to solve the issue?

Yes: updating only the existing full-SHA pins is the narrowest maintainable way to adopt the upstream CodeQL action revision.

AGENTS.md: found and applied where relevant.

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

Labels

Label changes:

• add P3: This is a routine, narrowly scoped CI dependency update with successful checks.
• add merge-risk: 🚨 security-boundary: The updated third-party actions run in a workflow permitted to upload security events.
• add merge-risk: 🚨 automation: The patch changes the action revisions executed by the repository’s CodeQL automation.
• 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 Dependabot-authored CI-only update is evidenced by successful workflow checks and does not require contributor runtime proof.

Label justifications:

• P3: This is a routine, narrowly scoped CI dependency update with successful checks.
• merge-risk: 🚨 automation: The patch changes the action revisions executed by the repository’s CodeQL automation.
• merge-risk: 🚨 security-boundary: The updated third-party actions run in a workflow permitted to upload security events.
• 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 Dependabot-authored CI-only update is evidenced by successful workflow checks and does not require contributor runtime proof.

Evidence

What I checked:

• Minimal workflow diff: The PR changes exactly two full-SHA CodeQL action references and leaves workflow inputs, matrix configuration, and permissions unchanged. (.github/workflows/codeql.yml:69, 5e267486f4b6)
• Security workflow boundary: The workflow has read-only contents access and security-events write access, and the changed init/analyze steps consume the TypeScript and Actions CodeQL profiles. (.github/workflows/codeql.yml:41, 1571f3143be5)
• Configured Dependabot scope: Repository policy explicitly groups all GitHub Actions dependencies for weekly Dependabot updates. (.github/dependabot.yml:23, 1571f3143be5)
• Workflow ownership and history: The changed workflow is owned by the secops team; history shows Vincent Koc introduced the hardening workflows and Peter Steinberger most recently refreshed tooling/actions in this area. (.github/CODEOWNERS:13, e4a60f499475)
• PR validation: The supplied PR checks show successful TypeScript and Actions CodeQL analyses, tests, and verified-secret scans on the proposed head. (.github/workflows/codeql.yml:76, 5e267486f4b6)

Likely related people:

• Vincent Koc: Introduced the repository hardening workflows that include this CodeQL surface. (role: introduced security workflow; confidence: high; commits: e4a60f499475; files: .github/workflows/codeql.yml, .github/CODEOWNERS)
• Peter Steinberger: Authored the most recent main-branch toolchain and Actions refresh touching this workflow’s history. (role: recent area contributor; confidence: high; commits: 439d9e42b891; files: .github/workflows/codeql.yml)

Rank-up moves

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

• Obtain the required security-workflow code-owner approval.

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.