Repository navigation
chore(deps): update dependency fallow to v3.42.0 - #980
Merged
Merged
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
commit: |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #980 +/- ##
=======================================
Coverage 94.77% 94.77%
=======================================
Files 10 10
Lines 746 746
Branches 235 235
=======================================
Hits 707 707
Misses 36 36
Partials 3 3 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
fengmk2
approved these changes
Nov 13, 2026
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.
This PR contains the following updates:
3.41.0→3.42.0Release Notes
fallow-rs/fallow (fallow)
v3.42.0Compare Source
Added
fallow coverage upload-inventory --with-callersnow finds the entry routes of Elysia and TanStack Router projects. A TanStack Router route file takes its pattern from the string argument ofcreateFileRoute("/repo/$repo"), withmethod: null. An Elysia route comes from a call such asapp.get("/repos/:repo", handler). The pattern joins theprefixof the instance, the.group()prefixes and the prefixes of the apps that mount the plugin with.use(). The file of the handler is the route entry. A route with a path or a prefix that is not a string literal is not uploaded. The route caps and therouteLimitsheader do not change. (Closes #4271)The GitHub Action and the GitLab template can run
fallow mutation. Set the inputmutation: true(GitLab:FALLOW_MUTATION: "true"). AResolve change scopestep (GitLab: an inline block) writes one root-relative diff first. Then the mutation run uses that diff, before the analysis, because the run refuses a dirty worktree. The default scope is the changed lines of the pull request, with a10mtime budget. The inputsmutation-scope,mutation-time-budget,mutation-max-mutantsandmutation-min-score(GitLab:FALLOW_MUTATION_SCOPE,FALLOW_MUTATION_TIME_BUDGET,FALLOW_MUTATION_MAX_MUTANTS,FALLOW_MUTATION_MIN_SCORE) set the run.fallow reportrenders the results (see the next entry). A failedmutation-min-scorefails the job with exit code 1, and a tool failure of the run (exit code 2) fails it with exit code 2, after the comment. The step runs only for a job that cannot run the code of a fork with the secrets of the base project: on GitHub, thepull_request,push,schedule,workflow_dispatchandmerge_groupevents; on GitLab, not a fork pipeline in the target project. It removes the CI tokens and theGITHUB_*file commands from the environment of the tests, and it never passes--allow-dirty. The result cache goes throughactions/cacheand the GitLab job cache, with a key that covers the lockfiles and the runner config. A fork pull request never saves the cache. With a fallow that cannot render the results, the gate still fails the job, and the job summary names the version that renders them.fallow ci-template gitlab --vendoralso writesci/scripts/mutation.shandci/scripts/mutation_common.sh.fallow mutationmakes more mutants with the existing operators. The new rules are:ifor? :test that is a comparison or a logical expression now becomestrueandfalse. A loop test of this kind becomesfalseonly, andfor (;;)gets the testfalse. A constant that the test always has, such astrueforitems.length >= 0on an array, gives no mutant;&&that is a comparison or a!xbecomestrue, and such an operand of||becomesfalse;a === bbecomestrueas well asfalse. A==or===loop test gets notrueconstant;regex-literalremoves a+,*or?quantifier, shortens{n,m}to{n}, and removes an anchor at the start or end of a group or an alternative. A removal that would join two tokens, as in\1?2, puts(?:)in the place of the quantifier, and a mutated literal that does not parse is dropped;return-valuechanges the concise body of an arrow function toundefined;arithmetic-operatorswaps*=and/=,<<=and>>=,&=and|=, and changes%=to*=.logical-operatorswaps&&=and||=, and changes??=to&&=;unary-operatorswaps-xand+x, and removes~;string-literalempties a template literal and fills an empty one. A tagged template gives no mutant.The operator names do not change. An existing mutant keeps its id. A mutant that two rules make is one mutant.
fallow mutation --typechecknow adds an equivalence hint to an optional-chaining survivor. The mutantsa?.btoa.b,a?.()toa()anda?.[k]toa[k]change nothing whenais never nullish at run time. When the declared type ofaexcludesnullandundefined, the survivor getsequivalence_hint: "type-non-nullish". The hint is advisory. The mutant stayssurvivedand stays in the score. The human report andfallow mutation tasksshow a one-line note, and a verdict file (--verdicts) records the mutant as equivalent after review.typecheck.hintedcounts the hinted survivors. The hint needsstrictNullChecksandnoUncheckedIndexedAccess. A verdict for a hinted survivor removes the hint. The hint can be wrong, for example in a method that loses itsthis.fallow mutation --time-budgetnow runs the cheapest mutants first. With a time budget, the first pass starts the mutants with the lowest estimated test time first. The estimate is the sum of the dry-run times of the covering tests. The budget now settles more mutants. Without a budget, the order does not change.fallow mutation --mutants-per-line <n>limits the mutants on each source line. The config key ismutation.mutantsPerLine. The plan keeps the most productive mutants of a line, in a fixed operator order, and ranks equal operators by a stable hash of the mutant id. The other mutants arependingwith the reasonsampled-out, and the run does not execute them. The summary and the plan counts give the number assampled_out. The completion of such a run ispartialwith the reasonsampled-out. A consumer that switches oncompletion.reasonsmust accept this new value. The MCPmutation_plantool takes the same limit asmutants_per_line.fallow mutationnow warns about skipped and todo tests. A test file can leave a test out of the run, for example withit.skip. Such a test checks nothing. When the changed-code scope changes a runner test file, a scan of the syntax tree finds these tests. The run reports them inerrorswith the codeskipped-tests, with file, line and name, and the human output shows a warning. A change to the tests alone starts no runner. A run with--allor paths gives no such warning. The completion does not change.fallow mutation --function-scopewidens the changed lines to whole functions. The config key ismutation.functionScope. A change to a parameter or a signature line holds no mutant, so the default changed-code scope can select nothing for it. With the option, each added line selects all mutants of the function that holds it. The option is off by default.fallow mutation exportwrites a saved report in the openmutation-testing-report-schemaformat. Mutation dashboards and HTML report viewers read this format, so a team can keep its dashboard. The command runs no code. It maps each Fallow status to a schema status:flaky,prunedandequivalentbecomeIgnoredwith a reason,pendingstaysPending, and a survivor of a partial run gets a reason that says the result is not conclusive. Columns count UTF-16 code units. The export refuses a report whose mutated files changed after the run.Built-in gulp plugin. When a package depends on
gulporgulp-cli, fallow makes itsgulpfilean entry point. This includesgulpfile.{js,mjs,cjs,ts,mts,cts,babel.js,esm.js}and theindexfile of agulpfile.jsdirectory. The task files that a gulpfile imports are no longer unused files.Built-in n8n plugin. n8n loads the nodes and credentials of a node package from the
n8n.nodesandn8n.credentialsarrays inpackage.json. Fallow now makes these files entry points, so node files, credential files and the files that they import are no longer unused files. Each path names build output, such asdist/nodes/Foo/Foo.node.js. Fallow maps it to the source file through thetsconfigoutDirandrootDir, or to the source file beside the output directory when norootDiris set. The members that n8n reads from a class that implementsINodeTypeorICredentialType, such asdescription,webhookMethodsanddocumentationUrl, are no longer unused class members.Built-in unplugin-icons plugin. An icon import such as
import IconX from '~icons/lucide/x'orvirtual:icons/mdi/arrow-leftis no longer an unlisted dependency~icons. The import also credits the icon set package (@iconify-json/lucide), the full@iconify/jsoncollection andunplugin-icons, when the project declares them. Before, fallow reported these packages as unused dev dependencies.Built-in vite-plugin-pages plugin. Fallow now reads the
Pages(...)call invite.config.*and makes the page files under eachdirsentry entry points. Adirsentry can be a string or an object withdir, and can point into another workspace package ("../common/src/pages"). Withoutdirs, the page directory issrc/pages. Theextensionsoption sets the page file extensions. Before, fallow reported the page files and the files that only pages import as unused files.Built-in SolidStart plugin. The
solid-startplugin activates from the@solidjs/startdependency. It makes<appRoot>/app.{tsx,jsx},<appRoot>/entry-client.{tsx,jsx},<appRoot>/entry-server.{tsx,jsx}and each module under<appRoot>/<routeDir>entry points. Before, fallow reported these files and all the modules that they import as unused files. Route files get thedefault,routeand HTTP method exports. The plugin readsappRoot,routeDir,extensionsandmiddlewarefrom thesolidStart()call invite.config.*and fromdefineConfig()in the version 1app.config.*. The defaults aresrcandroutes.Built-in dumi plugin. The
dumiplugin activates from thedumidependency. It makes each demo file that a<code src="...">tag of a Markdown file names an entry point, and credits itsdefaultexport. Before, fallow reported these demo files as unused files. A relativesrcis read from the directory of the Markdown file, and asrcthat starts with/from the package root. Fallow now also analyzes the hidden.dumidirectory: the themebuiltins,slots, layouts andplugin, thepagesroutes and theglobal,appandloadingfiles are entry points. The plugin reads.dumirc.tsand.dumirc.js: it credits the imported packages and thepluginsandpresetspackages, and it readsaliasas path aliases.fallow reportrenders mutation results for CI. The new flags--mutation-report <PATH>and--mutation-not-run <REASON>work with the pr-comment, review,github-summary,github-annotationsandcodeclimateformats. Survived mutants on changed lines appear as findings with the rulefallow/mutation-survivedin the new Tests category: rows in the sticky comment, annotations, inline review comments and Code Quality entries, 20 at most for each render. The comment, the review summary and the job summary get one "Mutation testing" section, and the check run gets amutationrow and amutation-min-scorerow. A survivor in a file that changed after the run is not shown. Without the flags, the output offallow reportdoes not change.fallow mutationwrites its score gate into the report. A run with--min-scoreormutation.minScoreaddsgate_outcomes["mutation-min-score"]to themutationreport, and exit code 1 reads that entry. Thegates-*outputs of the Action and theFALLOW_GATES_*lists of GitLab name the gate. The Action has the new outputmutation-report-rendered.fallow mutationhas nine opt-in operators. They run only when--operators,mutation.operatorsor the MCPoperatorsparameter names them:block-statementremoves the statements of a block or function body without declarations;array-literalchanges[x]to[]and[]to["fallow"];object-literalchanges a non-empty object literal to{};method-expressionswaps method pairs such asstartsWithandendsWith, and removes calls such as.trim()and.filter(...);switch-caseremoves the statements of a clause;call-expressionchanges a call in an expression position to(void 0);throw-statementremovesthrow new X(...);regex-constructorapplies the regex changes to anew RegExp("...")pattern;regex-assertionnegates a lookaround and swaps\band\B.The default set does not change.
docs/mutation-testing.mdlists both sets.Changed
The warning for a config glob that matches fewer files since 3.34.0 now names the files and gives two fixes. Since 3.34.0, a single
*or?in a config path glob matches in one folder level only. The stderr warning for a glob that lost files gave only a count and a**rewrite. Now it names up to 3 of the lost files, then "and N more". It also tells you how to keep the one-level meaning: write the names in place of*, for example{name1,name2}. This config change stops the warning. The**rewrite stays as the second choice. ForentryanddynamicallyLoaded, a lost file that another entry source declares, for example a plugin orpackage.json, does not count, because it is still an entry point. When no lost file remains, fallow prints no warning. Only the commands that find entry points, for examplefallow dead-codeandfallow health, check these two fields. The warning stays on stderr,--quiethides it, and JSON output does not change.fallow mutationstops an endless loop through the active mutant in under a second. Before, a synchronous endless loop blocked the Vitest worker until the watchdog fired aftertimeout_ms(5 seconds or more). Then Fallow started a new companion and a new dry run, and the retry waited twice as long. Now the mutant switch checks a loop budget of1.5times the covering-test time plus 500 ms, and the Vitest adapter reports the test as atimeoutin the same companion. On three public Vitest libraries, a full run with 2 workers took 1.7 to 6 times less wall time, and the score did not change. A mutant that only makes a test slow, for example under host load, can now gettimeoutin place ofkilledorsurvived. The retry with a doubled budget lowers this risk. Only the Vitest adapter checks the loop budget.(Part of #4341)
fallow mutationstops more endless loops in the companion, and gives a loop timeout of short tests no retry. The loop check now counts each evaluation of an instrumented site in a mutant run, not only the evaluations of the active mutant. So a mutant that makes a loop of other source code run forever, for example areturnthat givesundefinedto the condition of a caller loop, also ends at the loop budget. The loop budget of a mutant run now counts the CPU time of the test thread, not the wall time. A test that waits uses no budget, and load from other processes on the host does not count. A loop timeout of covering tests that take 200 ms or less in the dry run is final: the budget is then at least four times the work of the tests. Before, each such mutant ran a second time with twice the budget.(Part of #4341)
fallow mutationruns the test files of one Vitest mutant run in one worker. Vitest starts a new worker for each test file of a run when module isolation is on. After the dry run, the Vitest adapter now runs the test files once more in one shared worker. When each test gives the same result, the mutant runs of the companion use one worker for all of their test files. Each run still starts a new worker, so the modules stay fresh for each mutant. A test that needs a fresh worker for each file makes the two dry runs differ, and the runs then stay isolated. A kill in a later file of a shared worker counts only when the file also detects the mutant alone. On a public Vitest library, where a mutant has covering tests in almost three files, this cut the worker processes by a quarter, and no verdict changed.(Part of #4341)
fallow mutationkeeps one Vitest worker process for many mutant runs. Vitest starts a new worker process for each run, and that start cost more CPU than most mutant runs. When the dry run gives the same results in one reused process, also when each module loads a second time, the Vitest adapter now keeps the worker process between mutant runs. Each test file of a reused run loads the source modules again with the current mutant. A run whose tests change state outside the modules (a global, a prototype,process.env, a listener, a timer) ends the process, and a kill in such a run counts only when the test file also detects the mutant in a new worker. Dry runs, control runs and--kill-matrixruns still start a new worker. On three public Vitest libraries, the CPU time of a full run went down by a factor of 1.6 to 3.0, and no verdict changed.(Part of #4341)
arithmetic-operatorskips*,/and%with a string or template operand, as it already did for+and-.Fixed
fallow dead-codecredits a member on a method chain with arguments on a typed parameter. Infunction toWorld(local: Point) { return local.rotate(1).translate(1, 1); }, whererotate(angle: number): Point, fallow now creditsPoint.translate. Anew Point(...)local and a chain without arguments already gave this credit. Thanks @Smrtnyk for the report.(Closes #4311)
fallow dead-codecredits a member on the return value of an inherited method in a class that is not exported. Inclass Viewer extends Floor, whereFloordeclaresfind(): Table | undefinedin another file,this.find()?.setVip()now creditsTable.setVipalso whenVieweris not exported. A deeper chain of unexported classes also gives the credit. A class on the chain that declaresfind()itself gives no credit to the base. Thanks @Smrtnyk for the report.(Closes #4312)
fallow dead-codecredits a member on an element of an array that a local function returns. Withfunction all(): Table[]in the same file, fallow now creditsTable.setVipforfor (const table of all()),all().forEach((table) => table.setVip()),all()[0].setVip(), andconst tables = all(); for (const table of tables). The function can come before or after the reads. A call of a nested declaration or a catch parameter namedall, and a call in a namespace body, gives no credit. The extraction cache version is 422. Thanks @Smrtnyk for the report.(Closes #4313)
fallow mutationreports tests that share a test ID. Two tests of one file that ran, with the same full name (for exampletest.eachwith a title that has no placeholder), get the IDsnameandname (2)in report order, so the evidence of these IDs can belong to the other test. The dry run now reports them in aduplicate-test-idsentry oferrors(a warning in the human output), and the run goes on. A skipped or todo twin makes no duplicate.--kill-matrix-forwith a test ID target that names a duplicate ID exits2withFALLOW_MUTATION_TARGET_DUPLICATE_TEST_ID. A test file target drops the duplicate IDs and keeps its other tests.(Closes #4170)
fallow auditkeeps acss-duplicate-blockfinding inherited when only the lines of a later occurrence move. Before, a script or template edit that shifted the copy of a block in the second file of a group made the finding introduced, although the group and its count did not change. The audit key of a duplicate block finding now uses the sorted paths of all occurrences of the group, not the path of the occurrence that the changed-file scope names first. A new file that joins the group still gives an introduced finding. Thanks @Smrtnyk for the report. (Closes #4344)fallow dead-codeuses the element class of afor...ofloop variable only in the loop body. Afterfor (const t of tables)withtables: Table[], a parametertof another type in another function no longer creditsTablemembers. This applies also to a loop over a call, such asfor (const t of all()).(Closes #4352)
fallow dead-codeno longer credits a member throughthisin a function with its ownthis. In a nestedfunctionor an object-literal method inside a class method,this.find().setVip()no longer creditsfindorsetVip. An arrow function keeps thethisof the method and still gives the credit. A function that the code gives the instance also keeps the credit:.bind(this),.call(this)or.apply(this)on the function or its name, a call that also passesthis(such asitems.forEach(function () {}, this)), a method call onthis(such as the listener inthis.on("ready", function () {})), an assignment to athis.<field>or a class field, and athisparameter with a named type. The extraction cache version is 423.(Closes #4351)
fallow mutationnow selects a test that asserts only on the output of a Node child process. With the Vitest andnode:testrunners, a Node process that a test starts (spawn, exec, execFile or fork) now gives its coverage hits to that test in the dry run. Before, such a test had no hits, so the run did not select it for a mutant. When no other test file detected the mutant, the report showed a false survivor. A child process that a signal ends gives no hits.(Closes #4171)
A crafted TOML file no longer crashes fallow. A
fallow.toml, an external plugin file, or a TOML file that a framework plugin reads (bunfig.toml,mise.toml,wrangler.toml,.prettierrc.toml, GraphQL config) could crash any command with a stack overflow. Fallow now rejects TOML that nests arrays and inline tables deeper than 128 levels before it parses the file. A rejected config file gives a parse error. A rejected plugin file is skipped, as with other invalid TOML.A crafted stylesheet can no longer make
fallow dead-codeorfallow health --csshang. The CSS parser parsed the content of some unclosed color functions such aslight-dark(twice at each level, so the parse time doubled with each nested function. Fallow now skips the structural CSS parse of a stylesheet that nests more than 8 color functions. CSS Modules classes in such a file come from the plain class scan, and the file gets no CSS analytics. Real stylesheets are not affected.A crafted TypeScript, JSX or MDX file can no longer make
fallowhang. Some sources with many nested<characters made the TypeScript parser try each nested part again and again, so one small file could keepfallow dead-code,fallow dupesor MDX extraction busy for minutes. Fallow now counts this nesting before it parses a file. A file past the cap is reported as a failed parse, the same as a file with too-deep bracket nesting. Real code stays well below the cap, so its results do not change.fallow health --csskeeps a.scssor.lessfile with an absoluteurl()incss_analytics. Before, the Sass and Less lowering read the//ofurl(//cdn.example.com/a.png),url(https://...)orurl("//...")as a line comment, so the file lowered to nothing and dropped out of the analytics. As in Sass, a//inside a string or an unquotedurl(), or after a:, is now part of the value. A//or a quote inside a/* */comment no longer hides the end of that comment or a later line comment. Thanks @rezamuliawijaya for the fix. (Closes #4324)The LSP offers the remove-export quick fix for a name with a combining mark. JavaScript allows a combining mark after the first character of a name, for example
caféwritten as anefollowed by the character U+0301. The quick fix read the name only up to the mark, so it gave no action for such an export. It could also give the action for an exportcafeon that line. The quick fix now reads a name with the identifier rule of the parser. The "Dismiss optional prop review" action uses the same rule, so it no longer adds a comment for a longer name that only starts with the prop name.LSP diagnostics on the first line of a file with a UTF-8 byte order mark start at the correct column. The editor buffer does not hold the byte order mark, but the LSP counted the mark when it read the file from disk. Thus diagnostics on line 1 started 2 columns too far to the left, and a config diagnostic on line 1 started 1 column too far to the right. Also, an open file with a byte order mark never matched its file on disk, so the LSP did not publish its diagnostics. The LSP now drops the leading byte order mark when it reads a file.
Duplication results count lines and columns from the end of the byte order mark. The duplication detector read a file with its UTF-8 byte order mark, so a clone on line 1 started 1 column too far to the right in the CLI, JSON and LSP output. The detector now drops the mark, the same as extraction. The duplication token cache version changes, so a warm cache does not give the old columns.
A file that starts with two U+FEFF characters gets correct spans. Only the first U+FEFF of a file is the UTF-8 byte order mark. The second U+FEFF is source text. Extraction removed both, so each span of the file was 3 bytes too early. For
\u{feff}\u{feff}export const a0 = 1;, the span ofa0heldst. Extraction now removes the mark one time only. The extraction cache version and the graph cache version change, so a warm cache does not give the old spans.A Glimmer argument that only a
<template>block reads counts as used in a file with a byte order mark. In a.gtsor.gjsfile with a UTF-8 byte order mark, the template ranges counted the mark and the parser spans did not. A template at the end of its class then fell outside the class, so its argument reads did not count.CodeClimate clone fingerprints no longer change with CRLF line endings. The CodeClimate fingerprint of a clone instance hashes the first 64 characters of the clone fragment. Before, these characters kept each
\r, so a Windows checkout withcore.autocrlfgave other fingerprints than a Linux checkout of the same code. GitLab Code Quality then reported each clone as new and as fixed. Thereview-github,review-gitlab,pr-comment-githubandpr-comment-gitlabformats merge and sort by this fingerprint, so their output changed too, infallow dupesand infallow audit. The hash now leaves out\r. Files with LF line endings keep their fingerprints. A project with CRLF files gets new fingerprints one time, and they then match the fingerprints of an LF checkout. When two clone groups share onedup:hash, the order of their-r1and-r2suffixes also no longer changes with the line endings. Thefallow auditclone-group key also leaves out\r, and the audit base snapshot cache moves to version 21.A test runner or a bundler in the root
package.jsonnow activates its plugin in a workspace. A monorepo often declares a tool such as Mocha or Vite only in the rootpackage.json. The package manager hoists it, and a workspace script such asmocha --exitorvite buildcalls its binary. Before, the plugin of a workspace became active only for a dependency of that workspace. The test files of the workspace and the files that itsindex.htmllinks were then reported as unused files. A root dependency now activates its plugin in a workspace when a script of that workspace calls the binary of the dependency. A root dependency that no workspace script calls does not activate a plugin in the workspace.fallow dead-codecredits a member on the result of an awaited async static factory. Withstatic async create(): Promise<Service>in another file,const service = await Service.create(); service.getConflicts()now creditsService.getConflicts, asService.build()withstatic build(): Servicealready did. The factory can build the instance in a local before it returns it.fallow dead-codecredits a member on an element of a typed array field of a class in another file. Withdays: Day[]onMonth, fallow now creditsDaymembers form.days[0].getFirst(),m.days.some((day) => day.flag)andfor (const day of m.days), wheremis a parameter typedMonth. The same is true forthis.days[0]?.getFirst()inMonth, and for a getter or a method that returns an array (get sorted(): Day[]). The extraction cache version is 427.fallow dead-codecredits a member of a page object that a Playwright fixture reaches through a property. With the fixtureapp: AppPageandreadonly details: DetailsPageonAppPage,app.details.getParameter()in a test now creditsDetailsPage.getParameter. A longer chain (app.details.input.select()) also gives the credit when each property has a declared type or anewinitializer. The chain also credits each property that it reads:detailsonAppPageandinputonDetailsPage.fallow dead-codecredits a member on an element of an array that a function in another file returns. Withexport const make = (): Sheet[] => ..., fallow now creditsSheetmembers formake().forEach((sheet) => sheet.member),for (const sheet of make())andmake()[0].member, and for the same reads through a localconst sheets = make(). A function that returns one instance gives no credit for a read on an element of its result.React Router route files that an imported module declares are now entry points. A
routes.tsfile can import route arrays from other local modules and spread or merge them, for example[...coreRoutes]ormergeRoutes(coreRoutes, extendedRoutes). The React Router plugin read only the expressions inroutes.tsitself.fallow dead-codethen reported the route files of the imported modules as unused files, and also each file that only these route files import. The plugin now follows spread elements, named and default imports from relative specifiers,export { a as b },export { a } fromandexport * from. A.jsspecifier that names a TypeScript source also resolves. Route file paths in an imported module stay relative to the directory ofroutes.ts, the same as React Router resolves them.React Router route files with brackets in their path are now entry points. The plugin used each route file path as a glob pattern. A segment such as
[workspaceSlug]then matched one character and not the directory with that name, sofallow dead-codereported the route file as unused. The plugin now escapes the path before it makes the pattern.A warm run keeps its cache hits when the extraction cache is near its size limit. All entries that one run sees get the same seen stamp. When a save went past 80% of the limit, eviction removed entries down to 60% of the limit, also entries of the latest run. The next run parsed those files again, and the save removed the same entries again. On a project with a working set a little over 80% of the limit, each warm run parsed about 40% of the files again. Eviction now removes the entries that the latest run did not see down to 60% of the limit. It removes entries of the latest run only down to the limit itself. A working set that fits in the limit now stays in the cache, so
.fallow/cache.bincan stay near the full limit.Clone locations are correct on a line with non-ASCII text. The duplication detector gave
start_colandend_colas character counts, but the LSP read them as byte columns. Thus a non-ASCII character before a clone on the same line moved the clone diagnostic and hover in the editor. The detector now gives byte columns, the same as the other analyses. A consumer that read these JSON fields as character columns must change. (Closes #4378)SARIF region columns now count UTF-16 code units. A SARIF run without
columnKindcountsstartColumnin UTF-16 code units. Fallow gave the byte column plus 1, so on a line with non-ASCII text before a finding, a code scanning view showed the finding too far to the right. All SARIF output now converts the column with the source line: dead code, dupes, health, security, flags, flag retirement andfallow report --from. A byte order mark on line 1 does not count. The fingerprints keep the byte column, so existing alerts keep their identity. JSON column fields do not change. (Closes #4405)The changed-code scope of
fallow mutationdetects renamed and copied files. Before, the scope counted each line of a copied or moved file as new code, so unchanged copied lines got mutants. Now, when Git detects the source of a copy, only the edited lines of the copy are in scope. A new file stays in scope. A diff that you supply keeps its literal meaning. (Closes #4364)fallow mutationkeeps the scope of a diff that you supply. Before, when the paths of an explicit patch did not match the project, the run used a generated Git diff in its place. Now the CLI exits with code 2 and a structured error before any test runs. A patch on stdin and--diff-file -keep their hunks, also when the scope is empty.A wildcard
exportstarget in build output now maps to its source files. A package with"./*": "./esm/*.mjs"or"./*": "./dist/*.js"exports each file undersrc/, but fallow matched the target only against files on disk. Thus the public subpath files were unused files, and their exports were unused exports. A wildcard target now follows the rule of a single package entry: the lastdist,build,out,esmorcjsdirectory becomessrc, and a JavaScript output extension becomes each source extension. Alibtarget maps intosrconly when it matches no file. A target at the package root such as./*.jsmaps intosrc. Whensrchas a match, the target still matches the files directly in the package root, but not the files in other directories such asscripts/. The root package of a project now also expands its wildcardexportstargets, and a match skips the files of nested packages that have aname.Plugin entry points apply again in a monorepo with 200 or more workspaces. All plugin entry globs compiled into one glob set, with a copy for each workspace package. With 200 or more workspaces, the set went past the size limit of the glob engine and did not compile. Then no plugin entry point applied, and
fallow dead-codereported test files, pages and config files as unused. Fallow now groups the globs by their literal directory prefix and compiles each group on its own.An import into the unbuilt output folder of a workspace package now resolves to the source file. A deep import such as
lib/dist/util, and arequireof a package root whosemainnames unbuilt output in a customoutDir, were unresolved. The imported source file was then reported as unused. Fallow now maps these paths with the same output-to-source rules as amainorexportstarget. The tsconfig output map also applies each parent of an arrayextendsin order, and matches a packageextendssubpath against*patterns inexports.Workspace entry point paths no longer keep a
./segment.fallow list --entry-pointsshowedpackages/a/./index.jsfor the entry./index.jsof a workspace package. The path is nowpackages/a/index.js, the same as in the other reports.fallow mutation inspectandfallow mutation tasksshow the code of a mutant in a file with a UTF-8 byte order mark. The run instruments a file without its byte order mark, butinspectandtasksinstrumented the file with the mark. Thus each mutant of such a file wasstalewithmutant-not-reproduced. They now drop the mark first.return-valuenow mutates a concise arrow body that is a call, such as() => save(). Before, such a body got no mutant.A branch or operand constant now gives no equivalent mutant through
!.!(items.length >= 0) || flagon an array no longer givesfalse || flag.A mutant at the start of an expression statement now keeps the grouping of the rest of the statement. The guard against a join with the line before is now
void 0,, notvoid. Before,!x ? a() : b();becamevoid (x) ? a() : b()in the report and always ranb(), andf() ** 2;gave a syntax error. Thereplacementand themutant_idof such a mutant change. A verdict for its old id becomes unmatched, so review it again.fallow cloud loginstates the owner rule once when a member approves the code. Before, the message printed the reason from Fallow Cloud and then the same rule again from the CLI. The message now says once that only an organization owner can approve a key, and it names where to create one.The API keys links of
fallow cloud loginandfallow cloud logoutfollow the cloud that the login uses. Before, they always pointed tofallow.cloud, also with a custom--api-url. The link now uses the dashboard address that the cloud returns for the login, when that address is on the host of the API. Otherwise it uses<host>for an API atapi.<host>, or names the Settings page without a link. The CLI never prints a link with userinfo, a backslash, or plainhttpoutside loopback, so a cloud cannot make the link open another site. The login line also drops control characters from the address and the code that the cloud returns.fallow mutationsuggests--concurrency 1when a restarted companion fails in a parallel phase. Tests or a runner config that share files on disk can fail when workers run in parallel. The hint applies to init and dry-run failures and to missing covering tests. The original error and the timeout guidance stay. A serial phase keeps its diagnostics. (Closes #4363)Security
The MCP server requires
rmcp3.9 or later.rmcp3.8.0 has the advisory RUSTSEC-2026-0462, unbounded response buffering in the Streamable HTTP clients. The Fallow MCP server uses stdio and does not enable these client transports, so it was not exposed. The update clears the dependency audit.migrate,rule-pack init,coverage setupandci-template gitlab --vendorno longer write through a symlink that leaves the project. A cloned repository could commit a file or directory that one of these commands writes as a symlink to a path outside the project.fallow migratethen created the outside file with the migrated config when.fallowrc.json,.fallowrc.jsoncorfallow.tomlwas a dangling link.rule-pack initdid the same forrule-packs/team-policy.jsoncor a linkedrule-packsdirectory, and it added therulePacksentry to an outside file that the discovered config linked to, also when that config sits above--rootin the same repository.coverage setupwrotesetup.lockandsetup.jsonthrough a link at.fallowor at the file itself, and it wrotedocs/collect-coverage.mdthrough a link, so it could overwrite an outside file.ci-template gitlab --vendor <dir>wroteci/gitlab-ci.ymlandci/scripts/*.shthrough a link below<dir>, and with--forceit also overwrote an existing outside file. These commands now stop with an error when the target, or a directory on the way to it, is a symlink that resolves outside the project or a dangling link.migrate,rule-pack init,coverage setupandci-templateexit with code 2. When only the config file ofrule-pack initlinks outside the project, the command writes the pack, leaves the config unchanged and prints therulePacksentry to add by hand. This is the check thatinitandagent installalready use. A link that stays inside the project still works, andmigrate --dry-runis not affected.The analysis caches no longer write through a symlink that leaves the project. A cloned repository could commit
.fallow, a directory in it, or a cache file such as.fallow/.gitignoreas a symlink to a path outside the project. An analysis run then wrote through that link. It created or overwrote the outside file with the content*(the cache.gitignore), or it wrote cache files into the outside directory. This affected the extraction cache, the graph cache, the duplication token cache, the churn cache, the flag age cache, the audit and security base snapshot caches, the walkthrough state ofaudit, and the default snapshot path ofhealth --save-snapshot. Each of these writers now checks the path before it writes. When the cache directory, a directory below it, or the file is a symlink that resolves outside the project, or a dangling link, the writer skips the cache save and the analysis continues.health --save-snapshotstops with an error in that case, andaudit-cache prunedoes not delete through such a link. A link that stays inside the project still works. Whencache.dirorFALLOW_CACHE_DIRpoints outside the project, for example../shared-cache, the check starts at that directory, so a link at the directory itself stays allowed.The GitHub Action no longer writes its artifacts through a symlink. The Action now rejects a symlink or another file that is not a regular file at the path of an analysis, comment, review or scoped-result artifact, before it writes the artifact. The shared mutation helpers check their output paths before cleanup and publication. A regular artifact file from an earlier run is still replaced. The checks apply to a static checkout. They do not stop a path that another process replaces during the run.
A rejected dependency version in the installation diagnostics of the Action can no longer start a workflow command. The Action now escapes the version text, so a line break in it does not start another workflow command.
(Related to #4259)
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.