Repository navigation
chore(deps): bump docker/setup-qemu-action from 3.0.0 to 3.7.0 - #17
Merged
hyperpolymath merged 2 commits intoJan 22, 2026
Merged
hyperpolymath merged 2 commits into
hyperpolymath merged 2 commits into
Conversation
dependabot
Bot
added
dependencies
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
Bumps [docker/setup-qemu-action](https://github.com/docker/setup-qemu-action) from 3.0.0 to 3.7.0. - [Release notes](https://github.com/docker/setup-qemu-action/releases) - [Commits](docker/setup-qemu-action@6882732...c7c5346) --- updated-dependencies: - dependency-name: docker/setup-qemu-action dependency-version: 3.7.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/github_actions/docker/setup-qemu-action-3.7.0
branch
from
January 22, 2026 10:42
47a3f19 to
de55d4e
Compare
hyperpolymath
deleted the
dependabot/github_actions/docker/setup-qemu-action-3.7.0
branch
January 22, 2026 10:43
hyperpolymath
added a commit
that referenced
this pull request
Sep 15, 2026
…, and arm --warnings-as-errors (#786) Discharges task #17 (owner ruling R-C, \"#17 next\"). ## What was wrong **CSA006 always returned `[]`.** Both arms of `csa006_scorecard_config_advice/2` built their finding with `findings = [f | findings]` **inside an `if`**. Elixir's `if` does not leak bindings, so every assignment was dead and the function returned the outer `findings` — empty, always. This is **live**, not latent: `:code_scanning_alerts` is in the default rule list (`cli.ex:57`), `cli.ex:806` calls it, and `hypatia-scan-reusable.yml` exports `GITHUB_TOKEN` to the scan step (line 106). The rule has been running on all **449 consumers** and has never once produced a finding. It compiled clean, emitting only `variable "findings" is unused`. That is the whole argument for arming `--warnings-as-errors`. ## Measured blast radius — inflation, not breakage Probed all 438 non-archived repos in both orgs for open Scorecard alerts: | | repos | |---|---:| | open `CodeReviewID` (feeds the `:medium` arm) | **200** | | open `MaintainedID` (feeds the `:info` arm) | 62 | | probe unavailable (403/404) | 71 | So CSA006 will newly fire on **up to 200 repos**, further gated on `has_single_contributor?`. **No gate breaks:** the reusable's blocking step refuses only `high` or `critical`, and these arms are `medium` and `info`.⚠️ **The next estate-wide Hypatia re-measure will therefore go UP by up to ~200 findings.** That is this rule starting to work, not a regression. Please don't read it as one. ## The dead module `secret_scanner_verification.ex` is referenced nowhere — not in the rule list, not in `cli.ex`, no tests, no manifest entry. It is also broken in **seven independent ways**, so #17's framing ("an inert trufflehog fallback") understated it: the fallback was never reached, because `System.cmd(...) |> elem(0) == 0` compares the **output string** to the integer `0` and is always false. Full list in the commit message. Repairing it would be a rewrite, and Phase 1c supersedes the design anyway (assert the real 501-repo gitleaks rail is armed, rather than reimplement scanner invocation in Elixir). Under AGENTS.md §6, repaired dead code that *reads* as a working capability is worse than no code. **Deletion is in its own commit (`4581dcc`) and can be reverted alone** if you'd rather it were repaired or simply left in place. ## Controls | Arm | Result | |---|---| | `--warnings-as-errors` on **main** | **exit 1** (13 warnings) — the gate can fail | | `--warnings-as-errors` on this branch | **exit 0** — the gate can pass | | Old CSA006 shape, same input | returns `[]` | | New CSA006 shape, same input | returns the finding | | New tests against the old module | fail (undefined) | | `mix test` main / branch | 1560 / **1566**, the *same* 2 pre-existing `ResearchExtensionsTest` failures — **zero regressions** | | Escript soundness gate | **13/13 rules fired**, rc=0 | The decision logic is split into pure public functions specifically so the regression test can assert a **non-empty** result. A test asserting only `== []` passes against the broken version — which is exactly how this survived. ## Also The 8 `@doc` blocks before Plug `get "/path"` macros attached to the generated private `do_match/4` and were discarded — 8 blocks of endpoint documentation that could never appear in the docs. Converted to `#` comments, prose unchanged. `@doc` on the real public `protect/2` is left alone. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_011YTttTxnPc1V2sATvzBDN7 --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com> Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
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
2 participants
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.
Rebasing might not happen immediately, so don't worry if this takes some time.
Note: if you make any changes to this PR yourself, they will take precedence over the rebase.
Bumps docker/setup-qemu-action from 3.0.0 to 3.7.0.
Release notes
Sourced from docker/setup-qemu-action's releases.
Commits
c7c5346Merge pull request #230 from docker/dependabot/npm_and_yarn/docker/actions-to...3a517a1chore: update generated contenta5b45edbuild(deps): bump@docker/actions-toolkitfrom 0.62.1 to 0.67.03a64278Merge pull request #220 from docker/dependabot/npm_and_yarn/brace-expansion-1...94906bachore: update generated content4027abfbuild(deps): bump brace-expansion from 1.1.11 to 1.1.12bee0aaaMerge pull request #221 from docker/dependabot/npm_and_yarn/tmp-0.2.40d7e257chore: update generated contentb869601build(deps): bump tmp from 0.2.3 to 0.2.43a043edMerge pull request #219 from docker/dependabot/npm_and_yarn/undici-5.29.0Dependabot 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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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)