Skip to content

chore: Bump fallow from 3.42.0 to 3.43.1 - #645

Merged
thomasfosterau merged 1 commit into
trunkfrom
dependabot/npm_and_yarn/fallow-3.43.1
Nov 17, 2026
Merged

thomasfosterau merged 1 commit into
trunkfrom
dependabot/npm_and_yarn/fallow-3.43.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 16, 2026

Copy link
Copy Markdown
Contributor

Bumps fallow from 3.42.0 to 3.43.1.

Release notes

Sourced from fallow's releases.

v3.43.1: GitHub Action fix for Linux runners, and fewer false positives

Upgrade notes

  • If your workflow uses the fallow GitHub Action on a Linux runner, this release repairs it. With fallow 3.43.0, the install step of the Action failed on glibc runners such as ubuntu-latest. No change to your workflow is necessary: fallow-rs/fallow@v3 now gets the fix. If you set the input version: 3.42.0 as a workaround, you can remove it.

Changed

  • The fallow skill says what to do when the installed CLI is older than the skill. A plugin can deliver a newer skill than the installed CLI. An unexpected argument error, an invalid value error, or an unknown subcommand then means a version difference. The skill tells the agent to report the version, to tell you to update, and to continue without the argument. (fallow-skills#235)

Bug fixes

  • The GitHub Action no longer fails its install step on a glibc Linux runner. Since 3.43.0, npm installs only the platform package for the libc of the host. The Action then looked for the musl package on a glibc host and stopped with platform package @fallow-cli/linux-x64-musl not installed. The Action now finds the installed package. (#4591)

  • includeEntryExports no longer reports the React Router and Remix entry.server exports as unused. The exports default, handleDataRequest, handleError and streamTimeout now count as used. For React Router, instrumentations and unstable_instrumentations also count as used. A custom appDirectory gets the same rule. Thanks @​cr101 for the report. (#4583)

  • Entry-point named re-exports through export * barrels credit the underlying declaration. fallow dead-code reported a type or value as unused when an entry file re-exported it by name from an export * barrel. Each namespace of a merged declaration, type and value, now gets its own credit. Thanks @​mattlewis92 for the report. (#4579)

  • fallow audit no longer reports an old clone group as introduced when the change rewrites the lines above one copy. A rename of one copy, together with fewer import lines above the other copy, could fail --gate new-only on duplication that the change did not write. (#4580)

  • VS Code: the "enable" links in the Security Candidates and Health views no longer freeze Settings in Cursor. The links now run the new Fallow: Enable Security Candidates and Fallow: Enable Health View commands. These commands set fallow.security.enabled or fallow.health.enabled in workspace settings, or in user settings when no folder is open. Thanks @​milichev for the report. (#4553)

  • fallow migrate keeps the production markers of a migrated config visible. An ignoreDependencies or ignoreBinaries name such as left-pad! now migrates as left-pad, with a warning. A project exclusion with the production marker gets a warning with an overrides entry that hides the paths. A plugin section whose config names files that the plugin does not find by name now gets a warning that names these files. Thanks @​cr101 for the report. (#4585)

  • The Playwright plugin reads configs with other names. A config named playwright.<name>.config.<ext>, such as playwright.e2e.config.ts, is now a Playwright config. So is a config that a package.json script passes with playwright test --config <file> or -c <file>. The plugin also reads .mts, .mjs, .cts and .cjs configs. A script that runs a tool by its path, such as node_modules/.bin/playwright, now also gives its --config file to the plugin. Thanks @​cr101 for the report. (#4586)

  • unlisted-binaries no longer reports shell reserved words or subshell parentheses as binaries. A script with for ... do ... done or if ... then ... fi gave findings such as for, do and fi. A script with a subshell gave findings such as (tool. The script parser now skips reserved words, reads a subshell as a separate command, and finds the command after a case pattern and in a function body. Thanks @​ethan-huo for the report. (#4566)

  • A JSDoc visibility tag on a re-export now stops the unused report. Fallow now reads @public, @internal, @beta, @alpha and @expected-unused on export { a, b } from './impl', on export * as ns from './impl', and on export { a, b } that forwards imported bindings. A re-export with a visibility tag is public API and counts as a use of its source export. The cache versions change, so the first run after the update parses every file again. Thanks @​cr101 for the report. (#4584)

  • --constant-parameters follows a loader helper that returns a value loaded from an unknown source. A module-scope function such as export const load = (path) => import(path) is now a loader. So const mod = await load(name); mod.migrate() skips only the exported functions named migrate, and the rule keeps its other findings. (#4567)

  • fallow dead-code credits a member on a local that holds a method call result. In const rotated = local.rotate(angle); rotated.translate(1, 1);, fallow now credits Point.translate, as it does for the chained call. Thanks @​Smrtnyk for the report. (#4552)

Full Changelog: fallow-rs/fallow@v3.43.0...v3.43.1

v3.43.0: constant-parameter rule, fallow audit --staged, and mutation replay

Features

  • The new opt-in rule constant-parameter reports a parameter that each call passes in one way. The finding gives the reason identical-argument when each visible call passes the same value. It gives never-passed when no call passes an optional parameter. For a destructured options parameter such as { retries = 3, signal }, option_key names each key that no call sets, or that each call sets to the same value. Turn the rule on with fallow dead-code --constant-parameters or rules.constant-parameters. The default is off, and the rule has no automatic fix. The rule reports only when it sees each caller. It skips public API and entry-point exports, dynamic imports, CommonJS and functions with fewer than 2 calls. With --type-aware, the rule also reports the reason unused-default and reads the methods of exported classes. These findings have evidence: "type-aware". (#4491, #4516)
  • fallow audit --staged audits the staged index, not the working tree. The changed files are the staged changes against HEAD, and the analysis reads each file from the index. Unstaged edits and untracked files do not change the result of the audit. When Git gives the hook another index file (git commit -a, git commit <path>), the audit reads that index. --staged does not take --base or --changed-since.
  • fallow mutation inspect <id> --replay calls the mutated function on the original code and on the mutant. Pass the arguments with --args '[2, 3]'. The replay calls the export three times on each side and shows the results side by side. A difference that each call repeats is a witness. A test with this input can kill the mutant. Equal results are no_witness_found, never equivalent. The Vitest and node:test runners replay, and the JSON output adds the replay object.
  • fallow mutation --record-args values records the arguments of the changed exported functions. --replay without --args then replays up to 3 recorded inputs and stops at the first witness. Recording is off by default and runs after the mutant runs, so it never changes a result. The inputs stay in the gitignored cache directory for 7 days. Fallow does not keep an input with a secret. --record-args shapes keeps only the argument types.
  • fallow mutation tasks gives a ready test input for a survivor. After a --record-args values run, fallow mutation tasks replays the recorded inputs of up to 20 open tasks. A task then gets a witness with the result of the current code, the result of the changed code and the --replay command. A test with that input that asserts the current result kills the mutant. The MCP tool mutation_tasks gives the same field.
  • The new opt-in mutation operator nullish-fallback removes the fallback of a ?? b. Name it in --operators or mutation.operators. A survivor shows that no test gives a nullish left operand. With --typecheck, a survivor gets the hint type-non-nullish when the declared type of a excludes null and undefined. A negate-condition survivor can now also get equivalence_hint: "constant-parameter" when the condition is a parameter p, !p or !!p, and each visible call passes the same literal for p. The status stays survived, and the score does not change. (#4502)
  • The focus map of the review brief ranks changed files also by churn, complexity growth, test reach and surviving mutants. The score of a focus unit can have the new components churn, worsened, test_reach and mutation. The new fallow audit --mutation-report <file> flag reads a saved fallow mutation --format json report for the mutation component. These components can change total, the label and the rank order of a unit. triage.risk_class does not change. (#4505)
  • The agent task matrix and the fallow skill now name fallow mutation. The matrix has the row "improve or check the tests of a change" with fallow mutation --plan --base <ref>. The row is in fallow --help, fallow schema, the fallow://task-matrix MCP resource and the AGENTS.md block of fallow init --agents and fallow hooks install --target agent. The skill has a short workflow for the tests of a change.
  • fallow architecture --shared-state lists direct writes through imported values and custom global read and write sites. The observations have human, JSON and Markdown output. They are not in the finding totals and gates. They make no claim about runtime identity or execution order.
  • health.tailwindIgnorePatterns excludes intentional Tailwind arbitrary values. Each regular expression matches a normalized prefix-[value] token, so -mt-[7px] and mt-[7px] both match as mt-[7px]. Fallow removes matching classes from the token-drift findings and analytics, also in CVA variants. The default excludes nothing. Thanks @​DrJKL for the patch in #4421.
  • fallow security says when client-server-leak checked nothing. The rule starts only from files with a top-level "use client" directive. When no such file exists, the run records the client-server-leak-no-client-roots workspace diagnostic. The human output prints a blind-spot line, and MCP adds a warnings sentence. Thanks @​cr101 for the report. (#4430)
  • A stored security verdict now survives an edit that moves the sink to another line. Each fallow security finding has a new stable_finding_id of the form sec1:<16 hex digits>. Whitespace, comments, line breaks and an edit above the sink do not change it. fallow security survivors accepts this id or finding_id in a verdict. The location-based finding_id and the SARIF fingerprint do not change. A sink in Vue, Svelte or Angular template markup has no stable_finding_id. Thanks @​cr101 for the report. (#4429)

... (truncated)

Commits
  • 8cc305d chore: release v3.43.1
  • cd1bbe0 fix(extract): credit members read on a local of a method call result (#4601)
  • ac64a51 fix(constant-parameter): follow a loader helper that returns an unknown-sourc...
  • a90ca9f fix(extract): read JSDoc visibility tags on re-exports (#4599)
  • cfaabc6 fix(scripts): read shell reserved words and subshells in scripts (#4600)
  • 89ffa31 fix: keep production markers in migrate and read named Playwright configs (#4...
  • 0776b47 fix(vscode): enable links set the setting without the Settings editor (#4597)
  • 7a3fbe6 fix(audit): keep a clone inherited when lines above one copy are rewritten (#...
  • b14326d fix(action): find detect-libc in the installed package during verification (#...
  • b0ba708 chore(deps-dev): bump vitest from 5.0.5 to 5.1.0 in /tools/mutation-runner (#...
  • Additional commits viewable in compare view

Dependabot compatibility score

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 this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [fallow](https://github.com/fallow-rs/fallow) from 3.42.0 to 3.43.1.
- [Release notes](https://github.com/fallow-rs/fallow/releases)
- [Changelog](https://github.com/fallow-rs/fallow/blob/main/release.toml)
- [Commits](fallow-rs/fallow@v3.42.0...v3.43.1)

---
updated-dependencies:
- dependency-name: fallow
  dependency-version: 3.43.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Nov 16, 2026
@changeset-bot

changeset-bot Bot commented Nov 16, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 349b08f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatedfallow@​3.42.0 ⏵ 3.43.199 -110010096100

View full report

@thomasfosterau
thomasfosterau merged commit 0602f83 into trunk Nov 17, 2026
5 checks passed
@thomasfosterau
thomasfosterau deleted the dependabot/npm_and_yarn/fallow-3.43.1 branch November 17, 2026 03:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant