Skip to content

chore(deps): update dependency fallow to v3.43.2 - #983

Merged
fengmk2 merged 1 commit into
masterfrom
renovate/fallow-3.x-lockfile
Nov 20, 2026
Merged

fengmk2 merged 1 commit into
masterfrom
renovate/fallow-3.x-lockfile

Conversation

@renovate

@renovate renovate Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
fallow (source) 3.42.0 → 3.43.2 age confidence

Release Notes

fallow-rs/fallow (fallow)

v3.43.2

Compare Source

Fixed
  • fallow dead-code no longer reports enum members that code reads through an alias, or of an enum that code passes on whole.
    A member read through const Alias = Color, through a class field such as
    protected readonly levels = Level, through this.levels.High, or through
    an Angular template (inline or templateUrl) that reads the field is now
    used. Members that no alias reads are still reported. When code passes the
    whole enum on, for example as takesEnum(Shape) or { ref: Size }, each
    member of that enum is now used, as with Object.values(Shape). A
    typeof E (for example keyof typeof E) now counts as a use of every
    member of E.
    (Closes #​4578)

  • unused-component-inputs and unused-component-outputs read more Angular template syntax. The template scanner now credits a member in these places: a pipe argument (value | slice: start()), an interpolation in a plain attribute (title="{{ label() }}"), a keyed structural directive clause (*ngTemplateOutlet="tpl; context: ctx", *ngIf="ready; else loading"), the condition of @else if (cond; as alias), a style binding with a % unit ([style.width.%]), an explicit this. or this!. read, the head of an ICU message ({count, plural, ...}), and a host binding value in backticks. A component member that has the same name as a @for loop item elsewhere in the template is no longer hidden. An ICU case that opens into an interpolation (other {{{n}} items}) no longer stops the scan, so the members that the template reads after the ICU message are credited again. (Closes #​4576)

  • Inputs and outputs of a base class are credited from a subclass in another file. When a component or directive extends a base class from another file, its class body and its template now credit the inputs and outputs that the base class declares. The subclass can extend the base directly, through an intermediate class, or through a re-export. (Closes #​4577)

  • A Homebrew or cargo install binary now names a companion install that works for it. Such a binary has no npm launcher, so it does not find a global npm companion. When fallow-type-aware is missing, the message now names FALLOW_TYPE_AWARE_BIN with the global npm path on macOS and Linux. On Windows, it names the npm install of fallow. When fallow-similar-code is missing, the message names the release archive and the directory of the binary. The npm install keeps its messages and its companion lookup.
    (Closes #​4609)

  • Runtime coverage finds the sidecar in a Yarn Plug'n'Play project. Fallow now reads the signed binary from .yarn/unplugged. Before, discovery stopped at the unsigned wrapper, and the run failed with a signature error.

  • An unsigned node_modules/.bin/fallow-cov wrapper no longer hides a working sidecar. Discovery now continues to ~/.fallow/bin and PATH. It uses the wrapper only when no other location has a sidecar, so the signature error names the file that exists. Before, a pnpm project with a custom virtualStoreDir failed with a signature error even when ~/.fallow/bin/fallow-cov was installed.

  • fallow agent install no longer registers fallow mcp-server for a binary that cannot serve MCP. The Homebrew and cargo install fallow-cli binary has no mcp-server subcommand, but it answers fallow mcp-server --version with its own version and exit code 0. The MCP step took that answer as proof of the MCP server and printed a codex mcp add command that failed. Now the step accepts the running binary only when the answer comes from the MCP server (fallow-mcp <version>). Without another launcher, the step skips with mcp_entry_unavailable. Its message names cargo install fallow-mcp and the release archive, so a Homebrew or cargo install user gets a route that works.

Security
  • Runtime coverage no longer starts a package manager to find the fallow-cov sidecar. Before, sidecar discovery ran yarn bin, pnpm bin, bun pm bin or npm root in the analyzed project. A package manager reads config from the project, for example .yarnrc yarn-path, .yarnrc.yml yarnPath and plugins, or .pnpmfile.cjs, so a repository could run its own code when you analyzed it with --runtime-coverage. This happened before the sidecar signature check. Fallow now looks only in fixed install locations: the @fallow-cli/fallow-cov-<platform> package in node_modules, the pnpm and Bun stores, the Yarn unplugged folder, node_modules/.bin, ~/.fallow/bin and PATH. This applies to health, audit and security with --runtime-coverage, to the MCP runtime-coverage tools, and to the sidecar check of fallow coverage setup. Versions 2.39.0 to 3.43.1 are affected. On an older version, set FALLOW_COV_BIN to a signed fallow-cov binary. Thanks @​hgrgr for the report. (GHSA-m9pr-74q6-w362)

v3.43.1

Compare Source

Fixed
  • fallow dead-code no longer reports enum members that code reads through an alias, or of an enum that code passes on whole.
    A member read through const Alias = Color, through a class field such as
    protected readonly levels = Level, through this.levels.High, or through
    an Angular template (inline or templateUrl) that reads the field is now
    used. Members that no alias reads are still reported. When code passes the
    whole enum on, for example as takesEnum(Shape) or { ref: Size }, each
    member of that enum is now used, as with Object.values(Shape). A
    typeof E (for example keyof typeof E) now counts as a use of every
    member of E.
    (Closes #​4578)

  • unused-component-inputs and unused-component-outputs read more Angular template syntax. The template scanner now credits a member in these places: a pipe argument (value | slice: start()), an interpolation in a plain attribute (title="{{ label() }}"), a keyed structural directive clause (*ngTemplateOutlet="tpl; context: ctx", *ngIf="ready; else loading"), the condition of @else if (cond; as alias), a style binding with a % unit ([style.width.%]), an explicit this. or this!. read, the head of an ICU message ({count, plural, ...}), and a host binding value in backticks. A component member that has the same name as a @for loop item elsewhere in the template is no longer hidden. An ICU case that opens into an interpolation (other {{{n}} items}) no longer stops the scan, so the members that the template reads after the ICU message are credited again. (Closes #​4576)

  • Inputs and outputs of a base class are credited from a subclass in another file. When a component or directive extends a base class from another file, its class body and its template now credit the inputs and outputs that the base class declares. The subclass can extend the base directly, through an intermediate class, or through a re-export. (Closes #​4577)

  • A Homebrew or cargo install binary now names a companion install that works for it. Such a binary has no npm launcher, so it does not find a global npm companion. When fallow-type-aware is missing, the message now names FALLOW_TYPE_AWARE_BIN with the global npm path on macOS and Linux. On Windows, it names the npm install of fallow. When fallow-similar-code is missing, the message names the release archive and the directory of the binary. The npm install keeps its messages and its companion lookup.
    (Closes #​4609)

  • Runtime coverage finds the sidecar in a Yarn Plug'n'Play project. Fallow now reads the signed binary from .yarn/unplugged. Before, discovery stopped at the unsigned wrapper, and the run failed with a signature error.

  • An unsigned node_modules/.bin/fallow-cov wrapper no longer hides a working sidecar. Discovery now continues to ~/.fallow/bin and PATH. It uses the wrapper only when no other location has a sidecar, so the signature error names the file that exists. Before, a pnpm project with a custom virtualStoreDir failed with a signature error even when ~/.fallow/bin/fallow-cov was installed.

  • fallow agent install no longer registers fallow mcp-server for a binary that cannot serve MCP. The Homebrew and cargo install fallow-cli binary has no mcp-server subcommand, but it answers fallow mcp-server --version with its own version and exit code 0. The MCP step took that answer as proof of the MCP server and printed a codex mcp add command that failed. Now the step accepts the running binary only when the answer comes from the MCP server (fallow-mcp <version>). Without another launcher, the step skips with mcp_entry_unavailable. Its message names cargo install fallow-mcp and the release archive, so a Homebrew or cargo install user gets a route that works.

Security
  • Runtime coverage no longer starts a package manager to find the fallow-cov sidecar. Before, sidecar discovery ran yarn bin, pnpm bin, bun pm bin or npm root in the analyzed project. A package manager reads config from the project, for example .yarnrc yarn-path, .yarnrc.yml yarnPath and plugins, or .pnpmfile.cjs, so a repository could run its own code when you analyzed it with --runtime-coverage. This happened before the sidecar signature check. Fallow now looks only in fixed install locations: the @fallow-cli/fallow-cov-<platform> package in node_modules, the pnpm and Bun stores, the Yarn unplugged folder, node_modules/.bin, ~/.fallow/bin and PATH. This applies to health, audit and security with --runtime-coverage, to the MCP runtime-coverage tools, and to the sidecar check of fallow coverage setup. Versions 2.39.0 to 3.43.1 are affected. On an older version, set FALLOW_COV_BIN to a signed fallow-cov binary. Thanks @​hgrgr for the report. (GHSA-m9pr-74q6-w362)

v3.43.0

Compare Source

Added
  • Production mode reports a test pattern that drops a file that production code imports.
    A built-in production pattern such as **/test/** also matches production
    source, for example src/components/runner/test/Runner.vue. Fallow does not
    analyze that file, so an export or a parameter that only this file uses can
    appear in a finding. When a production file imports such a file,
    workspace_diagnostics[] now carries one production-excluded-file-imported
    entry for each pattern, with pattern, file_count and the first five
    files. An import of a workspace package whose entry file such a pattern
    excludes counts too. The human output prints the same warning on stderr. The production
    patterns do not change. To analyze the file, move it out of the matched path,
    or run that analysis without production mode (--no-production or
    production: { deadCode: false }).
    (Closes #​4498)

  • duplicates.normalization.consistentIdentifiers finds renamed copies without false matches. Use it together with ignoreIdentifiers. A clone then needs a one-to-one mapping between the names of its instances: a = b + c matches x = y + z, but not x = x + x. When a token breaks the mapping, fallow keeps each longest part of the clone that maps one-to-one and has minTokens or more tokens. An instance that breaks the mapping does not shorten the clone of the other instances. The option is off by default, and no mode turns it on. fallow migrate now maps the ignoreIdentifiers and ignoreLiterals options of an imported duplication config, and keeps string values compared when an imported weak mode did not ignore literals. Thanks @​neumaennl for the report. (Closes #​4626)

  • New rule unused-protected-class-members reports protected class members that no code reads. The rule is off by default, so the default output does not change. A protected member is used when its class or a subclass reads it through this or super. A subclass override is used when the base class calls the member. Classes of the public API of a package are not checked, because a consumer can subclass them. Production mode ignores reads in test files, as for public members. Turn the rule on in rules, select it with --unused-protected-class-members, and suppress one finding with // fallow-ignore-next-line unused-protected-class-member. The findings go to the new unused_protected_class_members array in JSON and reach SARIF, CodeClimate, the human report, the LSP and fallow explain. unused-class-members still does not report protected members. A finding on a run with an incomplete import graph carries reachability_caveats[]. Eleven arrays carry it: unused_protected_class_members[] joins the ten arrays that carried it before. Known limits: a read through a string key (this["member"]()) gives no credit, as for public members, and the rule does not check a constructor parameter property (constructor(protected readonly x: X)). An ignoreDecorators pattern that matches only protected members no longer gets the warning for an unmatched pattern. The extraction cache version and the graph cache version change, so the first run after the upgrade parses every file again.
    Thanks @​neumaennl for the report. (Closes #​4624)

  • production.ignore drops paths from discovery in production mode only.
    The object form of production accepts ignore, an array of
    project-root-relative globs, for example
    "production": { "deadCode": true, "ignore": ["scripts/**"] }. A run in
    production mode excludes these paths, in addition to the built-in test,
    spec, story and dev patterns. The default run keeps them. The globs apply to
    each analysis that runs in production mode, also when --production or a
    FALLOW_PRODUCTION* variable selects the mode. The boolean form of
    production does not change.
    Thanks @​cr101 for the report. (Closes #​4622)

  • client-server-leak now checks React Router Framework Mode apps. React Router code has no "use client" directive, so the rule had no starting point in such an app. When the React Router plugin is active, route modules (root.tsx included) are client roots. A route module is a file that the route config names, the root route, or a route file of the route directory. A helper next to a route.* file and a test file are not roots. Only the code that React Router keeps in the client build counts: an import, a re-export or a process.env.X / import.meta.env.X read that only loader, action, middleware or headers use is not followed. This also applies to a route module that another module imports. A secret read in the route component itself is reported. An env read in another form, such as const { X } = process.env, counts for the whole route module. Files named *.client.* or under a .client/ directory are client roots, and files named *.server.* or under a .server/ directory are server-only-import sinks, in the packages where the plugin is active. Such an app no longer gets the client-server-leak-no-client-roots diagnostic.
    Thanks @​cr101 for the report. (Closes #​4582)

  • circularDependencies.allow accepts exact cycles. Each entry lists the files of one cycle in import order, relative to the project root, for example [["src/a.ts", "src/b.ts"]]. An entry accepts only the cycle with exactly these files, from any start file. A new cycle through the same imports stays reported, which an inline fallow-ignore-next-line circular-dependency marker does not give. Paths are case-sensitive. An entry needs at least 2 files and lists each file once. An accepted cycle does not count toward the limit of 20 listed cycles per group of files that import each other. An entry that matches no cycle gives a circular-dependencies-allow-unmatched diagnostic in JSON, SARIF, Markdown and the stderr note. An entry that the detector cannot check (more than 12 files, or all files in a group that reached the limit) gives no diagnostic. A fallow-ignore-next-line circular-dependency comment on an accepted cycle becomes a stale suppression, so remove it when you add the entry. fallow migrate now translates the cycles.allow list of a migrated config. Thanks @​cr101 for the report. (Closes #​4623)

  • fallow audit can fail on a new clone group. The new rule introduced-clone-group (error, warn or off) sets how a clone group takes part in the audit verdict and exit code. The default is warn, so the verdict does not change for current configs. With error, a clone group that the change introduces fails the audit with exit code 1. With off, the group stays in the report but does not change the verdict. Under --gate new-only, an inherited clone group never gates. Under --gate all, every clone group in the changed files follows the rule. With overrides, the rule resolves for the file of each copy, and the most severe result applies. So an override cannot exempt a clone group that has a copy outside the override. For generated code, use duplicates.ignore or ignorePatterns. duplicates.threshold does not change and can still fail the run. fallow explain introduced-clone-group describes the rule.
    Thanks @​cr101 for the report. (Closes #​4658)

  • fallow fix reports each export that a kept re-export holds back. fix no longer removes the export of a declaration while a re-export that it keeps still names that declaration. A re-export stays, for example, in a file that fix skips as low confidence, in a file whose names ignoreExports hides, or in a list statement that has no safe text edit. Each withheld removal is a remove_export entry with skip_reason: "kept_re_export". The new JSON counter skipped_kept_re_exports counts these entries, and the human output and the CI step summary state them. The exit code does not change. Limit: a file that ignorePatterns excludes is not in the module graph, so a re-export in such a file cannot hold a removal back. Run the type check after fallow fix when an ignored file re-exports project code.
    (Refs #​4636)

  • fallow type-aware setup installs the type-aware companion for a binary that did not come from npm. A Homebrew, cargo install or release-archive binary on macOS or Linux now gets the companion with one command. The command asks Node for its platform and architecture, downloads the bundle of its own version from the GitHub release, and checks the signature with the release key that the binary holds before it unpacks. The bundle goes into a versioned user directory, and Fallow checks that directory after FALLOW_TYPE_AWARE_BIN and the sibling of the executable. --from <file> installs a copied bundle on a machine with no route to GitHub. The download honors HTTPS_PROXY, HTTP_PROXY, NO_PROXY and FALLOW_CA_BUNDLE. fallow type-aware cleanup removes the companions of other versions. The first bundles appear with the release that contains this change. type-aware status reports discovery_source: "setup-directory" for such a companion.
    (Closes #​4630)

  • fallow-ignore-start and fallow-ignore-end suppress one clone. Put // fallow-ignore-start code-duplication -- <reason> above a block and // fallow-ignore-end code-duplication below it. A clone inside the range is not reported. A clone that reaches into the range is cut at the range border, and a cut part below minTokens or minLines is not reported. The /* */, JSDoc and <!-- --> forms work too, each on its own line. A marker in a string or template literal does not count. Ranges support only code-duplication. fallow dupes and fallow audit report a range marker with a problem (an end with no start, a nested start, a start with no end, no kind, another kind, or a marker that shares its line with code) in the new range_marker_problems array, and such a marker has no effect. fallow suppressions lists ranges with level: "range" and end_line. Clone groups get a suppress-range action next to suppress-line. A missing reason on a range start shows is_range: true in its suppression origin. A range cuts its neighbor clones, so a baseline gate can show a cut clone as new, and its ignoredClones key changes: save the baseline again after you add a range. The duplication token cache and the extraction cache are rebuilt once after the upgrade.
    Thanks @​neumaennl for the report. (Closes #​4706)

  • A boundary zone can list its public entry files with publicFiles. Since 3.31.0, the boundary check follows a named or default import through re-export chains and judges it by the file that declares the symbol. That made the one-public-entry-file pattern (for example src/modules/billing/index.ts) report every import through the entry file. Now a zone can set "publicFiles": ["src/modules/billing/index.ts"]. A file of another zone may then import only those files of the zone, and the chain walk stops at a public entry file. A deep import that a rule allows gets a finding with reason: "internal_file" and public_files, which names the files to import instead. On an autoDiscover zone, each glob is relative to each discovered folder, so "publicFiles": ["index.ts"] gives each module its own entry file. The output omits reason for a zone-rule finding, so a project without publicFiles gets the same output as before. fallow list --boundaries --format json shows the public_files globs of a zone. Thanks @​robertrguerrero for the report. (Closes #​4760)

  • fallow mutation can select Vitest projects with --runner-project. A root Vitest config can hold projects from separate config files, such as browser or server projects. The mutation companion cannot instrument those projects, so the run failed at setup even when the tests of interest were in an inline project. Now --runner-project <name>, which you can repeat, or the mutation.runnerProjects config key selects projects as the Vitest --project flag does, wildcards included. Each project that is not selected stays out of the run. A selected project from a separate config file still fails at setup, and a name that matches no project fails with the Vitest message. With a runner other than Vitest, a selection exits with code 2. Thanks @​michalius for the report. (Closes #​4785)

Changed
  • fallow audit --quiet now prints only the actionable part of the human, compact and markdown reports. This is a behavior change for existing --quiet users. Before, --quiet removed only the progress output. Now the report also drops unchanged inherited findings, aggregate metrics (vital signs, health score, hotspots and other ranked lists) and the stale and active records of health.thresholdOverrides. The report keeps introduced and worsened findings, diff-risk findings, configuration errors, analysis failures, warnings about incomplete analysis, and the insufficient and no_match override records. FALLOW_QUIET=1, or --ci with an explicit --format human, --format compact or --format markdown, also sets quiet and gets this view. --ci alone prints SARIF, which keeps the complete report. A script that sets FALLOW_QUIET=1 and posts the output of fallow audit --format markdown no longer gets the inherited context. The verdict, the exit code and the JSON, SARIF, CodeClimate, review and GitHub formats do not change. Run without --quiet, or use --format json, for the complete report.
    Thanks @​Fidasek009 for the report. (Closes #​4575)

  • fallow dupes now compares the static text of template literals. Before, every template literal matched every other template literal. Now the text outside the ${...} expressions must match, as for string literals. Escapes compare by their value, so `\x41` matches `A`. Thus code that differs only in template text is no longer a clone, and default results can show fewer clone groups. Set normalization.ignoreStringValues: true, or use mode: "weak" or "semantic", to match template literals with different text again. (#​4626)

  • The VS Code and Cursor extension shows one Fallow status bar item instead of up to five. The item shows the finding count and the health grade, for example Fallow 9 · C. Its hover shows the issue breakdown, duplication, health, the audit verdict, the license state, the active workspace and whether findings are visible in the editor. A click opens a menu to run the analysis, hide or show findings, run the audit, switch the workspace, or open the settings. The item gets an error background when the audit fails. When all findings are hidden in the editor, the item keeps a closed-eye icon, also next to an audit or progress icon. The separate workspace, audit, license and eye items are gone. All commands keep their ids, and the new Fallow: Show Status Menu command opens the menu.

  • The Fallow status bar item shows a license only when it needs action. The item text shows the license when it expires within 14 days, has expired, or is not valid. When the license is past its grace window (paid features are blocked), the item also gets a warning background. A failed audit keeps the error background, also when the license is blocked. An expired license that still works shows the notice without a background. License material that the CLI cannot read, for example a stale FALLOW_LICENSE value, now shows "license invalid" with a warning icon. Before, the extension hid it. The hover shows the tier, the seats, the features and the expiry, and it offers a refresh when the CLI suggests one.

  • fallow migrate maps production exclusions to production.ignore.
    A !pattern! entry in a project setting of the migrated config, at the
    root or in a workspace, becomes a production.ignore glob. Before, fallow migrate
    dropped these entries and suggested an overrides entry, which hid the
    findings in every mode.

  • fallow mutation --kill-matrix-for runs the target tests first and stops when no target kills the mutant. Such a mutant now gets the new status not_killed_by_target. It runs no other covering test and gets no survivor retry. After a target kill, the other covering tests run fastest first up to the first kill. Only a kill by exactly one target test and no other test gets a retry, so one flaky run cannot make a test look necessary. A retry that does not kill again with the same tests makes the mutant flaky. For deterministic tests, each target keeps the same kills, unique_kills and target_only_kills, with fewer test runs. This mode has no score: summary.score is null, and --min-score exits 2. --kill-matrix-full keeps the earlier behavior, in which each mutant gets a normal status and the run has a score. kill_matrix.target_mode names the mode (target-first or full). Thanks @​cr101 for the report. (Closes #​4588)

  • A type-aware companion of another Fallow release stays valid while it speaks the same wire protocol. Fallow compared the companion package version with its own version, so each upgrade needed a new companion. It now compares only the wire protocol version, so a companion stays in use until the protocol changes. The wire protocol is now 8, because the format changed three times at version 7. A CI check now ties the version to a hash of the wire contract, so a format change cannot ship at the old version. Companions of earlier releases are not accepted: such a companion refuses the request, and the error then names fallow type-aware setup and the npm install. The npm launcher still selects the companion of the exact version.

  • Bursts of merges to main start fewer CI runs. The push runs of CI on main now share one concurrency group. A started run always finishes, and a newer push replaces a run that waits in the queue. The release commit keeps a group of its own, so the release gate always gets a result for it. The prose-only skip on main now also checks that the push run of the previous commit succeeded, because a replaced run leaves that commit without a result. This change affects contributors only.

  • Pull request checks finish sooner. The Rust CodeQL analysis takes about 20 minutes and ran longer than CI on most pull requests. It now runs on pushes to main and on the weekly schedule. A pull request analyzes Rust only when it changes the CodeQL configuration. The JavaScript and TypeScript analysis and the Actions analysis still run on each pull request. On main, a newer push replaces a queued analysis, and a started analysis always finishes. This change affects contributors only.

  • PGO Validate skips pull requests that cannot change a PGO build. The workflow starts for each edit of Cargo.toml or release.yml, and its comparison takes more than an hour on a macOS runner. A version bump, a dependency entry, a lint or a publish job change now skips the comparison. A change of a release profile section, of the top-level env of release.yml, or of the release jobs that train and use the profile, still runs it. The weekly run on main still covers dependency changes. This change affects contributors only.

  • The Rust structure checks use cargo-fallow 0.4.0. The Rust Structure CI job and mise.toml pin the same release. The baseline no longer holds three complexity entries for functions that are now under the limits. This change affects contributors only.

  • Pull request CI finishes sooner. Nextest starts tests in binary and name order, so a slow test that sorts late ran alone at the end of a CI test partition, and the partition waited for it. The ci nextest profile now starts the tests that take 25 seconds or more first. This change affects contributors only.

  • Pull request jobs miss the Rust cache less often. The repository uses more than the GitHub cache limit, so GitHub evicts the oldest caches within hours. Daily and weekly workflows saved large Rust caches that were gone before their next run and evicted the caches that pull request jobs restore. Workflows without a push trigger now restore a cache but do not save one, and the weekly release validation run saves nothing. PGO Validate no longer caches its fixtures of about 0.9 GB. Releases keep their caches. This change affects contributors only.

  • Rust pull requests get their CI result sooner. The nextest suite now runs in three Check jobs instead of two. Each job still builds every test binary, but it runs a third of the tests, so the slowest Check job, the last job of most pull request runs, finishes earlier. The same tests run. This change affects contributors only.

  • One rule now decides whether a run executes the duplication analysis. A run that names the analysis executes it. Without a name, the config key of the command decides (audit.dupes), and without that key duplicates.enabled decides. The bare fallow command, fallow audit, fallow_api::run_audit, fallow_api::run_combined, the language server and the health score all use this rule.

  • The maintainer plugin reference lists the Playwright config parsing and the correct plugin count. Thanks @​VariableVince for the report. (Closes #​4710)

  • The sticky PR comment states the verdict first, then the counts, then the details. The verdict line is followed by the counts per severity (19 findings: 4 errors, 15 warnings) and the gate line, before the finding tables. The gate line no longer comes after the footer. Each rule id links to its docs page, the location is one code span (src/a.ts:12), and the severity column uses error and warning, the same words as the review comments and the annotations.

  • The gate line and the request line are shorter. Gate outcomes: failed error-severity-findings (3 at or above error) (none of which fails this run) now reads Gates: failed error-severity-findings (3 at or above error). The job status states whether the run failed. The request line appears only when a request did not apply or applied over an empty scope.

  • Inline review comments are easier to read. Other locations: is now Also in:, a one-line range reads src/a.ts:3 and not src/a.ts:3-3, > Fix intent: is now **Fix:**, and the review body no longer repeats the mutation result in one line before the mutation section.

  • Duplicate code findings name the size of the clone. The CodeClimate description Code clone dup:7308a6eb (14 lines, 2 instances) is now 14 lines repeat in 2 places (clone group dup:7308a6eb).

  • The mutation section uses plain words. A partial run names its reason in words (the run reached its time budget), a survived mutant description puts the code in code spans (Changing `>=` to `>` in `isAdult` ), the count table leaves out the Not measured column when it is 0, and the section no longer says Scope: the changed lines. for the default scope.

  • The sticky PR comment puts the verdict in its heading. The heading is now Quality gate failed, Review needed or Quality gate passed, and the line under it names the report and the counts, for example Fallow combined report, 19 findings: 4 errors, 15 warnings. A reader who scans the pull request timeline sees the result first.

  • The mutation section of the PR comment and the review is two lines until a reader opens it. The partial-run line and the headline (12 mutants survived. Score 14.2%.) stay visible. The count table, the explanation, the lines without tests and the inspect command move into one Counts and details block. The job summary keeps every paragraph open.

  • A run with nothing to say says less. The PR comment and the review leave out the mutation section when no mutant was in scope. A passed gate names no measured value (Gates: passed error-severity-findings, health-findings.). A change scope that applied over an empty scope reads No changed file has code that fallow analyzes. Check the diff or the base ref of this run., and another narrowing request, such as a group selector, reads group-filter left nothing to analyze.

Deprecated
  • The fallow.diagnostics.statusBar setting has no effect. It controlled the separate eye button, which is gone. Use Hide findings in the editor in the menu of the Fallow status bar item, or the Fallow: Toggle Hide All Findings command.
Fixed
  • The GitLab CI template keeps the mutation results when the job fails. GitLab saves a job cache only after a successful job by default. A survived mutant or another error finding fails the job, so the job lost .fallow/mutation/results.json, and the next pipeline started the mutation run again from the start. A run that stopped at its time budget could then never continue. The template now saves the .fallow cache also when the job fails, the same as the GitHub Action saves its mutation cache. The mutation step also writes its cache stamp before the run, so the next run keeps the results of a job that stopped during the run.
    (Refs #​4383)

  • On Windows, the React Router .client and .server markers now apply in a workspace package. client-server-leak read a workspace package with the React Router plugin as out of scope, because its scope kept the backslashes of the Windows path. A *.client.* file in such a package was then no client root, and a *.server.* file was no server-only-import sink. A root project and macOS and Linux were not affected.

  • Imports in an inline HTML script are now in the graph. Fallow parses each inline script body that the browser runs. A module script gives static and dynamic imports, and a classic script gives dynamic imports. A package or a module that only an inline module script imports is no longer reported as unused. A script with a src attribute or a data type (JSON, import map, template) is not parsed, and a template placeholder such as {{ STATIC_URL }} in a specifier is skipped. (Closes #​4728)

  • An html tagged template of a local tag no longer gives unresolved imports. When a module binds html itself, for example export const html = String.raw, or imports it from a relative path, fallow reads its templates as plain text. A tag from a package such as lit or hono/html still gives asset imports. An unresolved asset of an html template now points at its src or href value, not at line 1, column 0. (Closes #​4729, #​4730)

  • The weekly fuzz smoke run completes inside its time limit. The scheduled run fuzzes each target for 300 seconds, one after the other, so it needs about 67 minutes. The job limit for a scheduled run is now 90 minutes. A push run keeps the 45-minute limit. A policy test checks that the job limit covers the fuzz time of all targets for each event. This change affects contributors only.
    (Closes #​4619)

  • fallow mutation runs one Vitest worker in each companion when VITEST_MAX_WORKERS is set. Vitest applies VITEST_MAX_WORKERS after the config options. An inherited value thus replaced the maxWorkers: 1 of the companion, and each companion started that many workers. With the default --concurrency, this multiplied the CPU and memory use. The Vitest companion now removes the variable before it starts Vitest, so --concurrency is the only control of test parallelism.
    Thanks @​DannyStreur for the report. (Closes #​4613)

  • constant-parameter follows a loaded value through ??, || and a ternary. Code such as const api = mod.default ?? mod; api.migrate() on a value from import(path) was an escape, so the rule skipped each exported function of the project. The rule now reads the result of the fallback when each branch is the loaded value or one member of it, and skips only the exported functions with a name that the code reads. An await of the loaded value also keeps it. A branch with any other value is still an escape. The extraction cache version goes up, so the first run after the update parses each file again.
    (Closes #​4594)

  • The VS Code extension opens the Settings editor in a way that cannot freeze it in Cursor. In Cursor, workbench.action.openSettings with a search query can freeze the Settings editor. These actions now run that command through runCommands:

    • the Fallow: Open Settings command
    • the "Open Settings" action after a failed binary download
    • the "Set Path" action when fallow-lsp is missing
    • the "Open Setting" action of Set Baseline at HEAD

    The Settings editor opens with the same query, and no result goes back to the extension. If the Settings editor does not open, a warning names the setting to search for. In VS Code, the actions do not change. (Closes #​4595)

  • A missing type-aware sidecar no longer fails the gate on findings that the type-aware pass can disprove. With typeAware.enabled: true, typeAware.require: best-effort (the default), and no fallow-type-aware sidecar, dead-code, audit and the bare run report unused-export, unused-type, unused-class-member and private-type-leak findings at warn, also under --fail-on-issues and --ci. Every other warn rule is still raised to error by these flags. Before, a Homebrew or cargo install binary reported these findings at error and exited 1, for example on a class method that only the type-aware pass sees as used. _meta.type_aware.executed stays false, the warning stays, and gate_outcomes gets a type-aware-fallback entry with status: skipped. A sidecar that starts and then fails or times out keeps the configured severities, and require: complete still exits 2. (Closes #​4606)

  • The Playwright plugin reads a reporter, globalSetup or globalTeardown value that a condition picks. A config such as globalSetup: external ? undefined : './setup.ts' made fallow dead-code report the setup and reporter files as unused. The plugin now reads each branch of a ? x : y, and the operands of a || x and a ?? x. A globalSetup array also gives each of its files. A template literal without expressions, such as `./setup.ts`, still counts.
    Thanks @​cr101 for the report. (Closes #​4620)

  • With includeEntryExports, the default export of a Playwright reporter, globalSetup or globalTeardown file counts as used. Playwright loads these files from the config and reads their default export. The credit also covers the TypeScript source of an ESM specifier, such as reporter.ts for ./reporter.js. Other exports of these files stay reported.
    Thanks @​cr101 for the report. (Closes #​4621)

  • A module-scope member read no longer credits a class binding of a function body. In function setup() { const Alias = new Foo(); } with a module-scope const Alias = E; Alias.One, the read Alias.One also credited Foo.One. The read now resolves only through the module-scope binding, so unused-class-members reports Foo.One and E.One stays credited. The order of the read and the function does not change the result. (Closes #​4603)

  • fallow security no longer reports a call of an inert local function as a library sink. Some rows match a callee by name only, for example request(url) for ssrf and x.merge(a, b) for prototype-pollution. When the module declares that function, or an object literal with that inline method, and its body runs no call and writes no member, the call cannot reach the library. The call is then not a candidate. A local function that runs a call still matches by name, because it can forward its argument to the library. When the module reassigns the function anywhere (request = got), writes a member of the object (utils.merge = _.merge), or passes the object to a call (Object.assign(utils, ...)), the call also stays a candidate. (Part of #​4611)

  • A type read through a namespace import of a JS module credits its declaration file. With import * as lib from "./lib.mjs" and the type reference lib.HelperOpts, the export HelperOpts of the sibling lib.d.mts no longer reports as an unused type under includeEntryExports. A usedExports rule of a framework plugin on the path lib.mjs now also credits that export in lib.d.mts. The same applies to a .js module with .d.ts and a .cjs module with .d.cts. (Closes #​4551)

  • fallow health --css credits declarations in nested CSS blocks. With
    native CSS nesting, these declarations now count:

    • a declaration in an @media, @supports, @container, @layer,
      @scope or @starting-style block inside a style rule;
    • a declaration after a nested rule, as in .a { &:hover {} color: red; }.

    A @keyframes or a font family that only these declarations use is no
    longer reported as unreferenced. A rule with only such declarations no
    longer counts as empty. The totals of declarations and !important
    declarations now include these declarations. They also feed the raw style
    values, the design-token counts and the custom-property definitions, so an
    upgrade can show new findings for them.
    Thanks @​Smrtnyk for the report. (Closes #​4612)

  • hardcoded-secret no longer reports sentences and public URLs. The entropy check now skips a value of three or more words with no token-shaped word, such as an error message or a SQL statement under a key that contains token or credential. It also skips an http or https URL without user information, a query, a fragment or a high-entropy path piece, such as an OAuth token endpoint or a help link. A header value such as Authorization: Bearer <token>, a URL with user:pass@ or a ?token= query, and a webhook URL with a secret path piece stay candidates. Provider token shapes do not use these filters. Thanks @​Smrtnyk for the report. (Closes #​4610)

  • unused-class-members follows a Durable Object binding of the Worker Env. A method call on a Durable Object stub now credits the method of the Durable Object class. The stub can come from the env import of cloudflare:workers, or from this.env in a class that extends DurableObject<Env>, WorkerEntrypoint<Env> or WorkflowEntrypoint<Env>. An inline call such as env.ROOM.getByName(name).join() also gives credit. Fallow reads the binding types from the worker-configuration.d.ts file that wrangler types writes. In a monorepo, each Worker package uses the nearest of these files. A st

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@coderabbitai

coderabbitai Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: f8e1e965-e848-4531-b781-6ef1d9c65aeb

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@socket-security

socket-security Bot commented Nov 16, 2026 •

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.2100 +110010096 +1100

View full report

@pkg-pr-new

pkg-pr-new Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/node-modules/urllib@983

commit: 8971255

@codecov

codecov Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.91%. Comparing base (c53cbba) to head (8971255).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #983   +/-   ##
=======================================
  Coverage   94.91%   94.91%           
=======================================
  Files          10       10           
  Lines         747      747           
  Branches      235      235           
=======================================
  Hits          709      709           
  Misses         35       35           
  Partials        3        3           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@renovate
renovate Bot force-pushed the renovate/fallow-3.x-lockfile branch 2 times, most recently from c316214 to 0095d73 Compare November 17, 2026 23:47
@renovate renovate Bot changed the title chore(deps): update dependency fallow to v3.43.0 chore(deps): update dependency fallow to v3.43.1 Nov 17, 2026
@renovate
renovate Bot force-pushed the renovate/fallow-3.x-lockfile branch from 0095d73 to 8971255 Compare November 20, 2026 07:12
@renovate renovate Bot changed the title chore(deps): update dependency fallow to v3.43.1 chore(deps): update dependency fallow to v3.43.2 Nov 20, 2026
@fengmk2
fengmk2 merged commit 140efda into master Nov 20, 2026
20 checks passed
@fengmk2
fengmk2 deleted the renovate/fallow-3.x-lockfile branch November 20, 2026 07:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant