fix(deps): update all non-major dependencies #77

renovate · 2025-08-04T01:27:05Z

Note

Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to mend[bot].

This notice will be removed on 2025-10-07.

This PR contains the following updates:

Package	Change	Type	Update
@types/node (source)	`^22.17.0` -> `^22.18.8`	devDependencies	minor
@types/semver (source)	`^7.7.0` -> `^7.7.1`	devDependencies	patch
esbuild	`^0.25.8` -> `^0.25.10`	devDependencies	patch
fs-fixture	`^2.8.1` -> `^2.9.0`	devDependencies	minor
node	`22` -> `22.20.0`	uses-with	minor
pnpm (source)	`10.13.1` -> `10.18.1`	packageManager	minor
publint (source)	`^0.3.12` -> `^0.3.14`	dependencies	patch
typescript (source)	`^5.8.3` -> `^5.9.3`	devDependencies	minor

Release Notes

evanw/esbuild (esbuild)

`v0.25.10`

Compare Source

Fix a panic in a minification edge case (#4287)

This release fixes a panic due to a null pointer that could happen when esbuild inlines a doubly-nested identity function and the final result is empty. It was fixed by emitting the value undefined in this case, which avoids the panic. This case must be rare since it hasn't come up until now. Here is an example of code that previously triggered the panic (which only happened when minifying):
```
function identity(x) { return x }
identity({ y: identity(123) })
```
Fix @supports nested inside pseudo-element (#4265)

When transforming nested CSS to non-nested CSS, esbuild is supposed to filter out pseudo-elements such as ::placeholder for correctness. The CSS nesting specification says the following:

The nesting selector cannot represent pseudo-elements (identical to the behavior of the ':is()' pseudo-class). We’d like to relax this restriction, but need to do so simultaneously for both ':is()' and '&', since they’re intentionally built on the same underlying mechanisms.

However, it seems like this behavior is different for nested at-rules such as @supports, which do work with pseudo-elements. So this release modifies esbuild's behavior to now take that into account:
```
/* Original code */
::placeholder {
  color: red;
  body & { color: green }
  @&#8203;supports (color: blue) { color: blue }
}

/* Old output (with --supported:nesting=false) */
::placeholder {
  color: red;
}
body :is() {
  color: green;
}
@&#8203;supports (color: blue) {
   {
    color: blue;
  }
}

/* New output (with --supported:nesting=false) */
::placeholder {
  color: red;
}
body :is() {
  color: green;
}
@&#8203;supports (color: blue) {
  ::placeholder {
    color: blue;
  }
}
```

`v0.25.9`

Compare Source

Better support building projects that use Yarn on Windows (#3131, #3663)

With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the C: drive. The problem was as follows:
1. Yarn in Plug'n'Play mode on Windows stores its global module cache on the C: drive
2. Some developers put their projects on the D: drive
3. Yarn generates relative paths that use ../.. to get from the project directory to the cache directory
4. Windows-style paths don't support directory traversal between drives via .. (so D:\.. is just D:)
5. I didn't have access to a Windows machine for testing this edge case
Yarn works around this edge case by pretending Windows-style paths beginning with C:\ are actually Unix-style paths beginning with /C:/, so the ../.. path segments are able to navigate across drives inside Yarn's implementation. This was broken for a long time in esbuild but I finally got access to a Windows machine and was able to debug and fix this edge case. So you should now be able to bundle these projects with esbuild.
Preserve parentheses around function expressions (#4252)

The V8 JavaScript VM uses parentheses around function expressions as an optimization hint to immediately compile the function. Otherwise the function would be lazily-compiled, which has additional overhead if that function is always called immediately as lazy compilation involves parsing the function twice. You can read V8's blog post about this for more details.

Previously esbuild did not represent parentheses around functions in the AST so they were lost during compilation. With this change, esbuild will now preserve parentheses around function expressions when they are present in the original source code. This means these optimization hints will not be lost when bundling with esbuild. In addition, esbuild will now automatically add this optimization hint to immediately-invoked function expressions. Here's an example:
```
// Original code
const fn0 = () => 0
const fn1 = (() => 1)
console.log(fn0, function() { return fn1() }())

// Old output
const fn0 = () => 0;
const fn1 = () => 1;
console.log(fn0, function() {
  return fn1();
}());

// New output
const fn0 = () => 0;
const fn1 = (() => 1);
console.log(fn0, (function() {
  return fn1();
})());
```
Note that you do not want to wrap all function expressions in parentheses. This optimization hint should only be used for functions that are called on initial load. Using this hint for functions that are not called on initial load will unnecessarily delay the initial load. Again, see V8's blog post linked above for details.
Update Go from 1.23.10 to 1.23.12 (#4257, #4258)

This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4674 and CVE-2025-47907) from vulnerability scanners that only detect which version of the Go compiler esbuild uses.

privatenumber/fs-fixture (fs-fixture)

`v2.9.0`

Compare Source

Bug Fixes

types: readFile & writeFile to inherit fs types (5482c45)

Features

accept buffer as content (6b877a9)
add readdir (7ea32e6)
add readJson method (48f3f6e)
improve json methods (5aa7d57)

actions/node-versions (node)

`v22.20.0`: 22.20.0

Compare Source

Node.js 22.20.0

`v22.19.0`: 22.19.0

Compare Source

Node.js 22.19.0

`v22.18.0`: 22.18.0

Compare Source

Node.js 22.18.0

`v22.17.1`: 22.17.1

Compare Source

Node.js 22.17.1

`v22.17.0`: 22.17.0

Compare Source

Node.js 22.17.0

`v22.16.0`: 22.16.0

Compare Source

Node.js 22.16.0

`v22.15.1`: 22.15.1

Compare Source

Node.js 22.15.1

`v22.15.0`: 22.15.0

Compare Source

Node.js 22.15.0

`v22.14.0`: 22.14.0

Compare Source

Node.js 22.14.0

`v22.13.1`: 22.13.1

Compare Source

Node.js 22.13.1

`v22.13.0`: 22.13.0

Compare Source

Node.js 22.13.0

`v22.12.0`: 22.12.0

Compare Source

Node.js 22.12.0

`v22.11.0`: 22.11.0

Compare Source

Node.js 22.11.0

`v22.10.0`: 22.10.0

Compare Source

Node.js 22.10.0

`v22.9.0`: 22.9.0

Compare Source

Node.js 22.9.0

`v22.8.0`: 22.8.0

Compare Source

Node.js 22.8.0

`v22.7.0`: 22.7.0

Compare Source

Node.js 22.7.0

`v22.6.0`: 22.6.0

Compare Source

Node.js 22.6.0

`v22.5.1`: 22.5.1

Compare Source

Node.js 22.5.1

`v22.5.0`: 22.5.0

Compare Source

Node.js 22.5.0

`v22.4.1`: 22.4.1

Compare Source

Node.js 22.4.1

`v22.4.0`: 22.4.0

Compare Source

Node.js 22.4.0

`v22.3.0`: 22.3.0

Compare Source

Node.js 22.3.0

`v22.2.0`: 22.2.0

Compare Source

Node.js 22.2.0

`v22.1.0`: 22.1.0

Compare Source

Node.js 22.1.0

pnpm/pnpm (pnpm)

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

publint/publint (publint)

`v0.3.14`

Compare Source

Patch Changes

Add a new warning when an entrypoint is exported as CJS-only, has a default export, and has the __esModule marker. This setup has different interpretations by bundlers and runtimes, and implicit handling detection that may not be obvious for both package authors and users, hence it is discouraged. (#201)

`v0.3.13`

Compare Source

Patch Changes

Improve message for "main" field with empty value and has missing files (0499518)
Update fallback arrays message for CLI output (37b9dd5)

microsoft/TypeScript (typescript)

`v5.9.3`

Compare Source

`v5.9.2`

Compare Source

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.

renovate bot added the dependencies Pull requests that update a dependency file label Aug 4, 2025

renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 08ea5ed to aa31a0e Compare August 10, 2025 12:36

renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 2f5eb5a to 81853a7 Compare August 19, 2025 17:36

renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from c980e05 to 415b641 Compare August 31, 2025 09:52

renovate bot force-pushed the renovate/all-minor-patch branch from 415b641 to 084a3c8 Compare September 6, 2025 15:42

renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 71c053c to e45ca5b Compare September 18, 2025 10:25

renovate bot changed the title ~~chore(deps): update all non-major dependencies~~ fix(deps): update all non-major dependencies Sep 18, 2025

renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 73d0be2 to c580942 Compare September 25, 2025 01:02

renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from e68b825 to ee0e654 Compare October 6, 2025 08:46

fix(deps): update all non-major dependencies

f21bcec

renovate bot force-pushed the renovate/all-minor-patch branch from ee0e654 to f21bcec Compare October 6, 2025 14:32

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

fix(deps): update all non-major dependencies #77

fix(deps): update all non-major dependencies #77

Uh oh!

renovate bot commented Aug 4, 2025 •

edited

Loading

Uh oh!

Uh oh!

Uh oh!

fix(deps): update all non-major dependencies #77

Are you sure you want to change the base?

fix(deps): update all non-major dependencies #77

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

Bug Fixes

Features

v22.20.0: 22.20.0

v22.19.0: 22.19.0

v22.18.0: 22.18.0

v22.17.1: 22.17.1

v22.17.0: 22.17.0

v22.16.0: 22.16.0

v22.15.1: 22.15.1

v22.15.0: 22.15.0

v22.14.0: 22.14.0

v22.13.1: 22.13.1

v22.13.0: 22.13.0

v22.12.0: 22.12.0

v22.11.0: 22.11.0

v22.10.0: 22.10.0

v22.9.0: 22.9.0

v22.8.0: 22.8.0

v22.7.0: 22.7.0

v22.6.0: 22.6.0

v22.5.1: 22.5.1

v22.5.0: 22.5.0

v22.4.1: 22.4.1

v22.4.0: 22.4.0

v22.3.0: 22.3.0

v22.2.0: 22.2.0

v22.1.0: 22.1.0

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

Patch Changes

Patch Changes

Configuration

Uh oh!

Uh oh!

renovate bot commented Aug 4, 2025 •

edited

Loading

`v22.20.0`: 22.20.0

`v22.19.0`: 22.19.0

`v22.18.0`: 22.18.0

`v22.17.1`: 22.17.1

`v22.17.0`: 22.17.0

`v22.16.0`: 22.16.0

`v22.15.1`: 22.15.1

`v22.15.0`: 22.15.0

`v22.14.0`: 22.14.0

`v22.13.1`: 22.13.1

`v22.13.0`: 22.13.0

`v22.12.0`: 22.12.0

`v22.11.0`: 22.11.0

`v22.10.0`: 22.10.0

`v22.9.0`: 22.9.0

`v22.8.0`: 22.8.0

`v22.7.0`: 22.7.0

`v22.6.0`: 22.6.0

`v22.5.1`: 22.5.1

`v22.5.0`: 22.5.0

`v22.4.1`: 22.4.1

`v22.4.0`: 22.4.0

`v22.3.0`: 22.3.0

`v22.2.0`: 22.2.0

`v22.1.0`: 22.1.0