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

renovate · 2025-08-04T05:05:32Z

This PR contains the following updates:

Package	Change	Type	Update
@nuxt/eslint-config (source)	`^1.7.1` -> `^1.9.0`	devDependencies	minor
actions/checkout	`v4.2.2` -> `v4.3.0`	action	minor
actions/github-script	`v7.0.1` -> `v7.1.0`	action	minor
crawler-user-agents	`^1.15.0` -> `^1.21.0`	devDependencies	minor
eslint (source)	`^9.32.0` -> `^9.37.0`	devDependencies	minor
playwright (source)	`^1.54.1` -> `^1.56.0`	devDependencies	minor
pnpm (source)	`10.13.1` -> `10.18.2`	packageManager	minor
typescript (source)	`^5.8.3` -> `^5.9.3`	devDependencies	minor

Release Notes

nuxt/eslint (@nuxt/eslint-config)

`v1.9.0`

Compare Source

🚀 Features

Update plugins - by @antfu (b80cb)

🐞 Bug Fixes

Add defineNuxtConfig as ESLint's globals, close #603 - by @antfu in #603 (2e67f)

View changes on GitHub

`v1.8.0`

Compare Source

🚀 Features

Update plugins - by @antfu (932a7)

View changes on GitHub

actions/checkout (actions/checkout)

actions/github-script (actions/github-script)

`v7.1.0`

Compare Source

What's Changed

Upgrade husky to v9 by @benelan in #482
Add workflow file for publishing releases to immutable action package by @Jcambass in #485
Upgrade IA Publish by @Jcambass in #486
Fix workflow status badges by @joshmgross in #497
Update usage of actions/upload-artifact by @joshmgross in #512
Clear up package name confusion by @joshmgross in #514
Update dependencies with npm audit fix by @joshmgross in #515
Specify that the used script is JavaScript by @timotk in #478
chore: Add Dependabot for NPM and Actions by @nschonni in #472
Define permissions in workflows and update actions by @joshmgross in #531
chore: Add Dependabot for .github/actions/install-dependencies by @nschonni in #532
chore: Remove .vscode settings by @nschonni in #533
ci: Use github/setup-licensed by @nschonni in #473
make octokit instance available as octokit on top of github, to make it easier to seamlessly copy examples from GitHub rest api or octokit documentations by @iamstarkov in #508
Remove octokit README updates for v7 by @joshmgross in #557
docs: add "exec" usage examples by @neilime in #546
Bump ruby/setup-ruby from 1.213.0 to 1.222.0 by @dependabot[bot] in #563
Bump ruby/setup-ruby from 1.222.0 to 1.229.0 by @dependabot[bot] in #575
Clearly document passing inputs to the script by @joshmgross in #603
Update README.md by @nebuk89 in #610

New Contributors

@benelan made their first contribution in #482
@Jcambass made their first contribution in #485
@timotk made their first contribution in #478
@iamstarkov made their first contribution in #508
@neilime made their first contribution in #546
@nebuk89 made their first contribution in #610

Full Changelog: actions/github-script@v7...v7.1.0

monperrus/crawler-user-agents (crawler-user-agents)

`v1.21.0`

Compare Source

`v1.20.0`

Compare Source

`v1.19.0`

Compare Source

`v1.18.0`

Compare Source

`v1.17.0`

Compare Source

`v1.16.0`

Compare Source

eslint/eslint (eslint)

`v9.37.0`

Compare Source

`v9.36.0`

Compare Source

`v9.35.0`

Compare Source

`v9.34.0`

Compare Source

`v9.33.0`

Compare Source

microsoft/playwright (playwright)

`v1.56.0`

Compare Source

`v1.55.1`

Compare Source

Highlights

#37479 - [Bug]: Upgrade Chromium to 140.0.7339.186.
#37147 - [Regression]: Internal error: step id not found.
#37146 - [Regression]: HTML reporter displays a broken chip link when there are no projects.
#37137 - Revert "fix(a11y): track inert elements as hidden".

Browser Versions

Chromium 140.0.7339.186
Mozilla Firefox 141.0
WebKit 26.0

This version was also tested against the following stable channels:

Google Chrome 139
Microsoft Edge 139

`v1.55.0`

Compare Source

`v1.54.2`

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/36714 - [Regression]: Codegen is not able to launch in Administrator Terminal on Windows (ProtocolError: Protocol error)https://github.com/microsoft/playwright/issues/368288 - [Regression]: Playwright Codegen keeps spamming with selected optiohttps://github.com/microsoft/playwright/issues/3681010 - [Regression]: Starting Codegen with target language doesn't work anymore

Browser Versions

Chromium 139.0.7258.5
Mozilla Firefox 140.0.2
WebKit 26.0

This version was also tested against the following stable channels:

Google Chrome 140
Microsoft Edge 140

pnpm/pnpm (pnpm)

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

microsoft/TypeScript (typescript)

`v5.9.3`

Compare Source

`v5.9.2`

Compare Source

Configuration

📅 Schedule: Branch creation - "on Monday" (UTC), 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.

github-actions bot added 3.x chore labels Aug 4, 2025

renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 6aec344 to 72700b5 Compare August 11, 2025 11:28

renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 8b7c909 to 01c34d6 Compare August 20, 2025 08:36

renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from cb15de3 to 0dd862e Compare August 22, 2025 23:58

renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from bf2a361 to 7c0ddd7 Compare September 5, 2025 19:01

renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from e5789bd to eaa6b6b Compare September 14, 2025 01:12

renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 351dd8c to 93927c6 Compare September 23, 2025 11:55

renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 5857274 to c23377b Compare October 2, 2025 16:11

renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 0e4c9e9 to efb3022 Compare October 6, 2025 15:36

renovate bot force-pushed the renovate/all-minor-patch branch from efb3022 to 5ef1a2d Compare October 9, 2025 11:35

chore(deps): update all non-major dependencies

892c5e6

renovate bot force-pushed the renovate/all-minor-patch branch from 5ef1a2d to 892c5e6 Compare October 9, 2025 23:43

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

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

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

renovate bot commented Aug 4, 2025 •

edited

Loading

Uh oh!

Uh oh!

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

Are you sure you want to change the base?

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

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

🚀 Features

🐞 Bug Fixes

🚀 Features

What's Changed

New Contributors

What's Changed

New Contributors

Highlights

Browser Versions

Highlights

Browser Versions

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!

Uh oh!

renovate bot commented Aug 4, 2025 •

edited

Loading