⬆️ (deps) fuse.js@7.5.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
fuse.js (source)	7.4.2 → 7.5.0

---

Release Notes

krisk/Fuse (fuse.js)

v7.5.0

Compare Source

⚠️ Behavior changes

Every change in this release is a bug fix, but each one corrects a scoring or ranking 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.

If you assert on exact score 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.

• Field-length normalisation now counts words correctly. 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 \t, \n, or \r now score differently (#​830).
• Key weights are now normalised in object and keyless-logical search. Weights that did not sum to 1 were applied unnormalised, skewing the relative influence of each key. If your keys weights do not already sum to 1, your relative ranking changes (#​833).
• limit now returns the correct top-N when scores tie. A tie at the cutoff boundary could evict a result that should have been kept, so limit could return the wrong items, not merely the right items in a different order (#​835).
• Bitap respects minMatchCharLength in the exact-match shortcut. Matches shorter than minMatchCharLength were still reported via the exact-match fast path, so the matches array could contain entries it was configured to exclude (#​831).

Bug Fixes

• bitap: respect minMatchCharLength in exact-match shortcut (dbb98b6), closes #​831
• fieldNorm: count tabs and newlines as word separators (6fe85b0), closes #​830
• fieldNorm: count word-starts instead of space transitions (2946f97)
• scoring: normalise key weights in object and keyless-logical search (e164b61), closes #​833
• search: keep the correct top-N under limit when scores tie (437f8f3), closes #​835, thanks @​spokodev for the report and the fix

7.4.2 (2026-06-05)

Bug Fixes

• types: emit CommonJS declarations (.d.cts) for node16/nodenext (#​780) (33f5d29)

7.4.1 (2026-06-02)

Bug Fixes

• types: add TypeScript declarations for fuse.js/worker-script (6ef6c33), closes #​828
• types: ship TypeScript declarations for fuse.js/worker (572ad1e), closes #​828

---

Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Enabled.

♻ 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

---

[BotJerome]

Coverage Report for @jeromefitz/notion

Status	Category	Percentage	Covered / Total
🔵	Lines	32.88%	122 / 371
🔵	Statements	31.8%	125 / 393
🔵	Functions	28.57%	22 / 77
🔵	Branches	11.62%	20 / 172

File Coverage

No changed files found.

Generated in workflow #4258 for commit 1460bf3 by the Vitest Coverage Report Action

[BotJerome]

Coverage Report for @jeromefitz/release-notes-generator

Status	Category	Percentage	Covered / Total
🔵	Lines	52.79%	85 / 161
🔵	Statements	51.36%	94 / 183
🔵	Functions	53.33%	16 / 30
🔵	Branches	46.61%	55 / 118

File Coverage

No changed files found.

Generated in workflow #4258 for commit 1460bf3 by the Vitest Coverage Report Action

[BotJerome]

Coverage Report for @jeromefitz/semantic

Status	Category	Percentage	Covered / Total
🔵	Lines	89.28%	25 / 28
🔵	Statements	89.28%	25 / 28
🔵	Functions	100%	6 / 6
🔵	Branches	100%	25 / 25

File Coverage

No changed files found.

Generated in workflow #4258 for commit 1460bf3 by the Vitest Coverage Report Action