Skip to content

chore(deps): update all non-major dependencies - #424

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

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

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 Type Update Pending
@tanstack/query-core (source) ^5.104.5 → ^5.105.3 age confidence pnpm.catalog.default minor 5.106.1 (+1)
@vitejs/plugin-react (source) ^6.1.2 → ^6.2.1 age confidence pnpm.catalog.default minor
@vue/language-core (source) ^3.3.13 → ^3.3.14 age confidence pnpm.catalog.default patch
eslint (source) ^10.13.0 → ^10.14.0 age confidence pnpm.catalog.default minor
globals ^17.13.0 → ^17.14.0 age confidence pnpm.catalog.default minor
nx (source) 24.0.2 → 24.0.3 age confidence pnpm.catalog.default patch 24.0.4
pnpm (source) 12.14.0 → 12.17.0 age confidence packageManager minor 12.18.0
pnpm (source) >=12.14.0 → >=12.17.0 age confidence engines minor 12.18.0
semver ^7.8.5 → ^7.8.6 age confidence pnpm.catalog.default patch
tsdown (source) ^0.23.1 → ^0.23.4 age confidence pnpm.catalog.default patch 0.23.5
typescript-eslint (source) ^8.72.0 → ^8.72.1 age confidence pnpm.catalog.default patch
vite (source) ^8.3.4 → ^8.3.5 age confidence pnpm.catalog.default patch 8.3.6
vitest (source) ^5.0.5 → ^5.1.0 age confidence pnpm.catalog.default minor
zizmorcore/zizmor-action v0.8.0 → v0.8.1 age confidence action patch

⚠️ Renovate does not enforce Minimum Release Age for bump, lockfileUpdate, or rollback updates, so these are raised without a Minimum Release Age check. You will need to manually validate the Minimum Release Age for these package(s).


Release Notes

TanStack/query (@​tanstack/query-core)

v5.105.3

Compare Source

Patch Changes
  • #​11537 3f4de1b - Prevent a cancelled retry from pausing the query when its retry delay expires.

  • #​12497 969e580 - Allow static queries without data to refetch after reset, invalidation, or an explicit refetch. A query is static only when it has data.

v5.105.2

Compare Source

Patch Changes
  • #​10969 2ee2fd9 - Fix infinite queries to respect a reduced maxPages limit when fetching in either direction.

  • #​12480 8d0dc27 - Exclude status from the filters accepted by QueryClient.isMutating, useIsMutating, and injectIsMutating. These APIs always count mutations with status: 'pending'.

  • #​12442 e69cac6 - Handle the rejection of a paused refetch started by refetchQueries with throwOnError, so cancelling it later no longer causes an unhandled CancelledError.

  • #​12447 f2215d2 - Use () => void instead of the DOM-only VoidFunction type in addConsumeAwareSignal, so the published declarations type-check without the DOM lib.

  • #​10777 86e7957 - Fix shallowEqualObjects to compare own property keys and values and ignore inherited properties. Objects with different own keys now compare as unequal, including when the differing values are undefined.

  • #​12489 b6576b3 - Keep all callers of an in-flight query waiting for the replacement fetch when invalidation cancels it, including after repeated invalidations.

  • #​12481 af0e0ef - Prevent cancelled streamed queries from writing to the cache or starting a delayed stream, even when the stream does not consume the abort signal.

  • #​11788 05d9b6a - Clear isPaused on a mutation that can start once its onMutate resolves, so it is no longer dehydrated and resumed a second time while its request is in flight.

v5.105.1

Compare Source

Patch Changes
  • #​12406 6f8a48d - Reduce temporary allocations when checking tracked result properties for observer notifications.

  • #​12390 18e54bf - Exclude fetchStatus from the filters accepted by QueryClient.isFetching, useIsFetching, and injectIsFetching. These APIs always count queries with fetchStatus: 'fetching'.

v5.105.0

Compare Source

No changes in this release.

vitejs/vite-plugin-react (@​vitejs/plugin-react)

v6.2.1

Compare Source

Fix refreshInclude and refreshExclude options not working (#​1543)

Fix mistake from #​1516

v6.2.0

Compare Source

Add refreshInclude and refreshExclude options (#​1516)

Add refreshInclude and refreshExclude options to skip fast refresh for certain files that won't run in the browser.

Expand oxc-transform-react peer dependency range (#​1540)

The peer dependency version range for oxc-transform-react was expanded from ^0.152.0 to >=0.152.0 <0.157.0.

Expand @rolldown/plugin-babel peer dependency range (#​1541)

The peer dependency version range for @rolldown/plugin-babel was expanded from ^0.1.7 || ^0.2.0 to ^0.1.7 || ^0.2.0 || ^0.3.0.

vuejs/language-tools (@​vue/language-core)

v3.3.14

Compare Source

language-core
  • fix: isolate template virtual code from setup control flow (d31557b)
  • fix: re-assert dot-value bindings in template closures (4524874) (f9c908f) (b65e458)
  • fix: avoid TS2454 from the withDotValue assertion (c774144)
  • fix: use a const type parameter in __VLS_unwrap to keep literal bindings on TS 7.1 (ce6c1de)
  • fix: avoid never slot props for dynamic slot names in generic components (7957e7f)
  • fix: omit emitted events from inherited attrs of generic components (2d94d89)
  • fix: check bindings of generic directive hooks (0cb7d92)
  • fix: wrap the v-model assignment target in parentheses (9bb1dc9)
  • fix: type the $event parameter of inline handlers explicitly (d3b42a1)
  • fix: type unknown components without diagnostic filters (b3909a3)
  • fix: keep leading @ts-nocheck and /// <reference> effective in script setup (c2e2e6f)
  • fix: declare component context vars before slot code (b7c773d)
  • fix: avoid non-null assertion in JS slot codegen (5633525)
  • fix: restore tag navigation for barrel imports (6358d15)
  • fix: map the whole hyphenated directive name in the auto-import access (beb0151)
language-service
  • fix: prevent crash on malformed html.customData configuration (3961653)
typescript-plugin
  • fix: show unwrapped type when hovering setup refs in template (c742c14)

Contributors: @​johnsoncodehk, @​lazerg, @​ValentinYoushkevich, @​so1ve, @​WangKepeople

eslint/eslint (eslint)

v10.14.0

Compare Source

Features

  • d23a7f9 feat: fix property descriptor handling in func-name-matching (#​21400) (xbinaryx)

Bug Fixes

Documentation

  • 0f94f47 docs: remove zh-hans from docs language switcher (#​21437) (lumir)
  • dab466e docs: Update README (GitHub Actions Bot)
  • 97431f8 docs: replace --rulesdir with a virtual plugin in custom rules docs (#​21452) (Pixel)
  • 7697550 docs: Update README (GitHub Actions Bot)
  • 0c699d5 docs: Remove Tidelift commercial support (#​21416) (Milos Djermanovic)
  • 0880666 docs: update loadESLint() documentation for v10 (#​21374) (Minseon Kim)
  • e06fe87 docs: Revise AI acknowledgment options in PR template (#​21414) (Nicholas C. Zakas)

Chores

  • 0e2ab70 ci: disable eslint-plugin-unicorn ecosystem test (#​21462) (Francesco Trotta)
  • 6e3f988 chore: update github/codeql-action action to v4.39.1 (#​21450) (renovate[bot])
  • a031c40 chore: update ecosystem plugins (#​21445) (ESLint Bot)
  • 67d2ca2 chore: add troubleshooting page URL to circular fixes warning message (#​21429) (Milos Djermanovic)
  • 276021d chore: update github/codeql-action action to v4.39.0 (#​21432) (renovate[bot])
  • 449724e chore: update ecosystem plugins (#​21420) (ESLint Bot)
  • 8ffeb8c chore: update dependency prettier to v3.9.10 (#​21417) (renovate[bot])
sindresorhus/globals (globals)

v17.14.0

Compare Source


nrwl/nx (nx)

v24.0.3

Compare Source

24.0.3 (2026-10-30)
🩹 Fixes
  • angular-rspack: print diagnostic positions and full warning text (#​37637, #​37431)
  • core: fix entryWhenNoChanges from adding empty lines to changelogs (#​36516)
  • core: detect package manager from workspace root in pnpm workspaces (#​35003, #​32579)
  • core: resolve workspace-provided packages from the workspace root (#​37272)
  • core: recover project dependencies after configuration errors (#​37611)
  • core: fail run-commands tasks whose command cannot start (#​37628)
  • core: report continuous dependency inputs in nx show target --json (#​37649)
  • core: report skipped tasks and count summaries against the run total (#​37626)
  • core: load angular.json projects for nx executors converted to builders (#​37645, #​33651)
  • core: keep claude md nx block that imports agents md (#​37646)
  • core: honor NO_PROXY forms and NODE_EXTRA_CA_CERTS in readyWhen url probes (#​37676)
  • core: support pnpm global virtual store installs in nx migrate (#​37653, #​37392)
  • core: recover from native cache load failures (#​37652)
  • core: bump undici to 7.30.1 to patch security advisories (#​37685, #​37331)
  • dotnet: pass configuration parameter for dotnet test and clean (#​36222)
  • graph: reset graph on external select all (#​36944)
  • graph: use current nx brand favicon in graph client (#​37655)
  • js: keep root tsconfig references to non-project tsconfig files (#​37266)
  • js: exclude node_modules from tailwind dependency glob patterns (#​37657, #​37343)
  • linter: reuse the project graph under bun lint (#​37641)
  • misc: read nx.dev agent skills from generated/.agents/skills (#​37681)
  • nextjs: make inferred build depend on dependency typecheck in ts solution setups (#​37647, #​36757)
  • nx-cloud: hand the nx-cloud bin's command line to the bundle's runCLI (#​37605)
  • nx-cloud: declare nx logout's URL argument and --all (#​37579)
  • nx-plugin: keep create-package e2e package managers consistent (#​37651)
  • rspack: warn when the ignored transformers option is set (#​37643, #​36875)
  • testing: exclude all generated jest config extensions from the production named input (#​37070, #​36978)
  • testing: make atomized jest targets run only their own test file (#​37625)
  • webpack: convert webpack configs of projects served by the js node executor (#​37644, #​36389)
❤️ Thank You
pnpm/pnpm (pnpm)

v12.17.0: pnpm 12.17

Compare Source

pnpm 12.17.0 adds pnpm peers check --global, dependency-group selectors and wildcards in overrides, and runtime, package manager, Cargo, and Python updates in pnpm outdated and pnpm update. It also fixes files that other users could not read in Docker images, and repeat installs that missed changes to local dependencies.

Minor Changes
  • pnpm peers check now accepts --global (-g) to check globally installed packages. After a global install or update, the peer dependency warning now suggests pnpm peers check -g #​17504.

  • pnpm outdated and pnpm update now inspect and update package manager and runtime versions in devEngines.packageManager, packageManager, devEngines.runtime, engines.runtime, and runtime: dependencies. With cargo.enabled or python.enabled, pnpm outdated and pnpm update also inspect and update Cargo dependencies in Cargo.toml and Cargo.lock and Python dependencies in pyproject.toml and pylock.toml.

  • overrides selectors now support :prod, :optional, and :peer pseudo-selectors that target a single dependency group. They also support * wildcard patterns on parent and target package names. An override with a non-range value, such as npm: or file:, no longer adds a peer dependency to dependencies. Removing an optional dependency with "-" now also removes the duplicate entry from dependencies #​5391.

Patch Changes
Installing packages
  • Files that pnpm creates in a project now get the permissions the umask gives any new file, such as 0644. Before, several of them were readable only by the user who ran pnpm, which broke Docker images that run as a different user #​17435.

    The fix applies to:

    • node_modules/.pnpm-workspace-state-v1.json. A different user running pnpm run reinstalled the dependencies because it could not read this file.
    • pnpm-workspace.yaml
    • the files written by pnpm deploy
    • patch files from pnpm patch-commit
    • the lockfile restored by pnpm dedupe --check
    • the Cargo and Python files that pnpm writes

    When pnpm edits an existing file, the file keeps its permissions.

  • pnpm install no longer writes broken dependency links when the project's node_modules is a symlink to another directory, such as another project's node_modules. The install reported success, but the links it wrote did not resolve #​17448.

  • Commands installed with pnpm add --global now find the dependencies that pnpm hoists for their package. A package that loads a dependency it does not declare, such as a native addon's platform-specific package, failed with "Cannot find module". Reinstall such a package with pnpm add --global to update its existing command #​17503.

  • When pnpm switches to the version a project pins, it now installs that version's native binary for the current host, even if the project's supportedArchitectures excludes the host. Before, pnpm could not use the pinned version and kept running the installed one. pnpm also repairs a pinned version that an earlier install left without the host's binary.

  • With the global virtual store, a change to a dependency of one package in a dependency cycle now gives every package in that cycle a new directory. Before, the other packages kept their directories and still linked the old copy of the changed package, so the project could load two copies of it #​17466.

    Packages in a dependency cycle, and packages that depend on one, move to new global virtual store directories once after this update. Those that run a build miss the side-effects cache once.

  • With nodeLinker: hoisted, when two workspace projects need the same package version and it cannot be hoisted to the root, each project now keeps the copy installed in its own node_modules. Build scripts run in each of these copies. Before, the second project's copy was replaced with a symlink to the first project's, so every repeat install imported it again #​17498.

  • The Node.js latest selector now chooses the newest stable release #​17490.

  • Hardlinking from the store now stats each store file once per install. Since pnpm 12.8.0, a store file was stat'ed again for every package that links it. On an offline install of a large workspace, that added up to 15% system CPU #​17500.

Repeat installs and local dependencies
  • pnpm install --frozen-lockfile no longer reports an outdated lockfile right after the install that wrote it. This happened when a pnpmfile readPackage hook or packageExtensions changed the dependencies or peer dependencies of a local directory dependency outside the workspace projects. It affected a file: dependency, an injected workspace:../dir dependency outside the workspace patterns, and an injected workspace package left out by --filter #​17447 #​17473.

    A repeat pnpm install now takes the fast path when ignoredOptionalDependencies removes an optional dependency of a file: directory dependency. It used to resolve again on every run.

  • pnpm install now resolves again after an edit to an injected workspace:../dir dependency outside the workspace patterns under a shared lockfile. It used to keep the lockfile unchanged. The next pnpm install --frozen-lockfile then failed #​17476.

  • pnpm install now resolves a local directory again after its package.json changes when an override or a package extension adds it to the dependencies of a registry package. pnpm install --frozen-lockfile fails on a lockfile that still records the old dependencies of such a directory #​17486.

  • With injectWorkspacePackages and per-project lockfiles, pnpm install now updates a project's lockfile when a local tarball that an injected workspace project depends on is replaced. The project's lockfile kept the old version and integrity before.

  • pnpm install now detects a change to a local tarball or directory that only a pnpmfile readPackage hook depends on. A repeat install reported "Already up to date" and kept the old contents before pnpm/tasks#227.

  • pnpm install now relinks a workspace: or link: dependency whose link was deleted from node_modules. It used to report "Already up to date" and leave the link missing #​17485.

  • A repeat pnpm install reports "Already up to date" again when a pnpmfile readPackage hook changes the dependencies of a workspace project. Since 12.15.0, every such install ran in full #​17468.

    After an edit to a project's package.json, pnpm install and verifyDepsBeforeRun now run the pnpmfile's readPackage hook on the edited manifest before comparing it with the lockfile. They could report the project up to date when the hook rewrote the edited dependency to a specifier the lockfile did not record.

Adding and updating dependencies
  • pnpm update --latest with package selectors now updates the dependencies of the selected packages within their declared ranges. Excluded packages and their dependencies keep their locked versions #​17444.

  • pnpm add <pkg>@<tag> now uses a catalog entry set to that same dist-tag. The dependency is saved as catalog: and the entry stays as written pnpm/tasks#225.

    When pnpm add adds a new dist-tag such as vue@legacy to a catalog, the catalog entry records the exact version the tag points to. The same applies to a dependency added without a version when the tag setting names a dist-tag other than latest.

  • pnpm add now saves the resolved version range of an npm alias. For example, pnpm add v2@npm:vue and pnpm add v2@npm:vue@^3.0.0 both save npm:vue@^3.5.13.

Running scripts and commands
  • Programs that a script or pnpm exec command leaves running, such as a browser opened by the open package, now outlive pnpm exactly when they would outlive the command run without pnpm. Before, on Windows, a failed command, Ctrl+C, or a closed terminal ended all of them. pnpm still ends them when it is killed or crashes.

    When a recursive or parallel run bails, the scripts still running now receive SIGTERM on Unix and are killed only if they are still running two seconds later. On Windows, everything those scripts started is ended, including detached processes whose parent has already exited. Before, a bail killed them at once #​17465.

  • On Windows, the shell shim of a .cmd or .bat bin now runs it under Git Bash when MSYS argument conversion is off, such as with MSYS_NO_PATHCONV=1 or MSYS2_ARG_CONV_EXCL='*'. The shim used to start an interactive cmd.exe prompt #​17480.

  • pnx and pnpm create now run the command in the directory selected by --dir or --workspace-root. Without either flag, the command still runs in the directory pnpm was started in.

  • pnpm --env-file now reads files the way node --env-file does. Values are taken as written, so $VAR is no longer expanded and Windows paths such as C:\Users\me load unchanged. A file is no longer rejected for its contents.

Settings and messages
  • pnpm version no longer creates a git commit and tag when gitTagVersion is set to false #​17460.

  • pnpm publish now reads the publishBranch setting from pnpm-workspace.yaml and from PNPM_CONFIG_PUBLISH_BRANCH. The --publish-branch flag overrides it.

  • pnpm now accepts --strict-ssl and --local-address <ip> on the command line.

  • pnpm doctor uses a 15-second timeout when checking registry connectivity.

  • pnpm-workspace.yaml parse errors now report ERR_PNPM_INVALID_SETTING.

  • The error for a dependency with an invalid name in a project's manifest now names the project's directory. It used to say only "The current package", which did not tell which workspace project to fix #​17475.

Platinum Sponsors

Bit OpenAI Notion
CodeRabbit Cloudflare

Gold Sponsors

Sanity Discord Vite
SerpApi Stackblitz Workleap
Nx Latitude Syntax

v12.16.1: pnpm 12.16.1

Compare Source

This release fixes pnpm install hanging on a cold store in workspaces that install Cargo crates, and pnpm pack shipping a file that files excludes by name.

Patch Changes
  • pnpm install no longer hangs on a cold store in a workspace that also installs Cargo crates or a Rust toolchain.

  • pnpm pack and pnpm publish now apply a files entry that names a file after the glob and directory entries, as npm does. A file excluded by name, such as !dist/index.js, stays out even when a later dist/** matches it. A file named by its path, such as lib/secret.js, ships even when a later !lib/*.js matches it.

  • pnpm install no longer leaves a broken symlink in an injected workspace dependency when the package links to a file outside its published files and pnpm imports by hardlink. Installing a git dependency now skips internal directory symlinks when importing its files into the store.

  • pnpm install now relinks a command that a workspace project renames into the projects that depend on it when sharedWorkspaceLockfile is false pnpm/tasks#224.

  • pnpm install and pnpm rebuild now refresh privately hoisted .bin shims in node_modules/.pnpm/node_modules/.bin after a dependency build replaces a script target with a native executable #​17402.

  • pnpm install now reads a package's manifest to decide its peer dependencies when it updates an existing lockfile, as it does when it resolves from scratch.

  • Commands, pnpm --version, pnpm self-update, and invocations with unknown flags now apply the same packageManager and devEngines.packageManager settings when switching to the pinned pnpm version or recording it in pnpm-lock.yaml. `--config.<

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


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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.

@renovate renovate Bot added the dependencies Pull requests that update a dependency file label Oct 26, 2026
@changeset-bot

changeset-bot Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: ccccf91

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions

Copy link
Copy Markdown
Contributor

🚀 Changeset Version Preview

No changeset entries found. Merging this PR will not cause a version bump for any packages.

@nx-cloud

nx-cloud Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

🤖 Nx Cloud AI Fix Eligible

An automatically generated fix could have helped fix failing tasks for this run, but Self-healing CI is disabled for this workspace. Visit workspace settings to enable it and get automatic fixes in future runs.

To disable these notifications, a workspace admin can disable them in workspace settings.


View your CI Pipeline Execution ↗ for commit ccccf91

Command Status Duration Result
nx affected --targets=test:sherif,test:docs,tes... ❌ Failed 11s View ↗
nx run-many --target=build ✅ Succeeded 6s View ↗

☁️ Nx Cloud last updated this comment at 2026-11-06 01:49:00 UTC

@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: 79635f53-342c-4af4-bb8c-3edfe3d781cd

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

@pkg-pr-new

pkg-pr-new Bot commented Oct 26, 2026 •

Copy link
Copy Markdown
npm i https://pkg.pr.new/@tanstack/eslint-config@424
npm i https://pkg.pr.new/@tanstack/publish-config@424
npm i https://pkg.pr.new/@tanstack/typedoc-config@424
npm i https://pkg.pr.new/@tanstack/vite-config@424

commit: ccccf91

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from a2b0f46 to d97ff5a Compare October 26, 2026 13:37
@socket-security

socket-security Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 11 times, most recently from d6f9b2f to cef273d Compare November 2, 2026 21:35
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 3ef5c9c to 88fc800 Compare November 3, 2026 01:46
@renovate
renovate Bot requested a review from a team as a code owner November 3, 2026 01:46
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from aeb2cb9 to a3c5659 Compare November 5, 2026 14:59
@socket-security

socket-security Bot commented Nov 5, 2026 •

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Priority Alert  (click "▶" to expand/collapse) Action
Low priority
Low adoption: npm @yuku-toolchain/darwin-x64

Location: Package overview

From: pnpm-lock.yaml → npm/tsdown@0.23.5 → npm/@yuku-toolchain/darwin-x64@0.25.0

ℹ Read more on: This package | This alert | What are unpopular packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Unpopular packages may have less maintenance and contain other problems.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@yuku-toolchain/darwin-x64@0.25.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn
Low priority
Low adoption: npm @yuku-toolchain/linux-arm64

Location: Package overview

From: pnpm-lock.yaml → npm/tsdown@0.23.5 → npm/@yuku-toolchain/linux-arm64@0.25.0

ℹ Read more on: This package | This alert | What are unpopular packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Unpopular packages may have less maintenance and contain other problems.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@yuku-toolchain/linux-arm64@0.25.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn
Low priority
Low adoption: npm @yuku-toolchain/linux-x64

Location: Package overview

From: pnpm-lock.yaml → npm/tsdown@0.23.5 → npm/@yuku-toolchain/linux-x64@0.25.0

ℹ Read more on: This package | This alert | What are unpopular packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Unpopular packages may have less maintenance and contain other problems.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@yuku-toolchain/linux-x64@0.25.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn
Low priority
Low adoption: npm @yuku-toolchain/win32-arm64

Location: Package overview

From: pnpm-lock.yaml → npm/tsdown@0.23.5 → npm/@yuku-toolchain/win32-arm64@0.25.0

ℹ Read more on: This package | This alert | What are unpopular packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Unpopular packages may have less maintenance and contain other problems.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@yuku-toolchain/win32-arm64@0.25.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn
Low priority
Low adoption: npm @yuku-toolchain/win32-x64

Location: Package overview

From: pnpm-lock.yaml → npm/tsdown@0.23.5 → npm/@yuku-toolchain/win32-x64@0.25.0

ℹ Read more on: This package | This alert | What are unpopular packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Unpopular packages may have less maintenance and contain other problems.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@yuku-toolchain/win32-x64@0.25.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn

View full report

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from a3c5659 to ccccf91 Compare November 6, 2026 01:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants