dependabot[bot] opened a new pull request, #42262: URL: https://github.com/apache/superset/pull/42262
Bumps [fuse.js](https://github.com/krisk/Fuse) from 7.4.2 to 7.5.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/krisk/Fuse/releases">fuse.js's releases</a>.</em></p> <blockquote> <h2>v7.5.0</h2> <h3>⚠️ Behavior changes</h3> <p>Every change in this release is a bug fix, but each one corrects a <strong>scoring or ranking</strong> bug. Scores and result ordering will shift for some queries. That is why this ships as a minor rather than a patch: the public API is unchanged and upgrading is a drop-in, but the results you get back can differ, and that should not arrive silently in a patch bump.</p> <p>If you assert on exact <code>score</code> values or on a specific result order, expect those assertions to need updating. Re-baseline them against 7.5.0 rather than pinning to 7.4.x, since the 7.4.x behavior was wrong in the cases below.</p> <ul> <li><strong>Field-length normalisation now counts words correctly.</strong> Tabs and newlines were not treated as word separators, so a multi-line or tab-delimited field was scored as though it were one long word, making it look far shorter than it is. Fields containing <code>\t</code>, <code>\n</code>, or <code>\r</code> now score differently (<a href="https://redirect.github.com/krisk/Fuse/issues/830">#830</a>).</li> <li><strong>Key weights are now normalised in object and keyless-logical search.</strong> Weights that did not sum to <code>1</code> were applied unnormalised, skewing the relative influence of each key. If your <code>keys</code> weights do not already sum to <code>1</code>, your relative ranking changes (<a href="https://redirect.github.com/krisk/Fuse/issues/833">#833</a>).</li> <li><strong><code>limit</code> now returns the correct top-N when scores tie.</strong> A tie at the cutoff boundary could evict a result that should have been kept, so <code>limit</code> could return the <em>wrong</em> items, not merely the right items in a different order (<a href="https://redirect.github.com/krisk/Fuse/issues/835">#835</a>).</li> <li><strong>Bitap respects <code>minMatchCharLength</code> in the exact-match shortcut.</strong> Matches shorter than <code>minMatchCharLength</code> were still reported via the exact-match fast path, so the <code>matches</code> array could contain entries it was configured to exclude (<a href="https://redirect.github.com/krisk/Fuse/issues/831">#831</a>).</li> </ul> <h3>Bug Fixes</h3> <ul> <li><strong>bitap:</strong> respect minMatchCharLength in exact-match shortcut (dbb98b6), closes <a href="https://redirect.github.com/krisk/Fuse/issues/831">#831</a></li> <li><strong>fieldNorm:</strong> count tabs and newlines as word separators (6fe85b0), closes <a href="https://redirect.github.com/krisk/Fuse/issues/830">#830</a></li> <li><strong>fieldNorm:</strong> count word-starts instead of space transitions (2946f97)</li> <li><strong>scoring:</strong> normalise key weights in object and keyless-logical search (e164b61), closes <a href="https://redirect.github.com/krisk/Fuse/issues/833">#833</a></li> <li><strong>search:</strong> keep the correct top-N under limit when scores tie (437f8f3), closes <a href="https://redirect.github.com/krisk/Fuse/issues/835">#835</a>, thanks <a href="https://github.com/spokodev"><code>@spokodev</code></a> for the report and the fix</li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/krisk/Fuse/compare/v7.4.2...v7.5.0">https://github.com/krisk/Fuse/compare/v7.4.2...v7.5.0</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/krisk/Fuse/blob/main/CHANGELOG.md">fuse.js's changelog</a>.</em></p> <blockquote> <h2><a href="https://github.com/krisk/Fuse/compare/v7.4.2...v7.5.0">7.5.0</a> (2026-07-13)</h2> <h3>⚠️ Behavior changes</h3> <p>Every change in this release is a bug fix, but each one corrects a <strong>scoring or ranking</strong> bug. Scores and result ordering will shift for some queries. That is why this ships as a minor rather than a patch: the public API is unchanged and upgrading is a drop-in, but the results you get back can differ, and that should not arrive silently in a patch bump.</p> <p>If you assert on exact <code>score</code> values or on a specific result order, expect those assertions to need updating. Re-baseline them against 7.5.0 rather than pinning to 7.4.x, since the 7.4.x behavior was wrong in the cases below.</p> <ul> <li><strong>Field-length normalisation now counts words correctly.</strong> Tabs and newlines were not treated as word separators, so a multi-line or tab-delimited field was scored as though it were one long word, making it look far shorter than it is. Fields containing <code>\t</code>, <code>\n</code>, or <code>\r</code> now score differently (<a href="https://redirect.github.com/krisk/Fuse/issues/830">#830</a>).</li> <li><strong>Key weights are now normalised in object and keyless-logical search.</strong> Weights that did not sum to <code>1</code> were applied unnormalised, skewing the relative influence of each key. If your <code>keys</code> weights do not already sum to <code>1</code>, your relative ranking changes (<a href="https://redirect.github.com/krisk/Fuse/issues/833">#833</a>).</li> <li><strong><code>limit</code> now returns the correct top-N when scores tie.</strong> A tie at the cutoff boundary could evict a result that should have been kept, so <code>limit</code> could return the <em>wrong</em> items, not merely the right items in a different order (<a href="https://redirect.github.com/krisk/Fuse/issues/835">#835</a>).</li> <li><strong>Bitap respects <code>minMatchCharLength</code> in the exact-match shortcut.</strong> Matches shorter than <code>minMatchCharLength</code> were still reported via the exact-match fast path, so the <code>matches</code> array could contain entries it was configured to exclude (<a href="https://redirect.github.com/krisk/Fuse/issues/831">#831</a>).</li> </ul> <h3>Bug Fixes</h3> <ul> <li><strong>bitap:</strong> respect minMatchCharLength in exact-match shortcut (<a href="https://github.com/krisk/Fuse/commit/dbb98b6ace1811ed65e1cac28f3e1501d1de3f34">dbb98b6</a>), closes <a href="https://redirect.github.com/krisk/Fuse/issues/831">#831</a></li> <li><strong>fieldNorm:</strong> count tabs and newlines as word separators (<a href="https://github.com/krisk/Fuse/commit/6fe85b087c675edc328b73f1d0088da73c09ab5e">6fe85b0</a>), closes <a href="https://redirect.github.com/krisk/Fuse/issues/830">#830</a></li> <li><strong>fieldNorm:</strong> count word-starts instead of space transitions (<a href="https://github.com/krisk/Fuse/commit/2946f978881f4bc2f214b6c64fee96450dcceae2">2946f97</a>)</li> <li><strong>scoring:</strong> normalise key weights in object and keyless-logical search (<a href="https://github.com/krisk/Fuse/commit/e164b61d4d324e0207e1f790e55dd13fe59c74ae">e164b61</a>), closes <a href="https://redirect.github.com/krisk/Fuse/issues/833">#833</a></li> <li><strong>search:</strong> keep the correct top-N under limit when scores tie (<a href="https://github.com/krisk/Fuse/commit/437f8f32713f6d8647339516dd61b8344847b3ae">437f8f3</a>), closes <a href="https://redirect.github.com/krisk/Fuse/issues/835">#835</a>, thanks <a href="https://github.com/spokodev"><code>@spokodev</code></a> for the report and the fix</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/krisk/Fuse/commit/45bac9fe2e71fe8c680c861a35a8b226c4ae6d5a"><code>45bac9f</code></a> chore(release): 7.5.0</li> <li><a href="https://github.com/krisk/Fuse/commit/437f8f32713f6d8647339516dd61b8344847b3ae"><code>437f8f3</code></a> fix(search): keep the correct top-N under limit when scores tie</li> <li><a href="https://github.com/krisk/Fuse/commit/b8142cfe11ad40409f0152b1d3c04df766f0951b"><code>b8142cf</code></a> test(fieldNorm): cover full separator set; narrow "any whitespace" comment</li> <li><a href="https://github.com/krisk/Fuse/commit/6fe85b087c675edc328b73f1d0088da73c09ab5e"><code>6fe85b0</code></a> fix(fieldNorm): count tabs and newlines as word separators</li> <li><a href="https://github.com/krisk/Fuse/commit/e164b61d4d324e0207e1f790e55dd13fe59c74ae"><code>e164b61</code></a> fix(scoring): normalise key weights in object and keyless-logical search</li> <li><a href="https://github.com/krisk/Fuse/commit/dbb98b6ace1811ed65e1cac28f3e1501d1de3f34"><code>dbb98b6</code></a> fix(bitap): respect minMatchCharLength in exact-match shortcut</li> <li><a href="https://github.com/krisk/Fuse/commit/e2ee793afa0b12d2405c22dcee790921cba8ff45"><code>e2ee793</code></a> chore: rebuild dist for <a href="https://redirect.github.com/krisk/Fuse/issues/830">#830</a> (fieldNorm whitespace fix)</li> <li><a href="https://github.com/krisk/Fuse/commit/2946f978881f4bc2f214b6c64fee96450dcceae2"><code>2946f97</code></a> fix(fieldNorm): count word-starts instead of space transitions</li> <li><a href="https://github.com/krisk/Fuse/commit/2fadbfa8c4277d7698f9d12387f57f86ae0ff382"><code>2fadbfa</code></a> chore: bump doc versions to 7.4.2</li> <li>See full diff in <a href="https://github.com/krisk/Fuse/compare/v7.4.2...v7.5.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
