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

renovate · 2025-06-16T02:10:12Z

This PR contains the following updates:

Package	Change	Type	Update
@antfu/eslint-config	`^4.13.2` -> `^4.19.0`	devDependencies	minor
bumpp	`^10.1.1` -> `^10.3.1`	devDependencies	minor
eslint (source)	`^9.28.0` -> `^9.37.0`	devDependencies	minor
lint-staged	`^16.1.0` -> `^16.2.4`	devDependencies	minor
node	`18` -> `18.20.8`	uses-with	minor
pnpm (source)	`10.11.1` -> `10.18.2`	packageManager	minor
simple-git-hooks	`^2.13.0` -> `^2.13.1`	devDependencies	patch
tsx (source)	`^4.19.4` -> `^4.20.6`	devDependencies	minor
typescript (source)	`^5.8.3` -> `^5.9.3`	devDependencies	minor
vitest (source)	`^3.2.1` -> `^3.2.4`	devDependencies	patch

Release Notes

antfu/eslint-config (@antfu/eslint-config)

`v4.19.0`

Compare Source

🚀 Features

Add Next.js support - by @Peek-A-Booo in #731 (8f9b4)
Update deps - by @antfu (58282)

🐞 Bug Fixes

Enhance TypedFlatConfigItem type and improve timeout handling in tests - by @ccpu in #738 (3d486)

View changes on GitHub

`v4.18.0`

Compare Source

🚀 Features

Update deps - by @antfu (ae7dc)

View changes on GitHub

`v4.17.0`

Compare Source

🚀 Features

Support sort jsconfig - by @pacexy in #733 (5dff7)
Update deps - by @antfu (f5f3f)

🐞 Bug Fixes

Update GLOB_SVELTE to include .js/.ts extensions - by @agafonovim in #734 (46ead)

View changes on GitHub

`v4.16.2`

Compare Source

No significant changes

View changes on GitHub

`v4.16.1`

Compare Source

🐞 Bug Fixes

Update eslint-plugin-command - by @antfu (195da)

View changes on GitHub

`v4.16.0`

Compare Source

🚀 Features

Update allow exports for react-router projects - by @yyyanghj and @antfu in #725 (83eec)

View changes on GitHub

`v4.15.0`

Compare Source

🚀 Features

Don't use deprecated option - by @9romise in #719 (4e0f8)
Bring import plugin back - by @9romise in #723 (ad23f)

View changes on GitHub

`v4.14.1`

Compare Source

🐞 Bug Fixes

Cleanup disable usages - by @antfu (f73ad)

View changes on GitHub

`v4.14.0`

Compare Source

🐞 Bug Fixes

Remove eslint-plugin-import-x - by @antfu (db5a3)

View changes on GitHub

`v4.13.3`

Compare Source

No significant changes

View changes on GitHub

antfu-collective/bumpp (bumpp)

`v10.3.1`

Compare Source

No significant changes

View changes on GitHub

`v10.3.0`

Compare Source

🚀 Features

Support --release for release type - by @luoling8192 in #97 (5af7b)

View changes on GitHub

`v10.2.3`

Compare Source

🐞 Bug Fixes

Add missing -a alias support for --all - by @kingyue737 in #93 (7c0bb)

View changes on GitHub

`v10.2.2`

Compare Source

🐞 Bug Fixes

Improve workspace handling in normalizeOptions #90 - by @Vanisper in #91 and #90 (5dc8c)

View changes on GitHub

`v10.2.1`

Compare Source

🐞 Bug Fixes

Respect custom cwd, close #87 - by @pot-code in #89 and #87 (08137)

View changes on GitHub

`v10.2.0`

Compare Source

🚀 Features

Support npm/bun workspace - by @yuzheng14 in #85 (a0901)

View changes on GitHub

eslint/eslint (eslint)

lint-staged/lint-staged (lint-staged)

`v16.2.4`

Compare Source

Patch Changes

#1682 0176038 Thanks @iiroj! - Update dependencies, including [email protected] with bug fixes.
#1671 581a54e Thanks @iiroj! - Speed up execution by only importing the yaml depedency if using YAML configuration files.

`v16.2.3`

Compare Source

Patch Changes

#1669 27cd541 Thanks @iiroj! - When using --fail-on-changes, automatically hidden (partially) unstaged changes are no longer counted to make lint-staged fail.

`v16.2.2`

Compare Source

Patch Changes

#1667 699f95d Thanks @iiroj! - The backup stash will not be dropped when using --fail-on-changes and there are errors. When reverting to original state is disabled (via --no-revert or --fail-on-changes), hidden (partially) unstaged changes are still restored automatically so that it's easier to resolve the situation manually.

Additionally, the example for using the backup stash manually now uses the correct backup hash, if available:

% npx lint-staged --fail-on-changes
✔ Backed up original state in git stash (c18d55a3)
✔ Running tasks for staged files...
✖ Tasks modified files and --fail-on-changes was used!
↓ Cleaning up temporary files...

✖ lint-staged failed because `--fail-on-changes` was used.

Any lost modifications can be restored from a git stash:

  > git stash list --format="%h %s"
  c18d55a3 On main: lint-staged automatic backup
  > git apply --index c18d55a3

`v16.2.1`

Compare Source

Patch Changes

#1664 8277b3b Thanks @iiroj! - The built-in TypeScript types have been updated to more closely match the implementation. Notably, the list of staged files supplied to task functions is readonly string[] and can't be mutated. Thanks @outslept!
```
export default {
---  "*": (files: string[]) => void console.log('staged files', files)
+++  "*": (files: readonly string[]) => void console.log('staged files', files)
}
```
#1654 70b9af3 Thanks @iiroj! - This version has been published from GitHub Actions using Trusted Publishing for npm packages.
#1659 4996817 Thanks @iiroj! - Fix searching configuration files when the working directory is a subdirectory of a git repository, and there are package.json files in the working directory. This situation might happen when running lint-staged for a single package in a monorepo.
#1654 7021f0a Thanks @iiroj! - Return the caret semver range (^) to direct dependencies so that future patch and minor versions are allowed. This enables projects to better maintain and deduplicate their own transitive dependencies while not requiring direct updates to lint-staged. This was changed in 16.2.0 after the vulnerability issues with chalk and debug, which were also removed in the same version.

Given the recent vulnerabilities in the npm ecosystem, it's best to be very careful when updating dependencies.

`v16.2.0`

Compare Source

Minor Changes

#1615 99eb742 Thanks @iiroj! - Added a new option --fail-on-changes to make lint-staged exit with code 1 when tasks modify any files, making the precommit hook fail. This is similar to the git diff --exit-code option. Using this flag also implies the --no-revert flag which means any changes made my tasks will be left in the working tree after failing, so that they can be manually staged and the commit tried again.
#1611 cd05fd3 Thanks @rlorenzo! - Added a new option --continue-on-error so that lint-staged will run all tasks to completion even if some of them fail. By default, lint-staded will exit early on the first failure.
#1637 82fcc07 Thanks @iiroj! - Internal lint-staged errors are now thrown and visible in the console output. Previously they were caught with the process exit code set to 1, but not logged. This happens when, for example, there's a syntax error in the lint-staged configuration file.
#1647 a5ecc06 Thanks @iiroj! - Remove debug as a dependency due to recent malware issue; read more at debug-js/debug#1005. Because of this, the DEBUG environment variable is no longer supported — use the --debug to enable debugging
#1636 8db2717 Thanks @iiroj! - Added a new option --hide-unstaged so that lint-staged will hide all unstaged changes to tracked files before running tasks. The changes will be applied back after running the tasks. Note that the combination of flags --hide-unstaged --no-hide-partially-staged isn't meaningful and behaves the same as just --hide-unstaged.

Thanks to @ItsNickBarry for the idea and initial implementation in #1552.
#1648 7900b3b Thanks @iiroj! - Remove lilconfig to reduce reliance on third-party dependencies. It was used to find possible config files outside of those tracked in Git, including from the parent directories. This behavior has been moved directly into lint-staged and should work about the same.

Patch Changes

#1633 7f9e485 Thanks @dependabot! - Bumps listr2 from 9.0.3 to 9.0.4.
#1626 99d5a9b Thanks @iiroj! - Due to recent phishing attacks, for example [email protected] was released with malware. To avoid lint-staged's users being at risk the direct dependencies are pinned to exact versions, instead of allowing future patch versions with the caret (^) range.
#1588 035bbf2 Thanks @outslept! - Increase performance by listing staged files and searching for configuration concurrently.
#1645 deba3ad Thanks @iiroj! - Remove chalk as a dependency due to recent malware issue; read more at chalk/chalk#656.

If you are having trouble with ANSI color codes when using lint-staged, you can try setting either FORCE_COLOR=true or NO_COLOR=true env variables.

`v16.1.6`

Compare Source

Patch Changes

#1610 e93578e Thanks @iiroj! - Try to improve terminating of subprocess of tasks by using SIGKILL, and only calling pidtree when the the main task process has a known pid.

`v16.1.5`

Compare Source

Patch Changes

#1608 4e3ce22 Thanks @srsatt! - Detect the git repo's top-level directory correctly when in a worktree.

`v16.1.4`

Compare Source

Patch Changes

#1604 90b37b0 Thanks @iiroj! - Add another types field to package.json to make even more sure NPM detects that lint-staged includes built-in TypeScript type definitions.

`v16.1.3`

Compare Source

Patch Changes

#1602 7ea700b Thanks @dword-design! - Add the types field to package.json to make sure NPM detects lint-staged includes built-in TypeScript type definitions.

`v16.1.2`

Compare Source

Patch Changes

#1570 a7c0c88 Thanks @ItsNickBarry! - When using --diff-filter with the D option to include deleted staged files, lint-staged no longer tries to stage the deleted files, unless they're no longer deleted. Previously this caused an error from git add like fatal: pathspec 'deleted-file' did not match any files.
38f942e Thanks @iiroj! - Removed an extraneous log entry that printed shouldHidePArtiallyStagedFiles to console output.

`v16.1.1`

Compare Source

Patch Changes

#1565 3686977 Thanks @iiroj! - Lint-staged now explicitly warns about potential data loss when using --no-stash.
#1571 02299a9 Thanks @iiroj! - Function tasks (introduced in v16.0.0) only received the staged files matching the conpmnfigured glob, instead of all staged files.
#1563 bc61c74 Thanks @iiroj! - This version fixes incorrect behavior where unstaged changes were committed when using the --no-stash option. This happened because --no-stash implied --no-hide-partially-staged, meaning unstaged changes to files which also had other staged changes were added to the commit by lint-staged; this is no longer the case.

The previous (incorrect) behavior can still be achieved by using both options --no-stash --no-hide-partially-staged at the same time.

actions/node-versions (node)

`v18.20.8`: 18.20.8

Compare Source

Node.js 18.20.8

`v18.20.7`: 18.20.7

Compare Source

Node.js 18.20.7

`v18.20.6`: 18.20.6

Compare Source

Node.js 18.20.6

`v18.20.5`: 18.20.5

Compare Source

Node.js 18.20.5

`v18.20.4`: 18.20.4

Compare Source

Node.js 18.20.4

`v18.20.3`: 18.20.3

Compare Source

Node.js 18.20.3

`v18.20.2`: 18.20.2

Compare Source

Node.js 18.20.2

`v18.20.1`: 18.20.1

Compare Source

Node.js 18.20.1

`v18.20.0`: 18.20.0

Compare Source

Node.js 18.20.0

`v18.19.1`: 18.19.1

Compare Source

Node.js 18.19.1

`v18.19.0`: 18.19.0

Compare Source

Node.js 18.19.0

`v18.18.2`: 18.18.2

Compare Source

Node.js 18.18.2

`v18.18.1`: 18.18.1

Compare Source

Node.js 18.18.1

`v18.18.0`: 18.18.0

Compare Source

Node.js 18.18.0

`v18.17.1`: 18.17.1

Compare Source

Node.js 18.17.1

`v18.17.0`: 18.17.0

Compare Source

Node.js 18.17.0

`v18.16.1`: 18.16.1

Compare Source

Node.js 18.16.1

`v18.16.0`: 18.16.0

Compare Source

Node.js 18.16.0

`v18.15.0`: 18.15.0

Compare Source

Node.js 18.15.0

`v18.14.2`: 18.14.2

Compare Source

Node.js 18.14.2

`v18.14.1`: 18.14.1

Compare Source

Node.js 18.14.1

`v18.14.0`: 18.14.0

Compare Source

Node.js 18.14.0

`v18.13.0`: 18.13.0

Compare Source

Node.js 18.13.0

`v18.12.1`: 18.12.1

Compare Source

Node.js 18.12.1

`v18.12.0`: 18.12.0

Compare Source

Node.js 18.12.0

`v18.11.0`: 18.11.0

Compare Source

Node.js 18.11.0

`v18.10.0`: 18.10.0

Compare Source

Node.js 18.10.0

`v18.9.1`: 18.9.1

Compare Source

Node.js 18.9.1

`v18.9.0`: 18.9.0

Compare Source

Node.js 18.9.0

`v18.8.0`: 18.8.0

Compare Source

Node.js 18.8.0

`v18.7.0`: 18.7.0

Compare Source

Node.js 18.7.0

`v18.6.0`: 18.6.0

Compare Source

Node.js 18.6.0

`v18.5.0`: 18.5.0

Compare Source

Node.js 18.5.0

`v18.4.0`: 18.4.0

Compare Source

Node.js 18.4.0

`v18.3.0`: 18.3.0

Compare Source

Node.js 18.3.0

`v18.2.0`: 18.2.0

Compare Source

Node.js 18.2.0

`v18.1.0`: 18.1.0

Compare Source

Node.js 18.1.0

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

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 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 bot added the dependencies label Jun 16, 2025

renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 1570a63 to e81297e Compare June 23, 2025 03:31

renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 467d034 to 5f604a9 Compare June 27, 2025 23:37

renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 35682fe to d84167f Compare July 2, 2025 02:43

renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from f318a4e to c60f04d Compare July 15, 2025 03:41

renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 8fb8a3a to 2a7a221 Compare July 29, 2025 06:35

renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from ccc2733 to ceedbcc Compare August 3, 2025 17:53

renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from a5d8596 to 7f2cbdc Compare August 12, 2025 15:26

renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 633550f to db052f8 Compare August 24, 2025 05:13

renovate bot force-pushed the renovate/all-minor-patch branch from db052f8 to d541653 Compare August 31, 2025 10:11

renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 5cf3dca to 606058e Compare September 5, 2025 17:09

renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from a2cfd7a to f493601 Compare September 19, 2025 17:41

renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from 5c1ec1c to 39b587c Compare September 28, 2025 13:32

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

renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 012a59b to 7c58519 Compare October 10, 2025 01:34

chore(deps): update all non-major dependencies

ba0986f

renovate bot force-pushed the renovate/all-minor-patch branch from 7c58519 to ba0986f Compare October 11, 2025 09:15

alexzhang1030 merged commit f7765e4 into main Oct 12, 2025
3 checks passed

alexzhang1030 deleted the renovate/all-minor-patch branch October 12, 2025 11:22

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

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

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

Uh oh!

renovate bot commented Jun 16, 2025 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

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

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

Uh oh!

Conversation

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

Uh oh!

Release Notes

🚀 Features

🐞 Bug Fixes

🚀 Features

🚀 Features

🐞 Bug Fixes

🐞 Bug Fixes

🚀 Features

🚀 Features

🐞 Bug Fixes

🐞 Bug Fixes

🚀 Features

🐞 Bug Fixes

🐞 Bug Fixes

🐞 Bug Fixes

🚀 Features

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

v18.20.8: 18.20.8

v18.20.7: 18.20.7

v18.20.6: 18.20.6

v18.20.5: 18.20.5

v18.20.4: 18.20.4

v18.20.3: 18.20.3

v18.20.2: 18.20.2

v18.20.1: 18.20.1

v18.20.0: 18.20.0

v18.19.1: 18.19.1

v18.19.0: 18.19.0

v18.18.2: 18.18.2

v18.18.1: 18.18.1

v18.18.0: 18.18.0

v18.17.1: 18.17.1

v18.17.0: 18.17.0

v18.16.1: 18.16.1

v18.16.0: 18.16.0

v18.15.0: 18.15.0

v18.14.2: 18.14.2

v18.14.1: 18.14.1

v18.14.0: 18.14.0

v18.13.0: 18.13.0

v18.12.1: 18.12.1

v18.12.0: 18.12.0

v18.11.0: 18.11.0

v18.10.0: 18.10.0

v18.9.1: 18.9.1

v18.9.0: 18.9.0

v18.8.0: 18.8.0

v18.7.0: 18.7.0

v18.6.0: 18.6.0

v18.5.0: 18.5.0

v18.4.0: 18.4.0

v18.3.0: 18.3.0

v18.2.0: 18.2.0

v18.1.0: 18.1.0

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

renovate bot commented Jun 16, 2025 •

edited

Loading

`v18.20.8`: 18.20.8

`v18.20.7`: 18.20.7

`v18.20.6`: 18.20.6

`v18.20.5`: 18.20.5

`v18.20.4`: 18.20.4

`v18.20.3`: 18.20.3

`v18.20.2`: 18.20.2

`v18.20.1`: 18.20.1

`v18.20.0`: 18.20.0

`v18.19.1`: 18.19.1

`v18.19.0`: 18.19.0

`v18.18.2`: 18.18.2

`v18.18.1`: 18.18.1

`v18.18.0`: 18.18.0

`v18.17.1`: 18.17.1

`v18.17.0`: 18.17.0

`v18.16.1`: 18.16.1

`v18.16.0`: 18.16.0

`v18.15.0`: 18.15.0

`v18.14.2`: 18.14.2

`v18.14.1`: 18.14.1

`v18.14.0`: 18.14.0

`v18.13.0`: 18.13.0

`v18.12.1`: 18.12.1

`v18.12.0`: 18.12.0

`v18.11.0`: 18.11.0

`v18.10.0`: 18.10.0

`v18.9.1`: 18.9.1

`v18.9.0`: 18.9.0

`v18.8.0`: 18.8.0

`v18.7.0`: 18.7.0

`v18.6.0`: 18.6.0

`v18.5.0`: 18.5.0

`v18.4.0`: 18.4.0

`v18.3.0`: 18.3.0

`v18.2.0`: 18.2.0

`v18.1.0`: 18.1.0