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.37.1 to 4.37.3

Release notes

Sourced from github/codeql-action/init'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

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]

• 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

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

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

Updates github/codeql-action/analyze from 4.37.1 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

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]

• 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

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

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

Updates trufflesecurity/trufflehog from 3.95.9 to 3.96.0

Release notes

Sourced from trufflesecurity/trufflehog's releases.

v3.96.0

What's Changed

• [INS-355] Added Hashicorp vault token detector by @​MuneebUllahKhan222 in trufflesecurity/trufflehog#4819
• Tighten JiraToken v1 verification by @​shahzadhaider1 in trufflesecurity/trufflehog#5122
• [INT-718] Add TargetNotFoundError for targeted scan targets missing from the source by @​bill-rich in trufflesecurity/trufflehog#5123
• Fix GitLab project metadata cache and switch to LRU by @​kashifkhan0771 in trufflesecurity/trufflehog#4727
• Log analyze errors for Anthropic Analyzer by @​kashifkhan0771 in trufflesecurity/trufflehog#5120
• Add metrics for chunks and results by @​mcastorina in trufflesecurity/trufflehog#5128
• Update Cloudflare detectors for 2026+ prefixed credential formats (include upstream PR changes) by @​kashifkhan0771 in trufflesecurity/trufflehog#5111
• [INS-312] Duo API Secret Key Detector by @​MuneebUllahKhan222 in trufflesecurity/trufflehog#4771
• [Feature] Added SonarQube Cloud "Scoped Organization Token" Detector by @​nabeelalam in trufflesecurity/trufflehog#4739
• [INS-255] Updated datadog detector to set verificationError in case of a verification error by @​MuneebUllahKhan222 in trufflesecurity/trufflehog#4661
• Log analyze errors for Postgres analyzer by @​kashifkhan0771 in trufflesecurity/trufflehog#5131
• Log analyze errors for HuggingFace analyzer by @​kashifkhan0771 in trufflesecurity/trufflehog#5130
• Engine - Config.SourceManager doc by @​amanfcp in trufflesecurity/trufflehog#5002
• Update module github.com/go-git/go-git/v5 to v5.19.1 [SECURITY] by @​renovate[bot] in trufflesecurity/trufflehog#5034
• Retry git clone on transient network errors by @​shahzadhaider1 in trufflesecurity/trufflehog#5132
• Fix scan_all_installations Rejecting Org Member Personal Repos by @​shahzadhaider1 in trufflesecurity/trufflehog#5142
• updated detector to include underscore char by @​mattbrady-1 in trufflesecurity/trufflehog#5121
• [chore] Change job_id in metric to source_type by @​mcastorina in trufflesecurity/trufflehog#5149
• Posthog regex update by @​mattbrady-1 in trufflesecurity/trufflehog#5133
• fix(handlers): apk handler now doesnt check for apk extension since json-enumerator and other byte stream methods wouldnt have it by @​johannestaas-trufflesec in trufflesecurity/trufflehog#5151

New Contributors

• @​mattbrady-1 made their first contribution in trufflesecurity/trufflehog#5121

Full Changelog: trufflesecurity/trufflehog@v3.95.9...v3.96.0

Commits

• 6f3c981 fix(handlers): apk handler now doesnt check for apk extension since json-enum...
• 05a5832 fix(detectors/posthog): widen phx_ key body to {43,48} (#5133)
• a2ef4f5 [chore] Change job_id in metric to source_type (#5149)
• e74404a updated detector to include underscore char (#5121)
• 4d82f21 Fix scan_all_installations Rejecting Org Member Personal Repos (#5142)
• 38999f8 Retry git clone on transient network errors (#5132)
• 0eb1a81 Update module github.com/go-git/go-git/v5 to v5.19.1 [SECURITY] (#5034)
• ec20cb3 document Config.SourceManager (#5002)
• 4ecd7d5 Log analyze errors for HuggingFace analyzer (#5130)
• 1247638 Log analyze errors for Postgres analyzer (#5131)
• 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 changes before merge. Reviewed August 1, 2026, 9:42 PM ET / August 2, 2026, 01:42 UTC.

ClawSweeper review

What this changes

Updates the SHA-pinned CodeQL init/analyze actions to v4.37.3 and the TruffleHog action wrapper to v3.96.0 in the repository’s GitHub security workflows.

Merge readiness

⛔ Blocked until real behavior proof is added - 7 items remain

This PR is still necessary as a security-workflow dependency update, but it is not ready to merge: the TruffleHog action SHA is changed to v3.96.0 while the unchanged version input still explicitly requests v3.95.9. That repeats the prior review blocker at the same head; no current-main implementation or safe replacement owns the update.

Priority: P2
Reviewed head: ee1de7b311129aaafe76aca753214d584a09ab9c

Review scores

Measure	Result	What it means
Overall readiness	🧂 unranked krab (1/6)	The grouped SHA-pinned update is small, but the unresolved scanner-version mismatch and missing live workflow proof keep it below merge-ready quality.
Proof confidence	🧂 unranked krab (1/6)	Needs real behavior proof before merge: No contributor-supplied after-fix run, redacted log, or artifact shows that this workflow configuration invokes the intended scanner version; passing CI is supplemental evidence only. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.
Patch quality	🦪 silver shellfish (2/6)	Security review found an item that needs attention.

Verification

Check	Result	Evidence
Real behavior	Needs proof	Needs real behavior proof before merge: No contributor-supplied after-fix run, redacted log, or artifact shows that this workflow configuration invokes the intended scanner version; passing CI is supplemental evidence only. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.
Evidence reviewed	5 items	Current main remains unupdated: Current main still uses the prior CodeQL v4 SHA and the TruffleHog v3.95.9 SHA, so the proposed updates are not already implemented or released. Version mismatch in the proposed workflow: The PR updates the TruffleHog action pin to the SHA annotated v3.96.0 but leaves its explicit version: "3.95.9" input unchanged, so the job remains configured to request the old scanner binary. Prior finding is still unfixed: The current head is the same SHA reviewed previously, and the earlier review already identified this exact wrapper-versus-input mismatch; no new commit resolves it.
Findings	1 actionable finding	[P2] Align the TruffleHog binary version with the action pin
Security	Needs attention	TruffleHog input selects an older scanner: The v3.96.0 action wrapper remains configured with version: "3.95.9", which can leave secret scanning on an older binary despite the dependency update.

How this fits together

Clawpatch uses GitHub Actions workflows to run CodeQL static analysis and TruffleHog secret scanning on repository changes. The workflows pin third-party action code by commit SHA and pass configuration, including the scanner binary version, before publishing security check results.

flowchart LR
  Changes[Repository changes] --> CodeQL[CodeQL workflow]
  Changes --> SecretScan[Secret-scan workflow]
  CodeQL --> CodeQLAction[SHA-pinned CodeQL actions]
  SecretScan --> TruffleAction[SHA-pinned TruffleHog action]
  TruffleAction --> ScannerVersion[Explicit scanner version]
  CodeQLAction --> Results[Security check results]
  ScannerVersion --> Results

Loading

Before merge

• Align the TruffleHog binary version with the action pin (P2) - The action pin changes to the SHA annotated v3.96.0, but the unchanged version input still explicitly requests 3.95.9. The job can therefore continue downloading the old scanner binary, leaving this TruffleHog update incomplete. This is the still-unfixed blocker from the earlier review at the same head.
• Resolve security concern: TruffleHog input selects an older scanner - The v3.96.0 action wrapper remains configured with version: "3.95.9", which can leave secret scanning on an older binary despite the dependency update.
• Resolve merge risk (P1) - Merging as written can leave verified-secret scanning configured to download TruffleHog 3.95.9 despite the updated v3.96.0 wrapper pin, creating misleading dependency-update coverage in a security boundary.
• Resolve merge risk (P1) - No after-fix live workflow evidence demonstrates which TruffleHog scanner binary the configured action actually invokes.
• Complete next step (P2) - A one-line, source-proven workflow repair is available, although an external contributor must still supply real after-fix workflow proof before the PR can merge.
• Improve patch quality - Align the TruffleHog version input with the pinned v3.96.0 action or restore the old action pin with an explicit rationale.
• Improve patch quality - Post a redacted successful secret-scan log or workflow artifact that identifies the invoked scanner version; updating the PR body should trigger a fresh review, or a maintainer can comment @clawsweeper re-review.

Findings

• [P2] Align the TruffleHog binary version with the action pin — .github/workflows/secret-scan.yml:50-55
• [medium] TruffleHog input selects an older scanner — .github/workflows/secret-scan.yml:55

Agent review details

Security

Needs attention: The SHA-pinned workflow update is narrow, but the stale TruffleHog scanner input can prevent the intended secret-scanner upgrade from taking effect.

Review metrics

Metric	Value	Why it matters
Workflow surface	2 files, 3 action pins updated	Every changed line controls CI security tooling rather than application runtime behavior.
Unaligned scanner setting	1 explicit version input remains at 3.95.9	This input can keep the secret scanner behind the action-wrapper release named by the PR.

Merge-risk options

Maintainer options:

1. Align the scanner and wrapper (recommended)
   Update the explicit TruffleHog version input to 3.96.0, retain the SHA-pinned action update, and verify the resulting secret-scan run.
2. Retain the old scanner deliberately
   Revert the TruffleHog wrapper pin if the repository intentionally needs scanner v3.95.9 and document that exception in the PR discussion.
3. Pause the grouped update
   Close or pause this grouped dependency update if a verified v3.96.0 secret-scan run cannot be supplied and the version split is not intentional.

Copy recommended automerge instruction

@clawsweeper automerge

Special instructions:
Align the explicit TruffleHog scanner version with the pinned v3.96.0 action in `.github/workflows/secret-scan.yml`, retain all other workflow behavior, and validate the resulting workflow configuration.

Technical review

Best possible solution:

Keep the SHA-pinned action upgrade, align the explicit TruffleHog scanner input to 3.96.0, and attach redacted evidence from a successful secret-scan run that identifies the scanner version before merge.

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

Yes. Current source and the PR diff show a reproducible configuration mismatch: the wrapper pin is annotated v3.96.0 while the explicit scanner input remains 3.95.9.

Is this the best way to solve the issue?

No. Updating only the wrapper SHA is not the best solution when the workflow also selects a scanner binary version; align both to v3.96.0 unless maintainers intentionally choose the older scanner.

Full review comments:

• [P2] Align the TruffleHog binary version with the action pin — .github/workflows/secret-scan.yml:50-55
  The action pin changes to the SHA annotated v3.96.0, but the unchanged version input still explicitly requests 3.95.9. The job can therefore continue downloading the old scanner binary, leaving this TruffleHog update incomplete. This is the still-unfixed blocker from the earlier review at the same head.
  Confidence: 0.99

Overall correctness: patch is incorrect
Overall confidence: 0.99

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 4a5028c27f01.

Labels

Label justifications:

• P2: The bounded workflow defect can leave a planned security-scanner update only partially applied, but it has limited direct user-runtime blast radius.
• merge-risk: 🚨 security-boundary: This PR changes the repository’s CodeQL and secret-scanning action pins, and the scanner-version mismatch affects the effective security-tool version.
• rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🧂 unranked krab and patch quality is 🦪 silver shellfish.
• status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask. Needs real behavior proof before merge: No contributor-supplied after-fix run, redacted log, or artifact shows that this workflow configuration invokes the intended scanner version; passing CI is supplemental evidence only. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.

Evidence

Security concerns:

• [medium] TruffleHog input selects an older scanner — .github/workflows/secret-scan.yml:55
  The v3.96.0 action wrapper remains configured with version: "3.95.9", which can leave secret scanning on an older binary despite the dependency update.
  Confidence: 0.99

Acceptance criteria:

• [P1] Inspect .github/workflows/secret-scan.yml to confirm the TruffleHog SHA annotation and explicit version input both identify v3.96.0.
• [P1] Run applicable read-only workflow/configuration validation in the repair environment.
• [P1] Capture a redacted successful secret-scan workflow run or log showing the invoked TruffleHog version before merge.

What I checked:

• Current main remains unupdated: Current main still uses the prior CodeQL v4 SHA and the TruffleHog v3.95.9 SHA, so the proposed updates are not already implemented or released. (.github/workflows/secret-scan.yml:50, 4a5028c27f01)
• Version mismatch in the proposed workflow: The PR updates the TruffleHog action pin to the SHA annotated v3.96.0 but leaves its explicit version: "3.95.9" input unchanged, so the job remains configured to request the old scanner binary. (.github/workflows/secret-scan.yml:55, ee1de7b31112)
• Prior finding is still unfixed: The current head is the same SHA reviewed previously, and the earlier review already identified this exact wrapper-versus-input mismatch; no new commit resolves it. (.github/workflows/secret-scan.yml:55, ee1de7b31112)
• Workflow provenance: The current CodeQL and secret-scan workflow configuration was introduced in the v0.7.1 release commit, making that release-tree author the strongest available routing candidate for the current workflow design. (.github/workflows/secret-scan.yml:50, f6e00010cc2a)
• Action-line ownership: Blame attributes the current CodeQL and TruffleHog pins and scanner input to the release-tree workflow introduction. (.github/workflows/secret-scan.yml:50, f6e00010cc2a)

Likely related people:

• Peter Steinberger: The v0.7.1 release-tree commit introduced both affected security workflow files, and blame attributes the current action pins and TruffleHog input to that commit. (role: workflow introducer and adjacent owner; confidence: high; commits: f6e00010cc2a; files: .github/workflows/codeql.yml, .github/workflows/secret-scan.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-07-31T23:34:10.567Z sha ee1de7b :: needs changes before merge. :: [P2] Align the TruffleHog binary version with the action pin
• reviewed 2026-08-01T07:10:56.585Z sha ee1de7b :: needs changes before merge. :: [P2] Align the TruffleHog binary version with the action pin
• reviewed 2026-08-01T09:34:41.661Z sha ee1de7b :: found issues before merge. :: [P2] Align the TruffleHog binary version with the action pin
• reviewed 2026-08-01T10:56:23.580Z sha ee1de7b :: needs changes before merge. :: [P2] Align the TruffleHog binary version with the action pin
• reviewed 2026-08-01T12:44:30.715Z sha ee1de7b :: needs changes before merge. :: [P2] Align the TruffleHog binary version with the action pin
• reviewed 2026-08-01T14:27:25.983Z sha ee1de7b :: needs changes before merge. :: [P2] Align the TruffleHog binary version with the action pin
• reviewed 2026-08-01T20:13:23.432Z sha ee1de7b :: found issues before merge. :: [P2] Align the TruffleHog binary version with the action pin
• reviewed 2026-08-01T22:36:37.435Z sha ee1de7b :: needs changes before merge. :: [P2] Align the TruffleHog binary version with the action pin

[steipete]

Dependency triage outcome: recommend CLOSE as superseded by #174.

This branch updates CodeQL only to 4.37.3, while 4.37.4 is current. It also moves the TruffleHog action wrapper to 3.96.0 but leaves the workflow's explicit scanner input at 3.95.9, so the scanner itself does not receive the intended update.

#174 updates the complete toolchain and both sides of the TruffleHog pin, with a frozen install, empty pnpm outdated result, 894 passing tests, production build, real built-CLI init/map/status proof, actionlint, and hosted CodeQL/secret-scan checks.

[clawsweeper]

ClawSweeper status: review started.

I am starting a fresh review of this pull request: build(deps): bump the github-actions group with 3 updates This is item 1/1 in the current shard. Shard 0/1.

This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking.

Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted.

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.