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

renovate · 2025-08-04T02:11:09Z

This PR contains the following updates:

Package	Type	Update	Change
actions/checkout	action	minor	`v4.2.2` -> `v4.3.0`
node	uses-with	minor	`24` -> `24.10.0`
pnpm (source)	packageManager	minor	`10.13.1` -> `10.18.3`
pnpm/action-setup	action	minor	`v4.1.0` -> `v4.2.0`

Release Notes

actions/checkout (actions/checkout)

actions/node-versions (node)

`v24.10.0`: 24.10.0

Compare Source

Node.js 24.10.0

pnpm/pnpm (pnpm)

`v10.18.3`

Compare Source

Patch Changes

Fix a bug where pnpm would infinitely recurse when using verifyDepsBeforeInstall: install and pre/post install scripts that called other pnpm scripts #10060.
Fixed scoped registry keys (e.g., @scope:registry) being parsed as property paths in pnpm config get when --location=project is used #9362.
Remove pnpm-specific CLI options before passing to npm publish to prevent "Unknown cli config" warnings #9646.
Fixed EISDIR error when bin field points to a directory #9441.
Preserve version and hasBin for variations packages #10022.
Fixed pnpm config set --location=project incorrectly handling keys with slashes (auth tokens, registry settings) #9884.
When both pnpm-workspace.yaml and .npmrc exist, pnpm config set --location=project now writes to pnpm-workspace.yaml (matching read priority) #10072.
Prevent a table width error in pnpm outdated --long #10040.
Sync bin links after injected dependencies are updated by build scripts. This ensures that binaries created during build processes are properly linked and accessible to consuming projects #10057.

`v10.18.2`

Compare Source

Patch Changes

pnpm outdated --long should work #10040.
Replace ndjson with split2. Reduce the bundle size of pnpm CLI #10054.
pnpm dlx should request the full metadata of packages, when minimumReleaseAge is set #9963.
pnpm version switching should work when the pnpm home directory is in a symlinked directory #9715.
Fix EPIPE errors when piping output to other commands #10027.

`v10.18.1`

Compare Source

Patch Changes

Don't print a warning, when --lockfile-only is used #8320.
pnpm setup creates a command shim to the pnpm executable. This is needed to be able to run pnpm self-update on Windows #5700.
When using pnpm catalogs and running a normal pnpm install, pnpm produced false positive warnings for "skip adding to the default catalog because it already exists". This warning now only prints when using pnpm add --save-catalog as originally intended.

`v10.18.0`

Compare Source

Minor Changes

Added network performance monitoring to pnpm by implementing warnings for slow network requests, including both metadata fetches and tarball downloads.

Added configuration options for warning thresholds: fetchWarnTimeoutMs and fetchMinSpeedKiBps.
Warning messages are displayed when requests exceed time thresholds or fall below speed minimums

Related PR: #10025.

Patch Changes

Retry filesystem operations on EAGAIN errors #9959.
Outdated command respects minimumReleaseAge configuration #10030.
Correctly apply the cleanupUnusedCatalogs configuration when removing dependent packages.
Don't fail with a meaningless error when scriptShell is set to false #8748.
pnpm dlx should not fail when minimumReleaseAge is set #10037.

`v10.17.1`

Compare Source

Patch Changes

When a version specifier cannot be resolved because the versions don't satisfy the minimumReleaseAge setting, print this information out in the error message #9974.
Fix state.json creation path when executing pnpm patch in a workspace project #9733.
When minimumReleaseAge is set and the latest tag is not mature enough, prefer a non-deprecated version as the new latest #9987.

`v10.17.0`

Compare Source

Minor Changes

The minimumReleaseAgeExclude setting now supports patterns. For instance:
```
minimumReleaseAge: 1440
minimumReleaseAgeExclude:
  - "@&#8203;eslint/*"
```
Related PR: #9984.

Patch Changes

Don't ignore the minimumReleaseAge check, when the package is requested by exact version and the packument is loaded from cache #9978.
When minimumReleaseAge is set and the active version under a dist-tag is not mature enough, do not downgrade to a prerelease version in case the original version wasn't a prerelease one #9979.

`v10.16.1`

Compare Source

Patch Changes

The full metadata cache should be stored not at the same location as the abbreviated metadata. This fixes a bug where pnpm was loading the abbreviated metadata from cache and couldn't find the "time" field as a result #9963.
Forcibly disable ANSI color codes when generating patch diff #9914.

`v10.16.0`

Compare Source

Minor Changes

There have been several incidents recently where popular packages were successfully attacked. To reduce the risk of installing a compromised version, we are introducing a new setting that delays the installation of newly released dependencies. In most cases, such attacks are discovered quickly and the malicious versions are removed from the registry within an hour.

The new setting is called minimumReleaseAge. It specifies the number of minutes that must pass after a version is published before pnpm will install it. For example, setting minimumReleaseAge: 1440 ensures that only packages released at least one day ago can be installed.

If you set minimumReleaseAge but need to disable this restriction for certain dependencies, you can list them under the minimumReleaseAgeExclude setting. For instance, with the following configuration pnpm will always install the latest version of webpack, regardless of its release time:
```
minimumReleaseAgeExclude:
  - webpack
```
Related issue: #9921.
Added support for finders #9946.

In the past, pnpm list and pnpm why could only search for dependencies by name (and optionally version). For example:
```
pnpm why minimist
```
prints the chain of dependencies to any installed instance of minimist:
```
verdaccio 5.20.1
├─┬ handlebars 4.7.7
│ └── minimist 1.2.8
└─┬ mv 2.1.1
  └─┬ mkdirp 0.5.6
    └── minimist 1.2.8
```
What if we want to search by other properties of a dependency, not just its name? For instance, find all packages that have react@17 in their peer dependencies?

This is now possible with "finder functions". Finder functions can be declared in .pnpmfile.cjs and invoked with the --find-by=<function name> flag when running pnpm list or pnpm why.

Let's say we want to find any dependencies that have React 17 in peer dependencies. We can add this finder to our .pnpmfile.cjs:
```
module.exports = {
  finders: {
    react17: (ctx) => {
      return ctx.readManifest().peerDependencies?.react === "^17.0.0";
    },
  },
};
```
Now we can use this finder function by running:
```
pnpm why --find-by=react17
```
pnpm will find all dependencies that have this React in peer dependencies and print their exact locations in the dependency graph.
```
@&#8203;apollo/client 4.0.4
├── @&#8203;graphql-typed-document-node/core 3.2.0
└── graphql-tag 2.12.6
```
It is also possible to print out some additional information in the output by returning a string from the finder. For example, with the following finder:
```
module.exports = {
  finders: {
    react17: (ctx) => {
      const manifest = ctx.readManifest();
      if (manifest.peerDependencies?.react === "^17.0.0") {
        return `license: ${manifest.license}`;
      }
      return false;
    },
  },
};
```
Every matched package will also print out the license from its package.json:
```
@&#8203;apollo/client 4.0.4
├── @&#8203;graphql-typed-document-node/core 3.2.0
│   license: MIT
└── graphql-tag 2.12.6
    license: MIT
```

Patch Changes

Fix deprecation warning printed when executing pnpm with Node.js 24 #9529.
Throw an error if nodeVersion is not set to an exact semver version #9934.
pnpm publish should be able to publish a .tar.gz file #9927.
Canceling a running process with Ctrl-C should make pnpm run return a non-zero exit code #9626.

`v10.15.1`

Compare Source

Patch Changes

Fix .pnp.cjs crash when importing subpath #9904.
When resolving peer dependencies, pnpm looks whether the peer dependency is present in the root workspace project's dependencies. This change makes it so that the peer dependency is correctly resolved even from aliased npm-hosted dependencies or other types of dependencies #9913.

`v10.15.0`

Compare Source

Minor Changes

Added the cleanupUnusedCatalogs configuration. When set to true, pnpm will remove unused catalog entries during installation #9793.
Automatically load pnpmfiles from config dependencies that are named @*/pnpm-plugin-* #9780.
pnpm config get now prints an INI string for an object value #9797.
pnpm config get now accepts property paths (e.g. pnpm config get catalog.react, pnpm config get .catalog.react, pnpm config get 'packageExtensions["@babel/parser"].peerDependencies["@babel/types"]'), and pnpm config set now accepts dot-leading or subscripted keys (e.g. pnpm config set .ignoreScripts true).
pnpm config get --json now prints a JSON serialization of config value, and pnpm config set --json now parses the input value as JSON.

Patch Changes

Semi-breaking. When automatically installing missing peer dependencies, prefer versions that are already present in the direct dependencies of the root workspace package #9835.
When executing the pnpm create command, must verify whether the node version is supported even if a cache already exists #9775.
When making requests for the non-abbreviated packument, add */* to the Accept header to avoid getting a 406 error on AWS CodeArtifact #9862.
The standalone exe version of pnpm works with glibc 2.26 again #9734.
Fix a regression in which pnpm dlx pkg --help doesn't pass --help to pkg #9823.

`v10.14.0`

Compare Source

Minor Changes

Added support for JavaScript runtime resolution

Declare Node.js, Deno, or Bun in devEngines.runtime (inside package.json) and let pnpm download and pin it automatically.

Usage example:
```
{
  "devEngines": {
    "runtime": {
      "name": "node",
      "version": "^24.4.0",
      "onFail": "download" (we only support the "download" value for now)
    }
  }
}
```
How it works:
1. pnpm install resolves your specified range to the latest matching runtime version.
2. The exact version (and checksum) is saved in the lockfile.
3. Scripts use the local runtime, ensuring consistency across environments.
Why this is better:
1. This new setting supports also Deno and Bun (vs. our Node-only settings useNodeVersion and executionEnv.nodeVersion)
2. Supports version ranges (not just a fixed version).
3. The resolved version is stored in the pnpm lockfile, along with an integrity checksum for future validation of the Node.js content's validity.
4. It can be used on any workspace project (like executionEnv.nodeVersion). So, different projects in a workspace can use different runtimes.
5. For now devEngines.runtime setting will install the runtime locally, which we will improve in future versions of pnpm by using a shared location on the computer.
Related PR: #9755.
Add --cpu, --libc, and --os to pnpm install, pnpm add, and pnpm dlx to customize supportedArchitectures via the CLI #7510.

Patch Changes

Fix a bug in which pnpm add downloads packages whose libc differ from pnpm.supportedArchitectures.libc.
The integrities of the downloaded Node.js artifacts are verified #9750.
Allow dlx to parse CLI flags and options between the dlx command and the command to run or between the dlx command and -- #9719.
pnpm install --prod should removing hoisted dev dependencies #9782.
Fix an edge case bug causing local tarballs to not re-link into the virtual store. This bug would happen when changing the contents of the tarball without renaming the file and running a filtered install.
Fix a bug causing pnpm install to incorrectly assume the lockfile is up to date after changing a local tarball that has peers dependencies.

pnpm/action-setup (pnpm/action-setup)

`v4.2.0`

Compare Source

When there's a .npmrc file at the root of the repository, pnpm will be fetched from the registry that is specified in that .npmrc file #179

Configuration

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

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

♻ 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.

changeset-bot · 2025-08-04T02:11:13Z

⚠️ No Changeset found

Latest commit: abbcf11

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

coderabbitai · 2025-08-04T02:11:15Z

Important

Review skipped

Bot user detected.

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

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

ellipsis-dev

Important

Looks good to me! 👍

Reviewed everything up to 8e30b1d in 36 seconds. Click for details.

Reviewed 13 lines of code in 1 files
Skipped 0 files when reviewing.
Skipped posting 1 draft comments. View those below.
Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. package.json:74

Draft comment:
The packageManager version bump to [email protected] appears correct. Verify that all CI/scripts and local environments are compatible with this update.
Reason this comment was not posted:
Confidence changes required: 0% <= threshold 50% None

Workflow ID: wflow_STDquDw5bBN1GyZ9

^{You can customize}^{by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

github-actions · 2025-08-04T02:12:41Z

Coverage Report

Status	Category	Percentage	Covered / Total
🔴	Lines	83.17% (🎯 90%) 🟰 ±0%	1261 / 1516
🔴	Statements	83.17% (🎯 90%) 🟰 ±0%	1261 / 1516
🔴	Functions	81.55% (🎯 90%) 🟰 ±0%	84 / 103
🟢	Branches	86.56% (🎯 85%) 🟰 ±0%	348 / 402

File Coverage

File	Stmts	Branches	Functions	Lines	Uncovered Lines
Unchanged Files
packages/unuse-angular/src/index.ts	94.2%	100%	83.33%	94.2%	143-146
packages/unuse-react/src/index.ts	69.86%	68.18%	100%	69.86%	49-55, 58-71, 139-143, 152
packages/unuse-reactivity/src/index.ts	100%	100%	100%	100%
packages/unuse-reactivity/src/unComputed/index.ts	96%	93.33%	100%	96%	78-79
packages/unuse-reactivity/src/unEffect/index.ts	100%	100%	100%	100%
packages/unuse-reactivity/src/unEffectScope/index.ts	100%	100%	100%	100%
packages/unuse-reactivity/src/unReactiveSystem/index.ts	87.41%	88.88%	80%	87.41%	38-44, 92-93, 96-97, 100-103, 154-155, 188-189
packages/unuse-reactivity/src/unSignal/index.ts	100%	100%	100%	100%
packages/unuse-reactivity/src/unWatch/index.ts	100%	100%	100%	100%
packages/unuse-solid/src/index.ts	83.09%	86.95%	100%	83.09%	52-59, 69, 141-145
packages/unuse-vue/src/index.ts	100%	100%	100%	100%
packages/unuse/src/index.ts	0%	0%	0%	0%	1-15
packages/unuse/src/_framework/index.ts	81.53%	62.5%	100%	81.53%	48-49, 67-68, 76-77, 85-86, 94-95, 102-103
packages/unuse/src/_testUtils/angular.ts	100%	100%	100%	100%
packages/unuse/src/_testUtils/react.ts	100%	100%	100%	100%
packages/unuse/src/_testUtils/solid.ts	100%	100%	100%	100%
packages/unuse/src/_testUtils/vue.ts	100%	100%	100%	100%
packages/unuse/src/isClient/index.ts	100%	0%	100%	100%
packages/unuse/src/isObject/index.ts	100%	100%	100%	100%
packages/unuse/src/isWorker/index.ts	66.66%	0%	100%	66.66%	5
packages/unuse/src/toArray/index.ts	100%	50%	100%	100%
packages/unuse/src/toUnSignal/index.ts	87.71%	92.85%	100%	87.71%	81-87, 98-99, 113-120, 130
packages/unuse/src/tryOnScopeDispose/index.ts	77.77%	80%	50%	77.77%	11-14, 23-24, 35-36, 40-41
packages/unuse/src/unAccess/index.ts	73%	80%	66.66%	73%	43-44, 48-49, 66-67, 71, 80-81, 84-93, 97-98, 104-105, 114-115, 118-119, 122-123
packages/unuse/src/unRefElement/index.ts	75%	33.33%	100%	75%	29, 36-37
packages/unuse/src/unResolve/index.ts	92.66%	97.22%	71.42%	92.66%	71-72, 93-94, 125-128
packages/unuse/src/useEventListener/index.ts	96.34%	86.66%	100%	96.34%	192-193, 198
packages/unuse/src/useIntervalFn/index.ts	100%	100%	100%	100%
packages/unuse/src/useToggle/index.ts	100%	100%	100%	100%
packages/unuse/src/useWebSocket/index.ts	46.66%	41.66%	33.33%	46.66%	161-163, 203-212, 216-218, 222-224, 233-235, 244-256, 262-263, 270-275, 278-308, 311-312, 315-326, 330-355, 367-368

Generated in workflow #356 for commit abbcf11 by the Vitest Coverage Report Action

renovate bot requested a review from Shinigami92 as a code owner August 4, 2025 02:11

renovate bot added the c: dependencies label Aug 4, 2025

renovate bot requested a review from JounQin as a code owner August 4, 2025 02:11

renovate bot added the c: dependencies label Aug 4, 2025

ellipsis-dev bot reviewed Aug 4, 2025

View reviewed changes

renovate bot force-pushed the renovate/all-minor-patch branch from 8e30b1d to 5066d2d Compare August 10, 2025 14:28

renovate bot changed the title ~~chore(deps): update pnpm to v10.14.0~~ chore(deps): update all non-major dependencies Aug 10, 2025

renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from a6c11d4 to 3f367eb Compare August 15, 2025 02:37

renovate bot force-pushed the renovate/all-minor-patch branch from 3f367eb to 685e8a3 Compare August 19, 2025 17:36

renovate bot force-pushed the renovate/all-minor-patch branch from 685e8a3 to 846782d Compare August 28, 2025 07:43

renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from c96cd4c to afcf562 Compare September 11, 2025 02:42

renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from f4f1145 to b3d2aa4 Compare September 17, 2025 18:53

renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 46efefe to be0971d Compare September 26, 2025 02:26

renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 0ad05fb to e3da1f0 Compare October 8, 2025 10:56

renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 9c91242 to d00e7f3 Compare October 13, 2025 05:12

chore(deps): update all non-major dependencies

abbcf11

renovate bot force-pushed the renovate/all-minor-patch branch from d00e7f3 to abbcf11 Compare October 14, 2025 11:04

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

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

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

Uh oh!

renovate bot commented Aug 4, 2025 •

edited

Loading

Uh oh!

changeset-bot bot commented Aug 4, 2025 •

edited

Loading

Uh oh!

coderabbitai bot commented Aug 4, 2025 •

edited

Loading

Review skipped

Uh oh!

ellipsis-dev bot left a comment

Uh oh!

github-actions bot commented Aug 4, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Uh oh!

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

Are you sure you want to change the base?

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

Uh oh!

Conversation

renovate bot commented Aug 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

What's Changed

New Contributors

v24.10.0: 24.10.0

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Configuration

Uh oh!

changeset-bot bot commented Aug 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ No Changeset found

Uh oh!

coderabbitai bot commented Aug 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

ellipsis-dev bot left a comment

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented Aug 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Coverage Report

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate bot commented Aug 4, 2025 •

edited

Loading

`v24.10.0`: 24.10.0

changeset-bot bot commented Aug 4, 2025 •

edited

Loading

coderabbitai bot commented Aug 4, 2025 •

edited

Loading

github-actions bot commented Aug 4, 2025 •

edited

Loading