chore(deps): bump the minor-and-patch group across 1 directory with 5 updates

[dependabot]

Bumps the minor-and-patch group with 5 updates in the / directory:

Package	From	To
fuse.js	7.4.2	7.5.0
@vitest/coverage-v8	4.1.9	4.1.10
@yao-pkg/pkg	6.20.0	6.21.0
semantic-release	25.0.5	25.0.7
vitest	4.1.9	4.1.10

Updates fuse.js from 7.4.2 to 7.5.0

Release notes

Sourced from fuse.js's releases.

v7.5.0

⚠️ 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

Full Changelog: krisk/Fuse@v7.4.2...v7.5.0

Changelog

Sourced from fuse.js's changelog.

7.5.0 (2026-07-13)

⚠️ 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

Commits

• 45bac9f chore(release): 7.5.0
• 437f8f3 fix(search): keep the correct top-N under limit when scores tie
• b8142cf test(fieldNorm): cover full separator set; narrow "any whitespace" comment
• 6fe85b0 fix(fieldNorm): count tabs and newlines as word separators
• e164b61 fix(scoring): normalise key weights in object and keyless-logical search
• dbb98b6 fix(bitap): respect minMatchCharLength in exact-match shortcut
• e2ee793 chore: rebuild dist for #830 (fieldNorm whitespace fix)
• 2946f97 fix(fieldNorm): count word-starts instead of space transitions
• 2fadbfa chore: bump doc versions to 7.4.2
• See full diff in compare view

Updates @vitest/coverage-v8 from 4.1.9 to 4.1.10

Release notes

Sourced from @​vitest/coverage-v8's releases.

v4.1.10

   🐞 Bug Fixes

• browser: Check fs access in builtin commands [backport to v4]  -  by @​hi-ogawa, Hiroshi Ogawa and OpenCode (claude-opus-4-8) in vitest-dev/vitest#10680 (5c18d)
• vm: Fix external module resolve error with deps optimizer query for encoded URI [backport to v4]  -  by @​SveLil and @​hi-ogawa in vitest-dev/vitest#10661 (bae52)

    View changes on GitHub

Commits

• db616d2 chore: release v4.1.10 (#10718)
• See full diff in compare view

Updates @yao-pkg/pkg from 6.20.0 to 6.21.0

Release notes

Sourced from @​yao-pkg/pkg's releases.

Release 6.21.0

6.21.0 (2026-06-30)

Features

• build hooks (preBuild, postBuild, per-file transform) (#273) (3667383), closes package.json#pkg
• bump fetch 3.6.3 with node 22.22.3, 24.15.0 and 26.2.0 (#277) (546bbf0)
• bump fetch 3.6.4 with nodejs 22.23.1, 24.18.0, 26.4.0 (#288) (3520d26)

Bug Fixes

• detector: pick up six more silent-drop shapes (re-exports, new URL, multi-arg path.join, path.resolve(__dirname,…), createRequire aliases, import.meta.resolve) (#272) (ea66111), closes #269
• sea: set process.pkg in worker threads (#270) (376e2a4)

Test added

• fetch-all: track supported node majors, drop node20 (#286) (1b0002f)
• split unit tests into node:test suite, add c8 coverage (#271) (26f10a3), closes #267 #267

Chores

• add worktrees to gitignore (d585e27)
• deps: bump esbuild to >=0.28.1 to fix security vuln (#282) (#284) (68f41d5)

Changelog

Sourced from @​yao-pkg/pkg's changelog.

6.21.0 (2026-06-30)

Features

• build hooks (preBuild, postBuild, per-file transform) (#273) (3667383), closes package.json#pkg
• bump fetch 3.6.3 with node 22.22.3, 24.15.0 and 26.2.0 (#277) (546bbf0)
• bump fetch 3.6.4 with nodejs 22.23.1, 24.18.0, 26.4.0 (#288) (3520d26)

Bug Fixes

• detector: pick up six more silent-drop shapes (re-exports, new URL, multi-arg path.join, path.resolve(__dirname,…), createRequire aliases, import.meta.resolve) (#272) (ea66111), closes #269
• sea: set process.pkg in worker threads (#270) (376e2a4)

Test added

• fetch-all: track supported node majors, drop node20 (#286) (1b0002f)
• split unit tests into node:test suite, add c8 coverage (#271) (26f10a3), closes #267 #267

Chores

• add worktrees to gitignore (d585e27)
• deps: bump esbuild to >=0.28.1 to fix security vuln (#282) (#284) (68f41d5)

6.19.0 (2026-04-24)

Features

• config: accept CLI-only build flags in pkg config (#263) (a8e91df)

Bug Fixes

• deps: update @​roberts_lando/vfs to version 0.3.3 (#266) (d155e24)
• detector: stop silent dependency drops in SEA mode (ESM parse, dynamic import, decorators) (#268) (81c6c88)
• sea: silence benign LIEF warnings during postject injection (#265) (974df53)

6.18.2 (2026-04-22)

Bug Fixes

• sea: match blob generator to target Node version (#247) (ad2a336), closes #236 #236 #236 #236 #236 #236 #236
• sea: strip trailing slashes in manifest key lookup (#261) (af0c086)

6.18.1 (2026-04-21)

Bug Fixes

• pkg: ship all .d.ts files in npm package (#258) (7e10ce2)

6.18.0 (2026-04-20)

... (truncated)

Commits

• See full diff in compare view

Updates semantic-release from 25.0.5 to 25.0.7

Release notes

Sourced from semantic-release's releases.

v25.0.7

25.0.7 (2026-07-13)

Bug Fixes

• argument Injection via repositoryUrl in package.json (#4245) (c46dbda)

v25.0.6

25.0.6 (2026-07-10)

Bug Fixes

• ensure encoded secrets get masked (8e28dd3)

Commits

• c46dbda fix: argument Injection via repositoryUrl in package.json (#4245)
• 7abb562 chore(deps): update npm to v12 (#4244)
• 8b15865 chore(deps): update dependency @​types/node to v24.13.3 (#4243)
• 8e28dd3 fix: ensure encoded secrets get masked
• f293647 Merge commit from fork
• a973d20 ci(action): update github/codeql-action action to v4.37.0 (#4241)
• c62136f chore(deps): update dependency mockserver-client to v7.4.0 (#4240)
• 9be3e6c chore(deps): lock file maintenance (#4239)
• 3259ebb chore(deps): update dependency got to v15.1.0 (#4238)
• 1c17eb5 chore(deps): update dependency mockserver-client to v7.3.0 (#4237)
• Additional commits viewable in compare view

Updates vitest from 4.1.9 to 4.1.10

Release notes

Sourced from vitest's releases.

v4.1.10

   🐞 Bug Fixes

• browser: Check fs access in builtin commands [backport to v4]  -  by @​hi-ogawa, Hiroshi Ogawa and OpenCode (claude-opus-4-8) in vitest-dev/vitest#10680 (5c18d)
• vm: Fix external module resolve error with deps optimizer query for encoded URI [backport to v4]  -  by @​SveLil and @​hi-ogawa in vitest-dev/vitest#10661 (bae52)

    View changes on GitHub

Commits

• db616d2 chore: release v4.1.10 (#10718)
• bae52b5 fix(vm): fix external module resolve error with deps optimizer query for enco...
• See full diff in compare view

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 commands and options

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[greptile-apps]

PR author is in the excluded authors list.

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.