Bump the minor group across 1 directory with 42 updates

[dependabot]

Bumps the minor group with 39 updates in the / directory:

Package	From	To
@codemirror/commands	6.10.3	6.10.4
@codemirror/lang-markdown	6.5.0	6.5.1
@codemirror/language	6.12.3	6.12.4
@kittycad/lib	4.3.8	4.3.12
@microlink/react-json-view	1.31.20	1.31.22
@preact/signals-core	1.14.3	1.14.4
@preact/signals-react	3.10.2	3.10.3
bonjour-service	1.4.1	1.4.3
fuse.js	7.4.2	7.5.0
html2canvas-pro	2.0.4	2.2.4
ignore	7.0.5	7.0.6
smol-toml	1.6.1	1.7.0
three	0.184.0	0.185.1
@types/three	0.184.1	0.185.1
vscode-languageserver-protocol	3.17.5	3.18.2
xstate	5.32.1	5.32.5
@biomejs/biome	2.3.0	2.5.4
@electron/fuses	2.1.2	2.1.3
@eslint/eslintrc	3.3.5	3.3.6
@playwright/test	1.60.0	1.61.1
autoprefixer	10.5.0	10.5.4
electron-builder	26.11.1	26.15.3
happy-dom	20.9.0	20.11.0
msw	2.14.6	2.15.0
postcss	8.5.15	8.5.20
typescript-eslint	8.60.0	8.64.0
vitest	4.1.9	4.1.10
ws	8.21.0	8.21.1
rollup	4.61.0	4.62.2
@tiptap/core	3.27.2	3.28.0
@tiptap/extension-link	3.27.2	3.28.0
@tiptap/markdown	3.27.2	3.28.0
@tiptap/react	3.27.2	3.28.0
@tiptap/starter-kit	3.27.2	3.28.0
@storybook/addon-a11y	10.4.6	10.5.3
@storybook/addon-docs	10.4.6	10.5.3
@storybook/react-vite	10.4.6	10.5.3
storybook	10.4.6	10.5.3
@types/vscode	1.120.0	1.125.0

Updates @codemirror/commands from 6.10.3 to 6.10.4

Commits

• See full diff in compare view

Updates @codemirror/lang-markdown from 6.5.0 to 6.5.1

Commits

• See full diff in compare view

Updates @codemirror/language from 6.12.3 to 6.12.4

Commits

• See full diff in compare view

Updates @codemirror/state from 6.6.0 to 6.7.1

Commits

• See full diff in compare view

Updates @kittycad/lib from 4.3.8 to 4.3.12

Commits

• b7439fd Update api spec (#646)
• 9124a42 Update api spec (#645)
• 490f9a0 Update api spec (#644)
• 2913894 Update api spec (#643)
• aa4719d Bump the patch group across 1 directory with 2 updates (#638)
• See full diff in compare view

Updates @microlink/react-json-view from 1.31.20 to 1.31.22

Release notes

Sourced from @​microlink/react-json-view's releases.

v1.31.22

What's Changed

• build(deps-dev): bump webpack-dev-server from 5.2.6 to 6.0.0 by @​dependabot[bot] in microlinkhq/react-json-view#188

Full Changelog: microlinkhq/react-json-view@v1.31.21...v1.31.22

v1.31.21

What's Changed

• build(deps-dev): bump sinon from 21.1.2 to 22.0.0 by @​dependabot[bot] in microlinkhq/react-json-view#166
• build(deps-dev): bump sass-loader from 16.0.8 to 17.0.0 by @​dependabot[bot] in microlinkhq/react-json-view#167
• build(deps-dev): bump webpack from 5.106.2 to 5.107.0 by @​dependabot[bot] in microlinkhq/react-json-view#168
• build(deps-dev): bump sass from 1.99.0 to 1.100.0 by @​dependabot[bot] in microlinkhq/react-json-view#169
• build(deps-dev): bump @​babel/plugin-syntax-jsx from 7.28.6 to 7.29.7 by @​dependabot[bot] in microlinkhq/react-json-view#170
• build(deps-dev): bump @​babel/eslint-parser from 7.28.6 to 7.29.7 by @​dependabot[bot] in microlinkhq/react-json-view#171
• build(deps-dev): bump @​babel/register from 7.29.3 to 7.29.7 by @​dependabot[bot] in microlinkhq/react-json-view#172
• build(deps-dev): bump sass from 1.100.0 to 1.101.0 by @​dependabot[bot] in microlinkhq/react-json-view#173
• build(deps): bump actions/checkout from 6 to 7 by @​dependabot[bot] in microlinkhq/react-json-view#183
• build(deps-dev): bump webpack from 5.107.2 to 5.108.3 by @​dependabot[bot] in microlinkhq/react-json-view#187

Full Changelog: microlinkhq/react-json-view@v1.31.20...v1.31.21

Changelog

Sourced from @​microlink/react-json-view's changelog.

1.31.22 (2026-07-03)

1.31.21 (2026-07-01)

Commits

• 2580eed chore(release): 1.31.22
• 53771e8 build(deps-dev): bump webpack-dev-server from 5.2.6 to 6.0.0 (#188)
• d6aa26d chore(release): 1.31.21
• 0e0b779 build(deps-dev): bump webpack from 5.107.2 to 5.108.3 (#187)
• 364702e build(deps): bump actions/checkout from 6 to 7 (#183)
• 8156fca build: tweaks
• 96da330 build(deps-dev): bump sass from 1.100.0 to 1.101.0 (#173)
• 2ac451c build(deps-dev): bump @​babel/register from 7.29.3 to 7.29.7 (#172)
• c5eef2d build(deps-dev): bump @​babel/eslint-parser from 7.28.6 to 7.29.7 (#171)
• 6638e3c build(deps-dev): bump @​babel/plugin-syntax-jsx from 7.28.6 to 7.29.7 (#170)
• Additional commits viewable in compare view

Updates @preact/signals-core from 1.14.3 to 1.14.4

Release notes

Sourced from @​preact/signals-core's releases.

@​preact/signals-core@​1.14.4

Patch Changes

• #947 2910fbf Thanks @​JoviDeCroock! - Fix computeds returning stale values after a batch reverts a signal to its original value.

  Reconciling a reverted batch write used to roll the signal's version number back, breaking version monotonicity. A lazy computed that read the signal during the batch had already observed the intermediate version, so a later write could re-mint that same version number for a different value and the computed would treat it as unchanged forever. Subscriber nodes that saw the pre-batch version are now fast-forwarded instead, keeping the no-op skip optimization without ever reusing version numbers.

• #945 d40746b Thanks @​andrewiggins! - Prevent model effect capture while creating effects inside untracked() and action() callbacks.

  If you create an effect() inside an untracked() callback within a createModel() factory, that effect is no longer disposed when the model is disposed. Use the disposer returned by effect() to clean it up manually.

Commits

• f6437f7 Version Packages (#946)
• 76f9155 Allow For to accept readonly arrays (#950)
• 6b0a76c fix(preact): dispose prop updaters when an element loses all signal props (#948)
• 2910fbf fix(core): keep signal versions monotonic when a batch reverts a value (#947)
• d40746b fix(core): prevent model effect capture in untracked (#945)
• See full diff in compare view

Updates @preact/signals-react from 3.10.2 to 3.10.3

Release notes

Sourced from @​preact/signals-react's releases.

@​preact/signals-react@​3.10.3

Patch Changes

• #950 76f9155 Thanks @​joeyTedeschi! - Allow <For> to accept readonly arrays and signals containing readonly arrays.

• Updated dependencies [2910fbf, d40746b]:

  • @​preact/signals-core@​1.14.4

Changelog

Sourced from @​preact/signals-react's changelog.

3.10.3

Patch Changes

• #950 76f9155 Thanks @​joeyTedeschi! - Allow <For> to accept readonly arrays and signals containing readonly arrays.

• Updated dependencies [2910fbf, d40746b]:

  • @​preact/signals-core@​1.14.4

Commits

• f6437f7 Version Packages (#946)
• 76f9155 Allow For to accept readonly arrays (#950)
• See full diff in compare view

Updates bonjour-service from 1.4.1 to 1.4.3

Release notes

Sourced from bonjour-service's releases.

1.4.3

Full Changelog: onlxltd/bonjour-service@1.4.2...1.4.3

Update for index.ts to fix imports #79 Thanks to @​andersk & @​Nerivec for their work identifying this issue.

Commits

• ee3a3c0 Update for imports
• 1eda77d Update .npmignore
• d7746b1 Update yarn.lock
• 6fe0a0d Bump js-yaml from 4.1.1 to 4.2.0
• d32a29b Updated package manager version
• a4c13f6 Merge branch 'dependabot/npm_and_yarn/tar-7.5.16'
• f9cf264 Bump undici from 6.25.0 to 6.27.0
• 47658b2 Bump tar from 7.5.15 to 7.5.16
• See full diff in compare view

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 html2canvas-pro from 2.0.4 to 2.2.4

Release notes

Sourced from html2canvas-pro's releases.

v2.2.4

Please refer to CHANGELOG.md for details.

v2.2.3

Please refer to CHANGELOG.md for details.

v2.2.2

Please refer to CHANGELOG.md for details.

v2.2.1

Please refer to CHANGELOG.md for details.

v2.2.0

Please refer to CHANGELOG.md for details.

v2.1.1

Please refer to CHANGELOG.md for details.

v2.1.0

Please refer to CHANGELOG.md for details.

Changelog

Sourced from html2canvas-pro's changelog.

2.2.4 (2026-07-13)

Features

• implement comprehensive drop-shadow parsing in FilterEffect class (c8ef6e7)

2.2.3 (2026-07-07)

Features

• enhance skipCache logic for image descriptors to ensure proper caching behavior (76224e4)
• implement skipCache flag for image descriptors to ensure side effects run on every render (5aa7e8c)

2.2.2 (2026-07-07)

Bug Fixes

• #216: render drop-shadow() via ctx.shadow instead of stripping it (110b343), closes #216

2.2.1 (2026-06-29)

Bug Fixes

• #216: strip drop-shadow() from ctx.filter to avoid canvas taint (89ba4fa), closes #216
• docs: update DeepWiki link in README for consistency (af3eeed)
• parseCache skips image descriptors + forward maxCacheSize to Cache (f6f6fe7)

2.2.0 (2026-06-24)

Features

• add new CSS property descriptors and rendering support (8a1d414)
• Phase2: add onError callback to Options and ContextOptions (23c0d4a)
• Phase4-5: add onProgress callback and raise coverage threshold (6018890)
• Phase4: wire onError callback to resource load failures (0524056)

Bug Fixes

• resolve circular dependency between canvas-renderer and content-renderer (fd6931f)
• resolve CodeQL alerts — new Function and document.write (1edd953)

Performance Improvements

• Phase3: add LRU pattern cache for linear-gradient backgrounds (0a82c98)
• Phase3: CSS parse cache LRU eviction and background pattern caching (ec5a8e3)

2.1.1 (2026-06-23)

Features

... (truncated)

Commits

• 7674c81 chore(release): v2.2.4
• c8ef6e7 feat: implement comprehensive drop-shadow parsing in FilterEffect class
• daaab61 chore(release): v2.2.3
• 76224e4 feat: enhance skipCache logic for image descriptors to ensure proper caching ...
• 5aa7e8c feat: implement skipCache flag for image descriptors to ensure side effects r...
• 069b7b6 chore(release): v2.2.2
• 110b343 fix(#216): render drop-shadow() via ctx.shadow instead of stripping it
• 604210f chore(release): v2.2.1
• 89ba4fa fix(#216): strip drop-shadow() from ctx.filter to avoid canvas taint
• f6f6fe7 fix: parseCache skips image descriptors + forward maxCacheSize to Cache
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for html2canvas-pro since your current version.

Updates ignore from 7.0.5 to 7.0.6

Release notes

Sourced from ignore's releases.

6.x (== 5.3.2)

6.x

• The release of 6.x is due to a mistake.
• Making an upgrade from 5.x to 6.x for now actually changes nothing and does no harm, everyone could just upgrade or ignore the version.
  • Actually 6.0.2 is 5.3.2
• The next major release will be 7.0.0

Commits

• 3823b5f 7.0.6
• f7520e2 test: adds tests for #153
• 424a2bb Merge pull request #161 from spokodev/fix/consecutive-leading-globstar
• e5cbe4a fix: consecutive leading **/ should match like a single **/
• ac68603 Merge pull request #159 from spokodev/fix/negated-character-class
• 5ba6b40 fix: negated character class [!...] should match like git
• See full diff in compare view

Updates smol-toml from 1.6.1 to 1.7.0

Release notes

Sourced from smol-toml's releases.

v1.7.0

This version slightly changes the behaviour of stringify: integers beyond the safe range are always emitted as float numbers.

String decode logic has been rewritten, it is a bit faster now and uses a single-pass approach instead of a dual-pass approach as it did previously. The code should be a bit smaller too, though I didn't actually measure that.

The package is now published with source-maps, declaration-maps, and a copy of the original TypeScript source files. This will improve your DX if you're like me and like Ctrl+Click'ing things a lot. ;)

What's Changed

• improve performance of the string decode logic by @​cyyynthia
• fix(stringify): emit integer-valued numbers beyond the safe-integer range as floats by @​spokodev in squirrelchat/smol-toml#56
• publish source-maps, declaration-maps, and original source files by @​cyyynthia
• miscellaneous repository maintenance tasks by @​cyyynthia

New Contributors

• @​spokodev made their first contribution in squirrelchat/smol-toml#56

Full Changelog: squirrelchat/smol-toml@v1.6.1...v1.7.0

Commits

• a62f06f revert: keep using vite 7
• 89aa9a3 chore: remove prepare script
• 17c7974 chore: make devEngine more lax w/ node version
• e5280a3 ci: checkout repo first
• 241c256 chore: version bump
• 0bfe7f4 chore: build cjs with rolldown instead of esbuild
• e0620ab chore: fmt
• 96114cb test: add tests for large integers
• f4537b6 fix: handle missed edge-cases in string parse
• 7b39aed chore: include source files in published package
• Additional commits viewable in compare view

Updates three from 0.184.0 to 0.185.1

Commits

• See full diff in compare view

Updates @types/three from 0.184.1 to 0.185.1

Commits

• See full diff in compare view

Updates vscode-languageserver-protocol from 3.17.5 to 3.18.2

Release notes

Sourced from vscode-languageserver-protocol's releases.

release/protocol/3.18.2

No release notes provided.

release/protocol/3.18.1

Changes:

• #1796: Make TextDocumentContentFeature a supported capability
• #1795: textDocumentContent capability/feature is still behind a proposed gate even though in 3.18 it's not flagged as proposed anymore
• #1794: Fix partial result type for textDocument/diagnostic request
• #1792: Update @​vscode/test-electron to version 3.0.0
• #1791: Refine notification assertions in delayOpenNotifications tests
• #1790: Update inline value documentation and clean up dependencies
• #1788: Update dependency versions in lock files
• #1787: Merge 3.18 release into main
• #1786: Shorten test dir path

This list of changes was auto generated.

release/protocol/3.18.0

No release notes provided.

release/types/3.18.0

Changes:

Feature Requests:

• #1691: Use NoInfer for better typing
• #1692: setImmediate Implementation in browser RAL for json-rpc is not ideal.
• #1698: RenameParams does not reference TextDocumentPositionParams interface in the JSON metamodel

Bugs:

• #752: Edits are applied twice
• #1717: Client requests textDocument/diagnostics before textDocument/didOpen
• #1693: Output channel leak when stopping LanguageClient
• #1581: Client error 'Failed to determine file type' after undoing rename with Cmd+Z
• #1548: Extra true in the output log when a language server disconnects

Others:

... (truncated)

Commits

• 20969f3 Prepare new release
• ba098d3 Update metaModel version to 3.18.0 (#1809)
• edd4c12 Merge 3.18.1 release into main (#1805)
• 14dbe29 Fix partial result type for textDocument/diagnostic request (#1794)
• e4e7d97 Update inline value documentation and clean up dependencies (#1790)
• 3c7721e Update dependency versions in lock files (#1788)
• dc94993 Merge 3.18 release into main (#1787)
• b21577c Merge next release into main (#1778)
• f168f85 Update documentation and fix lint errors (#1770)
• c54b2fd Merge pull request #1767 from microsoft/dbaeumer/straight-gazelle-plum
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by microsoft1es, a new releaser for vscode-languageserver-protocol since your current version.

Updates xstate from 5.32.1 to 5.32.5

Release notes

Sourced from xstate's releases.

xstate@5.32.5

Patch Changes

• #5603 345e04c Thanks @​xianjianlf2! - Sending an event to a stopped actor no longer throws when the event contains unserializable data (e.g. circular references). Previously, the development-only warning that an event was sent to a stopped actor used JSON.stringify on the event, which could throw and mask the intended warning. The warning is now emitted safely regardless of the event's contents.

xstate@5.32.4

Patch Changes

• #5589 e913eeb Thanks @​spokodev! - Fixed a bug where targeting a history state that is a direct child of a parallel state would silently do nothing when that parallel state had not been visited yet and the history state had no default target. The machine now enters the parallel state's initial configuration, matching the behavior of history states inside compound states.

  const machine = createMachine({
    initial: 'off',
    states: {
      off: { on: { GO: 'on.hist' } },
      on: {
        type: 'parallel',
        states: {
          regA: { initial: 'a1', states: { a1: {}, a2: {} } },
          regB: { initial: 'b1', states: { b1: {}, b2: {} } },
          hist: { type: 'history', history: 'deep' }
        }
      }
    }
  });
  const actor = createActor(machine).start();
  actor.send({ type: 'GO' });
  actor.getSnapshot().value; // { on: { regA: 'a1', regB: 'b1' } }

xstate@5.32.3

Patch Changes

• #5575 830db8b Thanks @​JSap0914! - Fixed initialTransition (and transition) throwing "Actor with system ID '...' already exists" when the machine contains an invoke with a systemId.

  Root cause: createInertActorScope used createActor(logic) internally, which eagerly ran getInitialSnapshot during construction and registered any systemId-carrying child actors in the system. When the caller then ran getInitialSnapshot (or transition) via the returned scope, the same system was reused, causing the duplicate-registration error.

  Fix: After creating the internal actor, createInertActorScope now replaces the actor's system reference with a freshly-created system. Child actors spawned by the subsequent caller-driven getInitialSnapshot / transition invocation therefore register into a clean system with no pre-existing entries.

  const machine = createMachine({
    initial: 'idle',
    states: {
      idle: {
        invoke: {
          src: fromPromise(async () => 42),
          systemId: 'myActor' // previously caused: "Actor with system ID 'myActor' already exists"
        }
      }

... (truncated)

Commits

• c25dba0 Version Packages (#5604)
• b669e95 fix(xstate-vue): correct vitest include glob so tests are discovered (#5607)
• 345e04c fix(core): don't throw when warning about unserializable event sent to stoppe...
• 9297fa8 Version Packages (#5590)
• e913eeb fix(core): enter parallel default when targeting an unvisited history child (...
• ab5aa56 Version Packages (#5586)
• 830db8b fix(core): prevent 'systemId already exists' in pure transition functions (#5...
• a551a2b docs: add missing https protocol to Stately Studio link (#5585)
• cc087bf ci: pin Node to 24.16.0 (#5577)
• 806ae91 Version Packages
• Additional commits viewable in compare view

Updates @biomejs/biome from 2.3.0 to 2.5.4

Release notes

Sourced from @​biomejs/biome's releases.

Biome CLI v2.5.4

2.5.4

Patch Changes

• #10665 55ff995 Thanks @​dyc3! - Improved the performance of the HTML parser slightly in our synthetic benchmarks.

• #10894 f4fb10e Thanks @​ematipico! - Fixed #6392: On-type formatting no longer moves comments before an if statement into its body.

• #10939 f2799db Thanks @​Netail! - Fixed #10930: noLabelWithoutControl now correctly detects text interpolation in Astro, Svelte & Vue as valid accessible content.

• #10945 ae15d98 Thanks @​Netail! - Fixed #10942: Svelte directives don't throw an accidental debug log anymore.

• #10842 5e1abfe Thanks @​JamBalaya56562! - Fixed #9196: biome check --write --unsafe no longer hangs forever when applying the noCommentText code fix.

  The rule's fix now wraps the comment in a real JSX expression container ({/* comment */}) instead of re-inserting the braces as plain JSX text, so the fixed code is no longer reported again by the same rule.

• #10891 ecca79e Thanks @​ematipico! - Fixed [#10885](https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome/issues/10885): prevented a module-inference regression introduced by a housekeeping change.

• #10886 60c8043 Thanks @​dyc3! - Fixed #10727: Biome now breaks the arguments of curried test.each, it.each, describe.each, and test.for calls when they exceed the configured line width.

  - test.each([[1, 2]])("a description that is long enough to push the hugged opening line beyond the print width", (a, b) => {
  -   expect(a).toBe(b);
  - });
  + test.each([[1, 2]])(
  +   "a description that is long enough to push the hugged opening line beyond the print width",
  +   (a, b) => {
  +     expect(a).toBe(b);
  +   },
  + );

• #10895 01a85f0 Thanks @​ematipico! - Biome will now remove stale Unix daemon sockets from older Biome versions when starting a newer daemon.

What's Changed

• feat(yml/fmt): basic block properties by @​ematipico in biomejs/biome#10873
• feat(useSortedClasses): sort important-suffix classes in sort_v4 by @​johncarmack1984 in biomejs/biome#10880
• fix(format/js): wrap curried test each calls by @​dyc3 in biomejs/biome#10886
• fix(markdown): parse whitespace after list markers by @​tidefield in biomejs/biome#10869
• fix(inference): use correct function when cloning data by @​ematipico in biomejs/biome#10891
• docs(noDuplicateProperties): note that @​keyframes declarations are ignored by @​dfedoryshchev in biomejs/biome#10893
• fix(lint): prevent noCommentText fix from looping forever by @​JamBalaya56562 in biomejs...

  Description has been truncated

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
modeling-app	Ready	Preview, Comment	Jul 27, 2026 3:54pm

[dependabot]

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