Skip to content

chore(deps): Update all patch dependencies - #230

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-patch-dependencies
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-patch-dependencies

Conversation

@renovate

@renovate renovate Bot commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@​codemirror/lint 6.9.7 → 6.9.8 age confidence
@iconify-json/material-symbols 1.2.96 → 1.2.99 age confidence
@inlang/paraglide-js (source) 2.29.1 → 2.29.3 age confidence
@tailwindcss/vite (source) 4.3.3 → 4.3.5 age confidence
@tanstack/devtools-vite (source) 0.8.5 → 0.8.6 age confidence
@tanstack/solid-devtools (source) 0.8.13 → 0.8.14 age confidence
@tanstack/solid-router-devtools (source) 1.167.2 → 1.167.3 age confidence
@tanstack/solid-virtual (source) 3.13.49 → 3.13.53 age confidence
@tauri-apps/plugin-dialog 2.8.3 → 2.8.4 age confidence
@tauri-apps/plugin-opener 2.7.2 → 2.7.3 age confidence
@tauri-apps/plugin-updater 2.14.0 → 2.14.1 age confidence
oxlint-tsgolint 7.0.2005 → 7.0.2007 age confidence
solid-js (source) 1.9.17 → 1.9.19 age confidence
tailwindcss (source) 4.3.3 → 4.3.5 age confidence
vite (source) 8.3.5 → 8.3.8 age confidence
vite-plugin-solid 2.11.14 → 2.11.16 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

generaltranslation/paraglide-js (@​inlang/paraglide-js)

v2.29.3

Patch Changes
  • d34c86c: Stop the bundler plugins from rewriting unchanged output when a watch event arrives before buildStart or after a failed compile. Such a recompile now starts from the hashes of the output on disk, as buildStart does, so it writes only the files that differ. Previously it rewrote every generated file, and in Vite each rewritten message module became another watch event: with message-modules and a few thousand messages, a dev server could stay busy for minutes after startup.

v2.29.2

Patch Changes
  • 6146ffd: Emit TypeScript declarations with the tsc of TypeScript 7 when it is installed beside TypeScript 5/6 under the @typescript/native alias, as documented for svelte-check --tsgo. On large locale-modules projects this is much faster than the compiler API of TypeScript 5/6. The declarations change the way they do when upgrading typescript to 7: formatting, ordering and some JSDoc.

    When additionalFiles contains JavaScript, keep using the TypeScript 5/6 compiler API to preserve project dependency resolution and inferred types.

tailwindlabs/tailwindcss (@​tailwindcss/vite)

v4.3.5

Compare Source

Fixed
  • Canonicalization: improve performance in projects with many functional variant values (e.g. a matchVariant plugin with thousands of values) (#​20663)
  • Don't crash or create a fallback with the wrong color for a color-mix(…) without a color interpolation method (e.g. color-mix(var(--color-red-500)) or color-mix(currentcolor 50%, transparent)) (#​20658, #​20666)
  • Ensure @tailwindcss/oxide-wasm32-wasi loads instead of hanging forever (e.g. with NAPI_RS_FORCE_WASI=error or in WebContainers) (#​20667)
  • Remove as: '*.css' from the @tailwindcss/turbopack setup in its README, because it breaks CSS modules (#​20660)
  • Ignore <!-- and --> between top-level rules in CSS instead of throwing or swallowing the next rule (e.g. a { color: red } --> b { color: blue }) (#​20665)
  • Ensure @tailwindcss/oxide-wasm32-wasi detects changed and new source files after the first scan (e.g. in WebContainers) (#​20487)
  • Prevent type errors with skipLibCheck: false caused by imports of unshipped modules in the @tailwindcss/node type declarations (#​20632)

v4.3.4

Compare Source

Added
  • Add @tailwindcss/turbopack, a Turbopack loader for using Tailwind CSS with Next.js (#​20367)
Fixed
  • Ensure watch mode detects changes to symlinked @source files whose real paths aren't otherwise scanned (#​20356)
  • Ensure variants using @scope wrap generated utilities instead of nesting inside them (#​20369)
  • Ensure nested @scope rules preserve their scoping semantics when flattened (#​20369)
  • Preserve declarations directly inside @scope by wrapping them in :where(:scope) (#​20369)
  • Ensure generated utilities include a space in empty var() fallbacks (e.g. var(--tw-blur,) → var(--tw-blur, )) (#​20373)
  • Canonicalization: convert arbitrary breakpoint and container query variants to named equivalents (e.g. max-[64rem]:flex → max-lg:flex) (#​20380)
  • Prevent @tailwindcss/vite from crashing on every edit under Vite's experimental bundledDev mode (#​20379)
  • Ensure @tailwindcss/oxide falls back to WASM on platforms without native bindings (@tailwindcss/oxide-wasm32-wasi now installs on all platforms, but only loads when no native binding is available) (#​20383)
  • Extract class candidates from Ruby %w and %W literals using angle brackets or custom delimiters (e.g. %w<flex>, %w|flex|), including in Slim and Haml templates (#​20387)
  • Preserve whitespace in --default(…) values in functional @utility definitions (e.g. --default(box alphabetic) no longer becomes boxalphabetic) (#​20392)
  • Ensure automatic source detection respects negation-based .gitignore files (e.g. /* followed by !/… patterns) (#​20397)
  • Ensure root theme('…') namespace lookups in JavaScript plugins and config files return the full namespace object instead of the value of its DEFAULT key (#​20399)
  • Skip ignored directories when generating watch globs instead of walking their contents on every rebuild (#​20408)
  • Drop invalid UTF-8 candidates during class detection (#​20389)
  • Prevent @tailwindcss/vite from forcing full-page reloads for scanned files that Vite does not handle as modules (e.g. .php files) (#​20414)
  • Canonicalization: don't merge utilities that reference different theme variables set to CSS-wide keywords like unset (#​20417)
  • Don't generate utilities when a modifier is used that would otherwise be silently ignored (e.g. rounded-sm/[5], shadow-sm/foo, stroke-2/50) (#​20419)
  • Preserve and, or, and not inside selectors in supports-[…] variants (e.g. supports-[selector(a:not(.foo))]:flex) (#​20420)
  • Don't warn about Angular's ::ng-deep and :host-context() when optimizing CSS (#​20434)
  • Don't generate CSS for candidates containing an empty additional modifier (e.g. bg-red-500/50/ and group-hover/foo//bar:flex) (#​20466)
  • Ensure min-*, max-*, and container query variants with decimal values are sorted numerically (e.g. min-[40.25rem] before min-[40.5rem]) (#​20512)
  • Ensure CSS comments ending with \*/ are closed correctly instead of swallowing the CSS that follows (e.g. /* C:\temp\*/) (#​20508)
  • Improve style invalidation performance of group-* and peer-* variants (#​20513)
  • Ensure cached compilers release their loadModule and loadStylesheet callbacks after compilation (#​20531)
  • Canonicalization: preserve & when moving a pseudo-element into * or ** (e.g. [&_::before]:flex → **:[&::before]:flex) (#​20550)
  • Ensure the Set.prototype.intersection polyfill in canonicalizeCandidates(…) returns the intersection instead of the first set on Node.js < 22 (#​20562)
  • Canonicalization: ensure inline theme(…) alphas with more than 2 decimals migrate to a percentage modifier with the same opacity (e.g. theme(colors.red.500/.12345) → text-red-500/[12.345%], not text-red-500/[12.345]) (#​20563)
  • Canonicalization: preserve inline theme(…) alphas as an arbitrary percentage when a custom --opacity-* theme value would change the opacity (e.g. theme(colors.red.500/50%) → text-red-500/[50%] with --opacity-50: 10%) (#​20563)
  • Ensure the @property fallback isn't applied in Safari versions that no longer support margin-trim: inline (#​20569)
  • Treat viewport units like dvmin and svi and font-relative units like cap and rex as lengths in arbitrary values (e.g. text-[10dvmin] generates font-size instead of color) (#​20516)
  • Write plugin logs to stderr in tailwindcss canonicalize so they don't end up in the results on stdout (#​20561)
  • Extract class shorthands on later lines when Pug text, comments, or quoted attribute values contain unbalanced brackets, or a quote that doesn't start a string (e.g. input(pattern=/"/.source)) (#​20547, #​20572)
  • Underline the correct occurrence of an unsupported data type in --value(…) warnings (#​20554)
  • Canonicalization: prefer an existing candidate when collapsing utilities over another utility with the same default theme value (e.g. text-foreground text-primary → text-primary, not text-card-checked-border) (#​20540)
  • Canonicalization: don't collapse utilities into a utility that uses another theme variable with the same default value (e.g. mt-card mb-card → my-card, not my-4) (#​20574)
  • Ensure @tailwindcss/postcss rewrites relative url(…)s of stylesheets that are inlined before it runs (e.g. @imports in Vite) in optimized builds (#​20576)
  • Drop nested rules that put a combinator after a pseudo-element when using pseudo-element variants (e.g. selection:* on a utility with a nested & > * rule) (#​20575)
  • Don't generate CSS for arbitrary values with unbalanced parentheses or brackets (e.g. w-[calc(1px] or [--x:a[b]) (#​20577)
  • Canonicalization: prevent collapse: true from taking exponentially longer when classes are linked through a utility that sets many properties (e.g. sr-only) (#​20558)
  • Ensure & is substituted inside :-moz-any(…) and :-webkit-any(…) in custom variants (e.g. @custom-variant firefox (:-moz-any(&));) (#​20486)
  • Ensure the standalone macOS binaries have a valid code signature, so macOS 27 no longer kills them at launch (#​20578)
  • Ensure @tailwindcss/turbopack and @tailwindcss/webpack rebuild when the input CSS changes (e.g. next dev with Turbopack no longer serves the CSS of the previous edit) (#​20582)
  • Canonicalization: don't drop a utility that sets a --tw-* variable when an unrelated property has the same value (e.g. link mt-4 no longer becomes mt-4 when link sets margin-top: 16px and --tw-translate-x: 16px) (#​20593)
  • Decode single-digit hexadecimal escapes in theme variable and @utility names as the CSS spec does (e.g. @theme { --color-\0: red; } no longer registers --color-0) (#​20591)
  • Don't treat !important inside strings, comments or url() in declaration values as the important flag (e.g. content: "a !important b") (#​20627)
  • Parse a custom property at the end of the input when it has no trailing ; (e.g. --foo: bar as the last declaration) (#​20653)
  • Keep a declaration without a ; at the end of the CSS input (e.g. color: red) (#​20655)
TanStack/devtools (@​tanstack/devtools-vite)

v0.8.6

Compare Source

Patch Changes
  • #​539 ed8b314 - Source injection no longer stops after the dev server parses a regex literal. Before this fix, a regex literal cached value as a child key of Literal nodes. Every later file with a string literal then threw during the walk and got zero data-tsd-source attributes.

  • #​540 012421f - Stop the console pipe feedback loop with Vite 8 server.forwardConsole. The server side of the pipe no longer sends browser logs that Vite printed in the terminal back to the browser.

  • #​548 40f32e4 - Run source injection before the transforms of other plugins (unless they also use order: 'pre'), also when devtools() is not first in the plugins array. Before this fix, a framework plugin that changed the code of only one environment shifted the line numbers, so data-tsd-source differed between SSR and client and caused hydration warnings.

  • #​541 df1464c - Fix "Go to Source" for files outside the current working directory, for example a package in a monorepo or Vite run from another directory. The editor got a path with the working directory added twice. Also answer a missing or malformed source with 400 instead of leaving the request pending.

  • #​542 9c58288 - Remove the intent bin from the published packages. It took over node_modules/.bin/intent from @tanstack/intent and imported the removed @tanstack/intent/intent-library subpath. The packages now have the tanstack-intent keyword, which current @tanstack/intent uses to find their skills.

  • #​545 d018c4c - Reject event bus requests to install a package when the name is not a valid npm package name. On macOS and Linux, run the package manager without a shell. Also reject a plugin import name that is not a JavaScript identifier, because it is written into your source file as code.

  • #​538 7cb0a8d - Inject the event bus port, host, and protocol into Vite pre-bundled dependency chunks too. Before this fix, a client installed from npm kept the default port 4206 and could not connect when the server bus used another port.

  • Updated dependencies [ed8b314, 012421f, df1464c, d018c4c]:

TanStack/devtools (@​tanstack/solid-devtools)

v0.8.14

Patch Changes
  • #​543 bbe529a - Require solid-js 1.9.13 or later. Our compiled output imports use from solid-js/web, and the server build of solid-js 1.9.12 and earlier does not export it. Before this fix, SSR apps with an older solid-js in their lockfile could not start the dev server.

  • #​557 f4ca00c - Cap the solid-js peer range at ^1. The previous open-ended >= range would accept Solid 2.0.0 once it is released, but these packages are built against Solid 1 and do not work with Solid 2.

  • Updated dependencies [8b3a032, f315fe8, 7b5f1ee, 9c58288, bbe529a, f4ca00c]:

TanStack/router (@​tanstack/solid-router-devtools)

v1.167.3

Compare Source

Patch Changes
TanStack/virtual (@​tanstack/solid-virtual)

v3.13.53

Compare Source

Patch Changes

v3.13.52

Compare Source

Patch Changes

v3.13.51

Compare Source

Patch Changes

v3.13.50

Compare Source

Patch Changes
tauri-apps/plugins-workspace (@​tauri-apps/plugin-dialog)

v2.8.4

Compare Source

vitejs/vite (vite)

v8.3.8

Compare Source

Bug Fixes
Performance Improvements
Miscellaneous Chores
Code Refactoring
  • optimizer: use non-capturing group for external types regex (#​24048) (ef23433)
Tests

v8.3.7

Compare Source

Bug Fixes
Miscellaneous Chores
Tests
Build System

v8.3.6

Compare Source

Bug Fixes
Performance Improvements
Miscellaneous Chores
Build System
  • generate sourcemaps in import-meta-current-dirname plugin (#​23904) (20d355a)
solidjs/solid-vite-plugin (vite-plugin-solid)

v2.11.16

Compare Source

Patch Changes
  • 1ea0fba: Load the client build of solid-js in test files that set // @vitest-environment node when test.environment is jsdom or happy-dom. The ssr environment keeps the browser condition again, and only the conditions Vitest passes to Node leave it out, so msw/node still loads.

v2.11.15

Compare Source

Patch Changes
  • 62e2b75: Production builds now dedupe solid-js the same way dev does. A dependency with its own nested copy of solid-js no longer adds a second runtime to the bundle, which broke context lookups (#​112).
  • a732eeb: Avoid overriding environments configured in Vitest workspaces and projects with the jsdom default
  • 9e67618: fix: exclude test mode from HMR setup
  • a7ec25f: Fix TypeError: Cannot read properties of undefined (reading 'extend') in tests on Vitest before 1.0 with @testing-library/jest-dom 6 or later installed (#​141). The plugin now injects jest-dom's ESM vitest entry as an absolute path for those Vitest versions, because they load the CommonJS entry from a bare specifier.
  • 6cc30fe: Only inject the @testing-library/jest-dom Vitest setup file when the package resolves from the project root. Previously the check ran from the plugin's own location, so with pnpm a transitive jest-dom (for example via Storybook) made Vitest fail with Failed to load url .../@testing-library/jest-dom/vitest.
  • d0e47f1: Vitest runs keep the jsdom environment and the @testing-library/jest-dom setup file when test.server.deps.external already lists solid-js. The plugin used to drop its whole test config in that case.
  • f8439e8: The plugin no longer changes resolve.alias. An alias object in your config now keeps priority over aliases that later plugins add, such as vite-plugin-node-polyfills mapping path (#​130).
  • df3ba8a: Compile modules whose id has the extension after the query, such as unplugin-icons' ~icons/mdi/folder?width=2em.tsx. Since 2.11.2 these were left to Vite's default JSX transform, which produced React code (#​206). Custom extensions are now also matched when the query contains a dot.
  • b50c064: Keep $ServerOnly templates in client transforms while HMR is active so hot updates of components using $ServerOnly no longer throw template is not a function. An explicit solid.omitServerOnlyTemplates setting still takes precedence.
  • cd79ed9: Without ssr: true, modules loaded on the server now compile to non-hydratable SSR output instead of DOM output. Prerendering a client-rendered app with ssrLoadModule no longer throws "Client-only API called on the server side" (#​64). Vitest keeps DOM output.
  • 9c17655: Server builds with ssr.target: 'webworker' now resolve the server build of solid-js. The plugin adds the worker export condition to that build, so renderToString and the other server APIs no longer resolve to their browser stubs (#​153). This works on Vite 4 and later.
  • 8909380: Vite 8's dependency scan no longer breaks on .tsx files (issue #​262).
    The plugin previously set optimizeDeps.rolldownOptions.transform.jsx: 'preserve' to stop Rolldown from injecting react/jsx-dev-runtime
    imports during the scan — but the scanner re-parses the transformed
    output as plain JS (import.meta.glob handling force-tags modules as
    js), so any .tsx with JSX was a hard PARSE_ERROR: Unexpected JSX expression that aborted the whole scan and skipped pre-bundling. The
    scan transform now uses the classic JSX runtime, which lowers JSX to bare
    React.createElement calls without injecting any import: the scan output
    is never executed, it only exists so rolldown can walk the import graph,
    so the undefined identifier is harmless. Backport of the fix already on
    the 3.0.0-next line.
  • 5d6846c: When the root config declares test.projects and leaves test.sharedViteServer unset, the plugin now sets it to false so every inline project resolves its own Vite config, as under Vitest 4. An explicit value is respected. Vitest 5 defaults the option to true, and a shared inline project takes its test options from the raw root block captured before any config hook runs, so it lost everything the plugin injects (the jsdom default, the @testing-library/jest-dom setup file, server.deps). Ports #​370; refs #​369.
  • 32adc90: In Vitest DOM tests (the jsdom defau

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (in timezone Europe/Oslo)

  • Branch creation
    • "before 09:00 on monday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@coderabbitai

coderabbitai Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: fe84745d-4aca-4ce0-bab5-b006784180c7

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@renovate
renovate Bot force-pushed the renovate/all-patch-dependencies branch from a1ca0c6 to a4dc488 Compare October 26, 2026 20:37
@renovate renovate Bot changed the title chore(deps): Update dependency ultralytics to v8.4.189 chore(deps): Update dependency ultralytics to v8.4.190 Oct 26, 2026
@renovate
renovate Bot force-pushed the renovate/all-patch-dependencies branch from a4dc488 to f77aba2 Compare October 27, 2026 03:23
@renovate renovate Bot changed the title chore(deps): Update dependency ultralytics to v8.4.190 chore(deps): Update all patch dependencies Oct 27, 2026
@renovate
renovate Bot force-pushed the renovate/all-patch-dependencies branch 24 times, most recently from 6c222be to fcf3589 Compare November 2, 2026 17:37
@renovate
renovate Bot force-pushed the renovate/all-patch-dependencies branch 16 times, most recently from 468db90 to a98d3be Compare November 14, 2026 07:52
@renovate
renovate Bot force-pushed the renovate/all-patch-dependencies branch 12 times, most recently from a7b0347 to 1a712f2 Compare November 16, 2026 08:51
@renovate
renovate Bot force-pushed the renovate/all-patch-dependencies branch from 1a712f2 to 79f57fd Compare November 16, 2026 20:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants