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

[dependabot]

Bumps the github-actions group with 3 updates: github/codeql-action/init, github/codeql-action/analyze and trufflesecurity/trufflehog.

Updates github/codeql-action/init from 4.36.2 to 4.36.3

Release notes

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

v4.36.3

No user facing changes.

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.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
• Update default CodeQL bundle version to 2.25.3. #3865

4.35.2 - 15 Apr 2026

• 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

... (truncated)

Commits

• 54f647b Merge pull request #3984 from github/update-v4.36.3-1f34ec164
• e78819e Trigger checks
• 2c9d3d6 Update changelog for v4.36.3
• 1f34ec1 Merge pull request #3983 from github/mbg/repo-props/ff-for-config-file-prop
• d5f0145 Log when repository property has a value but is ignored
• f27f563 Add test for when the FF is off
• 0025d0f Use FF
• f7fa18f Add FF for config file repo property
• 628fc3f Merge pull request #3979 from github/henrymercer/overlay-db-cleanup-size-tele...
• 9cfb67b Add clarifying comments
• Additional commits viewable in compare view

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

Release notes

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

v4.36.3

No user facing changes.

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.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
• Update default CodeQL bundle version to 2.25.3. #3865

4.35.2 - 15 Apr 2026

• 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

... (truncated)

Commits

• 54f647b Merge pull request #3984 from github/update-v4.36.3-1f34ec164
• e78819e Trigger checks
• 2c9d3d6 Update changelog for v4.36.3
• 1f34ec1 Merge pull request #3983 from github/mbg/repo-props/ff-for-config-file-prop
• d5f0145 Log when repository property has a value but is ignored
• f27f563 Add test for when the FF is off
• 0025d0f Use FF
• f7fa18f Add FF for config file repo property
• 628fc3f Merge pull request #3979 from github/henrymercer/overlay-db-cleanup-size-tele...
• 9cfb67b Add clarifying comments
• Additional commits viewable in compare view

Updates trufflesecurity/trufflehog from 3.95.6 to 3.95.8

Release notes

Sourced from trufflesecurity/trufflehog's releases.

v3.95.8

What's Changed

• removed "unauthorized" as exception for rotated graphana secrets by @​jordanTunstill in trufflesecurity/trufflehog#5068
• fix(azuresastoken): match SAS tokens regardless of parameter order by @​genisis0x in trufflesecurity/trufflehog#5043
• Add prometheus metrics for engine channels and workers by @​mcastorina in trufflesecurity/trufflehog#5095
• [INS-465] Skip unverified JWT Detector results when feature flag is enabled by @​MuneebUllahKhan222 in trufflesecurity/trufflehog#5072
• [INS-334] Octopus Deploy detector by @​MuneebUllahKhan222 in trufflesecurity/trufflehog#4787
• Fix Syntax error in feature.go by @​MuneebUllahKhan222 in trufflesecurity/trufflehog#5109
• Include encoded resume info instead of clobbering it by @​bill-rich in trufflesecurity/trufflehog#5110

Full Changelog: trufflesecurity/trufflehog@v3.95.7...v3.95.8

v3.95.7

What's Changed

• fix(sources/filesystem): order resume comparison by path component by @​genisis0x in trufflesecurity/trufflehog#5041
• test(handlers): point APK test fixture at trufflehog-test-assets by @​amanfcp in trufflesecurity/trufflehog#5053
• fixed regex typo that was causing conf uuid's to be surfaced as non-live atlassian secrets. by @​jordanTunstill in trufflesecurity/trufflehog#5029
• Fix GitHub App cross-org member enumeration using per-installation tokens by @​dustin-decker in trufflesecurity/trufflehog#4774
• fix: add git worktree support in PrepareRepo by @​andoniaf in trufflesecurity/trufflehog#4690
• [INS-406] Braintrust detector by @​MuneebUllahKhan222 in trufflesecurity/trufflehog#4826
• huggingface: add bucket scanning by @​julien-c in trufflesecurity/trufflehog#5017
• Skip reverification results during deduplication by @​mcastorina in trufflesecurity/trufflehog#5069
• chore(renovate): bump shared config to v1.0.3 by @​bryanbeverly in trufflesecurity/trufflehog#5044
• Add scan_all_installations option for multi-org GitHub App scanning by @​dustin-decker in trufflesecurity/trufflehog#4775
• Expose SecretParts in the JSON output by @​bradlarsen in trufflesecurity/trufflehog#5073
• [INS-497] Add Pganalyze Read Key Detector by @​MuneebUllahKhan222 in trufflesecurity/trufflehog#4993
• [INS-197] Add redhatpyxis api key detector by @​MuneebUllahKhan222 in trufflesecurity/trufflehog#4995
• [INS-407] Fixed AWS detector producing non deterministic output by @​MuneebUllahKhan222 in trufflesecurity/trufflehog#4836

New Contributors

• @​genisis0x made their first contribution in trufflesecurity/trufflehog#5041
• @​andoniaf made their first contribution in trufflesecurity/trufflehog#4690
• @​julien-c made their first contribution in trufflesecurity/trufflehog#5017

Full Changelog: trufflesecurity/trufflehog@v3.95.6...v3.95.7

Commits

• 00155c9 Include encoded resume info instead of clobbering it (#5110)
• 4d3a66f fixed syntax error (#5109)
• 797f02b [INS-334] Octopus Deploy detector (#4787)
• 7f04a89 [INS-465] Skip unverified JWT Detector results when feature flag is enabled (...
• 459d5a7 Add prometheus metrics for engine channels and workers (#5095)
• f38f8f7 fix(azuresastoken): match SAS tokens regardless of parameter order (#5043)
• 6261f5c removed "unauthorized" as exception for rotated graphana secrets (#5068)
• f446421 [INS-407] Fixed AWS detector producing non deterministic output (#4836)
• 885fa2d [INS-197] Add redhatpyxis api key detector (#4995)
• c09d726 [INS-497] Add Pganalyze Read Key Detector (#4993)
• 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 6, 2026, 12:12 PM ET / 16:12 UTC.

Summary
Dependabot updates the GitHub Actions group by bumping CodeQL init/analyze from v4.36.2 to v4.36.3 and TruffleHog from v3.95.6 to v3.95.8 in two workflow files.

Reproducibility: not applicable. this is a dependency maintenance PR, not a bug report. The relevant validation is that CI, CodeQL, and secret-scan check runs passed on the updated PR head.

Review metrics: 3 noteworthy metrics.

• Workflow files changed: 2 modified, 0 added, 0 removed. The patch is confined to CI/security workflow dependency references.
• Action refs bumped: 3 updates. Both CodeQL steps move to the same pinned upstream commit and TruffleHog moves by patch releases.
• Observed PR checks: 6 successful, 0 failed. The touched CodeQL and secret-scan workflows executed successfully on the PR head.

Merge readiness
Overall: 🐚 platinum hermit
Proof: 🌊 off-meta tidepool
Patch quality: 🐚 platinum hermit
Result: ready for maintainer review.

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

Rank-up moves:

• none.

Next step before merge

• [P2] No repair lane is needed because the PR has no concrete patch defect; it should proceed through normal review/merge gating.

Security
Cleared: The diff only advances existing workflow action refs, and upstream release notes plus successful CodeQL/secret-scan runs show no concrete supply-chain or security regression.

Review details

Best possible solution:

Merge through the normal Dependabot and security-codeowner path once maintainers are satisfied with the successful workflow checks.

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

Not applicable; this is a dependency maintenance PR, not a bug report. The relevant validation is that CI, CodeQL, and secret-scan check runs passed on the updated PR head.

Is this the best way to solve the issue?

Yes; for this Dependabot PR, changing only the existing action refs is the narrow maintainable solution, and no duplicate or already-implemented path was found on current main.

AGENTS.md: found and applied where relevant.

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

Label changes

Label changes:

• add P3: This is a low-risk maintenance dependency update to CI/security workflow action references with passing checks.
• 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: Dependabot bot PRs do not need contributor real-behavior proof; the workflow check runs are the relevant validation evidence here.

Label justifications:

• P3: This is a low-risk maintenance dependency update to CI/security workflow action references with passing checks.
• 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: Dependabot bot PRs do not need contributor real-behavior proof; the workflow check runs are the relevant validation evidence here.

Evidence reviewed

What I checked:

• PR diff is narrowly scoped: The diff changes only three action references across the CodeQL and secret-scan workflows: two CodeQL SHA pins and one TruffleHog patch tag. (.github/workflows/codeql.yml:69, 19a1496837f6)
• Current main still has prior refs: Current main uses github/codeql-action/init and analyze at 8aad20d150bbac5944a9f9d289da16a4b0d87c1e, so the proposed CodeQL bump is not already implemented on main. (.github/workflows/codeql.yml:69, 140b0ac6ac19)
• Current main still has prior TruffleHog tag: Current main uses trufflesecurity/trufflehog@v3.95.6, so the proposed v3.95.8 bump is not already implemented on main. (.github/workflows/secret-scan.yml:49, 140b0ac6ac19)
• Workflow checks passed on PR head: The PR head had successful CI, CodeQL, and secret-scan check runs, including Analyze (actions), Analyze (typescript), and Scan for verified secrets. (19a1496837f6)
• Upstream CodeQL release note checked: The CodeQL v4.36.3 release says there are no user-facing changes.
• Upstream TruffleHog release notes checked: The TruffleHog v3.95.7 and v3.95.8 release notes list detector and scanning fixes/additions; no repository-specific incompatible workflow input change was identified.

Likely related people:

• openclaw/openclaw-secops: The repository CODEOWNERS file assigns /.github/workflows/ and other security automation surfaces to this team. (role: CODEOWNERS route; confidence: high; files: .github/CODEOWNERS, .github/workflows/codeql.yml, .github/workflows/secret-scan.yml)
• Peter Steinberger: The CodeQL and secret-scan workflow bodies appear to date to the v0.7.0 release commit authored by Peter Steinberger. (role: introduced workflow surface; confidence: medium; commits: 0cd24d07a262; files: .github/workflows/codeql.yml, .github/workflows/secret-scan.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.