chore(deps): bump trufflesecurity/trufflehog from 3.96.0 to 3.97.1 - #425
Merged
KbWen merged 5 commits intoSep 7, 2026
Merged
Conversation
Bumps [trufflesecurity/trufflehog](https://github.com/trufflesecurity/trufflehog) from 3.96.0 to 3.97.1. - [Release notes](https://github.com/trufflesecurity/trufflehog/releases) - [Commits](trufflesecurity/trufflehog@6f3c981...20652fb) --- updated-dependencies: - dependency-name: trufflesecurity/trufflehog dependency-version: 3.97.1 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
…ions/trufflesecurity/trufflehog-3.97.1
Dependabot moved the wrapper action SHA to v3.97.1 but cannot touch a
`with:` input, so the `version:` image digest stayed on v3.96.0's. The
composed reference still resolved to the 3.96.0 scanner: the upgrade
was wrapper-only, and the go-git advisory this release carries would
not have landed.
Verified against ground truth rather than the PR body — GHCR resolves
tag 3.96.0 to exactly the digest this workflow pinned and 3.97.1 to
the new one; both are manifest lists over linux/amd64+arm64, so the
swap is shape-preserving, and `action.yml` at the new SHA still
composes `"${IMAGE}:${VERSION}"`, so the digest-pin construction holds.
Backlog #166 predicted this drift when the digest pin was chosen, and
the spec mitigated it with a human cadence that failed on first
contact: this PR sat open a week with the two halves naming different
releases and no check objected.
`test_ac5_trufflehog_wrapper_and_digest_agree_on_release` now compares
the release named by the `uses:` comment against the one named by the
digest comment. Mutation-verified — reverting only the digest half
fails 1 of 43, and that one.
It is not a revival of the comment-equality-as-provenance design #166
withdrew: it binds the automated bump path only, two hand edits still
pass it, and the docstring and AC-5 both say so.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
… Work Log Spec Index notes the AC-5 amendment; Ship History takes the new entry at the top and rotates `Ship-fix-trufflehog-lob-false-positive-171-2026-08-23` into `archive/ship-history-2026.md` at the 10-entry cap (verbatim, no relative links to re-depth). Sequence 169 -> 170. The Work Log moves to `archive/` with its chain entry. Two warns this branch briefly added were its own placeholders — `Checkpoint SHA: pending` against a `<git-sha or none>` contract, and a ship receipt written before ship happened. Both are recorded in the archived log with the experiment that reproduced each, including one hypothesis that was refuted rather than quietly dropped. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…rst mis-scoped The local full run finished after the ship record was written, so both the Ship History entry and the archived Work Log said no local claim was made. The numbers now exist and belong in the record: 947 passed, 1 skipped over `tests/ci/ tests/guard/ .agentcortex/tests/`, matching CI's 948 collected. Recorded with the mistake attached rather than only the result. The first local run used `pytest tests/`, which collects 687 — it silently omits `.agentcortex/tests/`, so a 686-pass figure looked like a full suite and was not one. Caught by taking the count from `--collect-only` instead of by eye, then running the missing 261. The two halves ran separately, and a ~3-minute window of the long run had three files temporarily reverted for the working-tree experiment; nothing failed, and they are not presented as one clean run. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
KbWen
deleted the
dependabot/github_actions/trufflesecurity/trufflehog-3.97.1
branch
September 7, 2026 14:49
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps trufflesecurity/trufflehog from 3.96.0 to 3.97.1.
Release notes
Sourced from trufflesecurity/trufflehog's releases.
... (truncated)
Commits
20652fbCarry GitHub App installation ID on repo units (#5215)3ab759fRefine SECURITY.md (#5216)2cdb97d[SCAN-101] s3 source accept persisted unit envelopes in UnmarshalSourceUnit (...4ec7749preallocate bindings capacity in dockerhub and groq, with unit tests (#5213)9610306Doubled timeout, as MongoDB secrets are repeatedly hitting this and failing t...9d3f5d1[SCAN-1020] neon scram pgx (#5217)925c1d0fix(detectors/docker): don't greedy match in keyPat (#5214)e12da3cdocs: add generic config-secret custom detector example (#5195)bcbcab2Fix GHEC with Data Residency (*.ghe.com) base URL (#4777)bc3a3aeUpdate module github.com/go-git/go-git/v5 to v5.19.2 [SECURITY] (#5196)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)