chore: bump the docs group across 1 directory with 2 updates #66

Open

dependabot[bot] wants to merge 1 commit from dependabot/npm_and_yarn/docs-3b1bcb31a8 into main

dependabot[bot] commented

2026-08-17 13:29:34 +00:00

(Migrated from github.com)

Bumps the docs group with 2 updates in the / directory: fuse.js and laravel-mix.

Updates fuse.js from 6.6.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: https://github.com/krisk/Fuse/compare/v7.4.2...v7.5.0

v7.4.2

Bug Fixes

types: ship CommonJS type declarations (.d.cts) so consumers on moduleResolution: node16/nodenext no longer hit TS1479 ("masquerading as ESM") when importing the package from a CommonJS project. The lib entries now resolve to a runtime-accurate export = declaration and the worker to its named declaration, via the require exports condition. (#780)

Full Changelog: https://github.com/krisk/Fuse/compare/v7.4.1...v7.4.2

v7.4.1

Bug Fixes

types: ship TypeScript declarations for fuse.js/worker (572ad1e), closes #828

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

Both worker subpaths now resolve types under node16/nodenext and bundler module resolution.

v7.4.0

First stable on the 7.4 line. Aggregates everything from the 7.4.0-beta.1 → 7.4.0-beta.8 cycle. See CHANGELOG.md for the per-beta breakdown.

Features

FuseWorker — parallel search via Web Workers (9ba192c). New FuseWorker class shards the collection across workers, runs searches in parallel, and preserves the same result ordering as Fuse. See the Web Workers guide.

token-search: tokenMatch: 'all' | 'any' option for AND/OR semantics (#827, 9f979d0). Default 'any' preserves existing behavior; 'all' requires every query word to match somewhere in a record (term-centric AND), useful for filter-style queries.

token-search: customizable tokenizer with unicode-aware default (#821, 8e55cae). New tokenize?: RegExp | (text: string) => string[] option; the default regex now segments CJK, Cyrillic, Greek, Arabic, etc. out of the box.

Bug Fixes

matches: report array-path keys as dotted strings (acd54e8). Previously match.key leaked a raw string[] for keys declared as path arrays (e.g. keys: [['author', 'firstName']]), contradicting the documented FuseResultMatch.key: string type. Now emits the canonical dotted string ('author.firstName'). Behavior change: consumers relying on the array shape need to update.

bitap: restrict highlight indices to matched window (#792, 622f105). Closes #505, #611, #691, #793.

... (truncated)

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

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

7.4.0 (2026-05-30)

7.4.0-beta.8 (2026-05-25)

Bug Fixes

matches: report array-path keys as dotted strings (acd54e8)

7.4.0-beta.7 (2026-05-22)

Features

... (truncated)

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
9e63058 chore(release): 7.4.2
Additional commits viewable in compare view

Updates laravel-mix from 6.0.43 to 6.0.49

Commits

See full diff in compare view

Bumps the docs group with 2 updates in the / directory: [fuse.js](https://github.com/krisk/Fuse) and [laravel-mix](https://github.com/JeffreyWay/laravel-mix). Updates `fuse.js` from 6.6.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> <h2>v7.4.2</h2> <h3>Bug Fixes</h3> <ul> <li><strong>types:</strong> ship CommonJS type declarations (<code>.d.cts</code>) so consumers on <code>moduleResolution: node16</code>/<code>nodenext</code> no longer hit <code>TS1479</code> ("masquerading as ESM") when importing the package from a CommonJS project. The lib entries now resolve to a runtime-accurate <code>export =</code> declaration and the worker to its named declaration, via the <code>require</code> exports condition. (<a href="https://redirect.github.com/krisk/Fuse/issues/780">#780</a>)</li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/krisk/Fuse/compare/v7.4.1...v7.4.2">https://github.com/krisk/Fuse/compare/v7.4.1...v7.4.2</a></p> <h2>v7.4.1</h2> <h3>Bug Fixes</h3> <ul> <li><strong>types:</strong> ship TypeScript declarations for <code>fuse.js/worker</code> (<a href="https://github.com/krisk/Fuse/commit/572ad1e6fca0bce226afae88b33a6f2d3672f80f">572ad1e</a>), closes <a href="https://redirect.github.com/krisk/Fuse/issues/828">#828</a></li> <li><strong>types:</strong> add TypeScript declarations for <code>fuse.js/worker-script</code> (<a href="https://github.com/krisk/Fuse/commit/6ef6c33101f8f4387d8a1dc7a227e483a179231f">6ef6c33</a>), closes <a href="https://redirect.github.com/krisk/Fuse/issues/828">#828</a></li> </ul> <p>Both worker subpaths now resolve types under node16/nodenext and bundler module resolution.</p> <h2>v7.4.0</h2> <p>First stable on the 7.4 line. Aggregates everything from the <code>7.4.0-beta.1</code> → <code>7.4.0-beta.8</code> cycle. See <a href="https://github.com/krisk/Fuse/blob/main/CHANGELOG.md">CHANGELOG.md</a> for the per-beta breakdown.</p> <h3>Features</h3> <ul> <li><strong>FuseWorker</strong> — parallel search via Web Workers (<a href="https://github.com/krisk/Fuse/commit/9ba192c5">9ba192c</a>). New <code>FuseWorker</code> class shards the collection across workers, runs searches in parallel, and preserves the same result ordering as <code>Fuse</code>. See the <a href="https://fusejs.io/api/workers">Web Workers guide</a>.</li> <li><strong>token-search:</strong> <code>tokenMatch: 'all' | 'any'</code> option for AND/OR semantics (<a href="https://redirect.github.com/krisk/Fuse/issues/827">#827</a>, <a href="https://github.com/krisk/Fuse/commit/9f979d0">9f979d0</a>). Default <code>'any'</code> preserves existing behavior; <code>'all'</code> requires every query word to match somewhere in a record (term-centric AND), useful for filter-style queries.</li> <li><strong>token-search:</strong> customizable tokenizer with unicode-aware default (<a href="https://redirect.github.com/krisk/Fuse/issues/821">#821</a>, <a href="https://github.com/krisk/Fuse/commit/8e55cae">8e55cae</a>). New <code>tokenize?: RegExp | (text: string) => string[]</code> option; the default regex now segments CJK, Cyrillic, Greek, Arabic, etc. out of the box.</li> </ul> <h3>Bug Fixes</h3> <ul> <li><strong>matches:</strong> report array-path keys as dotted strings (<a href="https://github.com/krisk/Fuse/commit/acd54e8">acd54e8</a>). Previously <code>match.key</code> leaked a raw <code>string[]</code> for keys declared as path arrays (e.g. <code>keys: [['author', 'firstName']]</code>), contradicting the documented <code>FuseResultMatch.key: string</code> type. Now emits the canonical dotted string (<code>'author.firstName'</code>). <strong>Behavior change:</strong> consumers relying on the array shape need to update.</li> <li><strong>bitap:</strong> restrict highlight indices to matched window (<a href="https://redirect.github.com/krisk/Fuse/issues/792">#792</a>, <a href="https://github.com/krisk/Fuse/commit/622f105">622f105</a>). Closes <a href="https://redirect.github.com/krisk/Fuse/issues/505">#505</a>, <a href="https://redirect.github.com/krisk/Fuse/issues/611">#611</a>, <a href="https://redirect.github.com/krisk/Fuse/issues/691">#691</a>, <a href="https://redirect.github.com/krisk/Fuse/issues/793">#793</a>.</li> </ul>  </blockquote> <p>... (truncated)</p> </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> <h3><a href="https://github.com/krisk/Fuse/compare/v7.4.1...v7.4.2">7.4.2</a> (2026-06-05)</h3> <h3>Bug Fixes</h3> <ul> <li><strong>types:</strong> emit CommonJS declarations (.d.cts) for node16/nodenext (<a href="https://redirect.github.com/krisk/Fuse/issues/780">#780</a>) (<a href="https://github.com/krisk/Fuse/commit/33f5d290df034e50b0646125264ee4a6229def98">33f5d29</a>)</li> </ul> <h3><a href="https://github.com/krisk/Fuse/compare/v7.4.0...v7.4.1">7.4.1</a> (2026-06-02)</h3> <h3>Bug Fixes</h3> <ul> <li><strong>types:</strong> add TypeScript declarations for fuse.js/worker-script (<a href="https://github.com/krisk/Fuse/commit/6ef6c33101f8f4387d8a1dc7a227e483a179231f">6ef6c33</a>), closes <a href="https://redirect.github.com/krisk/Fuse/issues/828">#828</a></li> <li><strong>types:</strong> ship TypeScript declarations for fuse.js/worker (<a href="https://github.com/krisk/Fuse/commit/572ad1e6fca0bce226afae88b33a6f2d3672f80f">572ad1e</a>), closes <a href="https://redirect.github.com/krisk/Fuse/issues/828">#828</a></li> </ul> <h2><a href="https://github.com/krisk/Fuse/compare/v7.4.0-beta.8...v7.4.0">7.4.0</a> (2026-05-30)</h2> <h2><a href="https://github.com/krisk/Fuse/compare/v7.4.0-beta.7...v7.4.0-beta.8">7.4.0-beta.8</a> (2026-05-25)</h2> <h3>Bug Fixes</h3> <ul> <li><strong>matches:</strong> report array-path keys as dotted strings (<a href="https://github.com/krisk/Fuse/commit/acd54e88b667002c602ff624f7d7f2cbc62f23ec">acd54e8</a>)</li> </ul> <h2><a href="https://github.com/krisk/Fuse/compare/v7.4.0-beta.6...v7.4.0-beta.7">7.4.0-beta.7</a> (2026-05-22)</h2> <h3>Features</h3>  </blockquote> <p>... (truncated)</p> </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><a href="https://github.com/krisk/Fuse/commit/9e630585195afc873876217270061d17b42cc6ef"><code>9e63058</code></a> chore(release): 7.4.2</li> <li>Additional commits viewable in <a href="https://github.com/krisk/Fuse/compare/v6.6.2...v7.5.0">compare view</a></li> </ul> </details> <br /> Updates `laravel-mix` from 6.0.43 to 6.0.49 <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/JeffreyWay/laravel-mix/commits">compare view</a></li> </ul> </details> <br />

This pull request can be merged automatically.

This branch is out-of-date with the base branch

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin dependabot/npm_and_yarn/docs-3b1bcb31a8:dependabot/npm_and_yarn/docs-3b1bcb31a8

git switch dependabot/npm_and_yarn/docs-3b1bcb31a8

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main

git merge --no-ff dependabot/npm_and_yarn/docs-3b1bcb31a8

git switch dependabot/npm_and_yarn/docs-3b1bcb31a8

git rebase main

git switch main

git merge --ff-only dependabot/npm_and_yarn/docs-3b1bcb31a8

git switch dependabot/npm_and_yarn/docs-3b1bcb31a8

git rebase main

git switch main

git merge --no-ff dependabot/npm_and_yarn/docs-3b1bcb31a8

git switch main

git merge --squash dependabot/npm_and_yarn/docs-3b1bcb31a8