chore(deps): bump the actions group across 1 directory with 3 updates - #12
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps the actions group with 3 updates in the / directory: [actions/cache](https://github.com/actions/cache), [github/codeql-action](https://github.com/github/codeql-action) and [trufflesecurity/trufflehog](https://github.com/trufflesecurity/trufflehog). Updates `actions/cache` from 5.0.2 to 5.0.3 - [Release notes](https://github.com/actions/cache/releases) - [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md) - [Commits](actions/cache@8b402f5...cdf6c1f) Updates `github/codeql-action` from 4.31.11 to 4.32.1 - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](github/codeql-action@19b2f06...6bc82e0) Updates `trufflesecurity/trufflehog` from 3.92.5 to 3.93.0 - [Release notes](https://github.com/trufflesecurity/trufflehog/releases) - [Commits](trufflesecurity/trufflehog@116e717...7f4e37d) --- updated-dependencies: - dependency-name: actions/cache dependency-version: 5.0.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: actions - dependency-name: github/codeql-action dependency-version: 4.32.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: actions - dependency-name: trufflesecurity/trufflehog dependency-version: 3.93.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: actions ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/github_actions/actions-6d858dd6bd
branch
from
February 9, 2026 15:08
bf96a93 to
a3be03b
Compare
Contributor
Author
|
Looks like these dependencies are updatable in another way, so this is no longer needed. |
dependabot
Bot
deleted the
dependabot/github_actions/actions-6d858dd6bd
branch
February 13, 2026 13:27
hyperpolymath
added a commit
that referenced
this pull request
Apr 18, 2026
Closes Dependabot alerts #12 + #13 on hyperpolymath/standards: - GHSA-xgp8-3hg3-c2mh — webpki: name constraints accepted for certificates asserting a wildcard name. - GHSA-965h-392x-2mh5 — webpki: name constraints for URI names incorrectly accepted. Both advisories fixed in 0.103.12. Transitive dep (not declared in any Cargo.toml); bump applied via `cargo update -p rustls-webpki --precise 0.103.12`. Cargo.lock-only change. Note: rsr-certifier has pre-existing build errors (missing modules / deps in engine crate) unrelated to this bump — see rsr-certifier's own backlog. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced May 17, 2026
10 tasks
hyperpolymath
added a commit
that referenced
this pull request
Sep 20, 2026
…not see GitHub-generated checks The five contexts this census flagged as unsatisfiable are all published: every one reports in the check-run history of the repository that requires it, as a job of a GitHub-generated workflow (code scanning default setup and friends) that no file in the repository mentions. Evidence, gathered 2026-09-20 from check-runs on the default branch: awesome-gleam Analyze (actions) 8 of the last 8 commits, and PR #12's head awesome-gleam Adjust Configuration reports on main (intermittent) casket-ssg Analyze Code (actions) 15 of the last 30 commits coord-tui CodeQL Analysis (actions, none) 5 of the last 8 commits, and PR #63's head vext CodeQL Analysis (actions, none) 12 reports over 8 commits, and PR #51's head The previous commit stated that all five were re-checked and are "live defects". That re-check answered the wrong question: it confirmed the *rules* were live (active enforcement, ~DEFAULT_BRANCH, integration_id 15368) and never asked whether a *publisher* exists. The publisher is the platform. This matters beyond the ledger: merged guidance to go and patch four repositories' required-status-check lists would have deleted working gates on false evidence, and the deleted names would have been the ones nothing could see — the checks GitHub generates itself. Changes: * the audit's results now read 0 unsatisfiable, with the five candidates and their evidence; the residues table becomes the refuted-candidates table; * the method note becomes the operational rule: a file-based pass may only produce candidates; an unsatisfiable verdict becomes a finding only after check-run history confirms the name never reports; a required context is never deleted on a file-based verdict alone; * the gate carries the same limit in its header, in its warning and error text, and in --print-commands, so the person reading a finding is told to confirm it before acting; * the census caveats section cites this as the worked example rather than a hypothetical. The class remains real — tropical-types#17 was a genuine mis-named requirement. What changes is the confidence level a file-based census may claim.
hyperpolymath
added a commit
that referenced
this pull request
Sep 20, 2026
…not see GitHub-generated checks (#876) ## What Withdraws the five "unsatisfiable required contexts" this census reported, because all five are published. Each one reports in the **check-run history** of the repository that requires it — as a job of a GitHub-generated workflow (code scanning default setup and friends) that no file in the repository mentions: | Repository | Context | Evidence (check-runs, default branch, 2026-09-20) | | --- | --- | --- | | `awesome-gleam` | `Analyze (actions)` | 8 of the last 8 commits, and PR #12's head | | `awesome-gleam` | `Adjust Configuration` | reports on `main` (intermittent) | | `casket-ssg` | `Analyze Code (actions)` | 15 of the last 30 commits | | `coord-tui` | `CodeQL Analysis (actions, none)` | 5 of the last 8 commits, and PR #63's head | | `vext` | `CodeQL Analysis (actions, none)` | 12 reports over 8 commits, and PR #51's head | ## Why the previous pass got it wrong The verification in the previous commit asked whether the *rules* were live — active enforcement, `~DEFAULT_BRANCH`, `integration_id: 15368`. It never asked whether a *publisher* exists. For these five the publisher is the platform itself, not the repository, so a census over repository files cannot see it. That is not a footnote. Acting on the previous version would have meant patching four repositories' required-status-check lists to delete working gates, on false evidence, and the names deleted would have been the ones nothing in the repository can see. ## What changes * results read **0 unsatisfiable**; the five are recorded as refuted candidates with their evidence; * the operational rule is stated where a reader will meet it: a file-based pass may only produce *candidates*; an `unsatisfiable` verdict becomes a *finding* only after check-run history confirms the name never reports; a required context is never deleted on a file-based verdict alone; * the gate says this in its header, in its warning and error text, and in `--print-commands`, next to the remediation it prints; * the census caveats section cites this as the worked example instead of a hypothetical. ## Verification * `bash scripts/tests/check-required-contexts-test.sh` — 5/5 pass. * `bash scripts/check-canonical-names.sh origin/main` — clean. * The refutation is reproducible: for each context, compare `GET /repos/{r}/commits/{default}/check-runs` and the check-runs on a recent PR head.
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 the actions group with 3 updates in the / directory: actions/cache, github/codeql-action and trufflesecurity/trufflehog.
Updates
actions/cachefrom 5.0.2 to 5.0.3Release notes
Sourced from actions/cache's releases.
Changelog
Sourced from actions/cache's changelog.
... (truncated)
Commits
cdf6c1fMerge pull request #1695 from actions/Link-/prepare-5.0.3a1bee22Add review for the@actions/http-clientlicense4695763Add licensed outputdc73bb9Upgrade dependencies and address security warnings345d5c2Add 5.0.3 buildsUpdates
github/codeql-actionfrom 4.31.11 to 4.32.1Release notes
Sourced from github/codeql-action's releases.
Changelog
Sourced from github/codeql-action's changelog.
... (truncated)
Commits
6bc82e0Merge pull request #3447 from github/update-v4.32.1-f52cbc83042f00f2Add a couple of change notescedee6dUpdate changelog for v4.32.1f52cbc8Merge pull request #3445 from github/dependabot/npm_and_yarn/fast-xml-parser-...c5aaca4Merge pull request #3446 from github/mbg/ci/pin-node-packages3e58739Pin@actions/tool-cache@3in workflows to avoid failures withgithub-scripta6ccefbRebuild0e64858Bump fast-xml-parser from 5.3.3 to 5.3.4f985be5Merge pull request #3443 from github/dependabot/npm_and_yarn/tar-7.5.70c8e06dBump tar from 7.5.6 to 7.5.7Updates
trufflesecurity/trufflehogfrom 3.92.5 to 3.93.0Release notes
Sourced from trufflesecurity/trufflehog's releases.
Commits
7f4e37d[INS-228] Add ignorePattern configuration support to Postgres and Sqlserver d...daf5bf1[INS-280] Fix Github "repostories" filter does not respect GHES endpoint (#4677)4d4080bremove tracker type (#4723)ddb9583Added Analysis info to tableau detector (#4717)ef3bf34[INS-307] Added unspecified(0.0.0.0) check to DetectorHttpClientWithNoLocalAd...f70218b[INS-249] Updated Gitlab client from v0.129.0 to v1.12.0(latest) (#4655)a450544Unify some false positive logic (#4720)a9a7416Unify false positive/overlap tests (#4699)7c7facfAdd some false positive tests #47035032470enabled the test which was previously failing due to inaccessible github repo...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 <dependency name> major versionwill 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 versionwill 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