Version updated for https://github.com/fallow-rs/fallow to version v3.9.1. This action is used across all versions by 349 repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. Action Summary This GitHub Action automates static code analysis for TypeScript and JavaScript projects by identifying unused files, circular dependencies, duplication, complexity hotspots, boundary violations, and design-system styling drift. It provides deterministic findings with typed output contracts and can be integrated into CI workflows to ensure code quality before deployment. The action supports various formats and integrates with popular development tools like LSP servers for language-specific analysis.

Version updated for https://github.com/fallow-rs/fallow to version v3.4.2. This action is used across all versions by 307 repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. What’s Changed Suppression governance fallow suppressions: a read-only inventory of every active suppression marker, grouped per file with line, kind, level, and reason, plus project totals and a stale count cross-referenced from this run’s findings. Teams governing tech debt (and agents that should distrust a “clean” verdict) no longer grep for fallow-ignore by hand. Ships with --format json (new suppression-inventory envelope) and full workspace/changed/file scoping; always exits 0. MCP tool list_suppressions exposes the same inventory to agents on the MCP surface, returning the JSON envelope verbatim. Every “To suppress:” hint in the human footer now names a token fallow actually parses. Eight sections printed tokens the parser does not recognize, so following the hint suppressed nothing and then surfaced a stale-suppression finding on top. Hint tokens now derive from the issue registry, backed by a roundtrip guard test. Thanks @slyeargin for catching the unused-files case in #1820. Native GitHub workflow output --format github-annotations and --format github-summary: inline PR annotations (::error / ::warning / ::notice workflow commands) and job-summary markdown straight from the CLI, no bundled action required. Both are log-based, so they render on fork PRs without a write token. fallow report --from <results.json>: analyze once with fallow --format json -o results.json, then render annotations and the job summary from the saved envelope, byte-identical to the direct run. Monorepo CI paths Behavior change: CI-facing formats emit repository-root-relative paths when --root is a subdirectory. GitLab’s Code Quality widget matched nothing and inline review discussions were rejected when the analyzed project lived in a package subdirectory, because codeclimate, review-github, and review-gitlab addressed files relative to --root. All CI formats now share one namespace, detected via the git toplevel; pass --report-path-prefix '' to restore the old output. Single-package repositories are unaffected. See docs/backwards-compatibility.md for the classification rationale. --annotations-path-prefix is now --report-path-prefix and governs every CI-facing format; the old name keeps working as an alias. --diff-file resolves the diff’s path namespace from the diff itself, so changed-file filtering works in monorepo packages for both git diff conventions; a diff that parses but touches no analyzable files filters to zero findings, and an unplaceable diff warns and reports at full scope instead of producing a plausible-looking empty report. Renamed files keep their old_path in review-gitlab. Thanks @Jerc92 for the diagnosis and the patch in #1808. unused-class-members accuracy Four extraction gaps produced false positives on dependency-injection-style code, reported across three issues by adopters running the rule on real codebases:

Version updated for https://github.com/fallow-rs/fallow to version v3.2.0. This action is used across all versions by 252 repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. What’s Changed Health: a configurable “function too big” threshold, surfaced in the summary This release makes the unit-size (large-function) check configurable and reports the effective ceiling in the health output. health.maxUnitSize: raise the large-function bar instead of switching it off The line count at which a function is reported as an oversized “large function” was hardcoded to 60 LOC. That made test suites noisy: a describe() callback spans hundreds of lines, and each large it() body trips the threshold too. The only escape was health.ignore, which drops every health signal (complexity, CRAP, hotspots) for those files, so you lost complexity checking on your test code as well.

Version updated for https://github.com/fallow-rs/fallow to version v2.104.0. This action is used across all versions by 235 repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. What’s Changed Highlights This release is heavy on CSS intelligence. fallow health --css now understands CSS-in-JS (styled-components, emotion, linaria, vanilla-extract, StyleX, Panda) as first-class, ships a second styling-health quality axis, and adds a design-token blast-radius index. Plus a staged human review walkthrough, an opt-in unused-prop exemption, and a batch of framework false-positive fixes.