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

renovate · 2024-11-18T02:27:41Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@actions/cache (source)	`^4.0.1` -> `^4.0.3`
@actions/core (source)	`^1.10.0` -> `^1.11.1`
@antfu/ni	`^0.20.0` -> `^0.23.2`
@types/node (source)	`^18.15.5` -> `^18.19.111`
@types/semver (source)	`^7.3.13` -> `^7.7.0`
execa	`^7.1.1` -> `^7.2.0`
node-fetch	`^3.3.1` -> `^3.3.2`
pnpm (source)	`10.0.0` -> `10.12.1`
semver	`^7.3.8` -> `^7.7.2`
simple-git-hooks	`^2.8.1` -> `^2.13.0`
tsx (source)	`^4.19.2` -> `^4.20.1`

Release Notes

actions/toolkit (@actions/cache)

`v4.0.3`

Added masking for Shared Access Signature (SAS) cache entry URLs #1982
Improved debugging by logging both the cache version alongside the keys requested when a cache restore fails #1994

`v4.0.2`

Wrap create failures in ReserveCacheError #1966

antfu-collective/ni (@antfu/ni)

`v0.23.2`

Compare Source

No significant changes

View changes on GitHub

View changes on GitHub

`v0.23.0`

Compare Source

🚨 Breaking Changes

parseNi etc. now return ResolvedCommand object instead of string, migrate to tinyexec - by @userquin, Ben McCann and @antfu in https://github.com/antfu-collective/ni/issues/231 (3d323)

View changes on GitHub

`v0.22.4`

Compare Source

🐞 Bug Fixes

Revert to v0.22.1 - by @antfu (69f95)

View changes on GitHub

`v0.22.3`

Compare Source

🐞 Bug Fixes

Move back to @jsdevtools/ez-spawn, fix #224 - by @antfu in https://github.com/antfu-collective/ni/issues/224 (af1b1)

View changes on GitHub

`v0.22.2`

Compare Source

No significant changes

View changes on GitHub

`v0.22.1`

Compare Source

🚀 Features

Support environment variables for ni config - by @ghostdevv and @antfu in https://github.com/antfu-collective/ni/issues/216 (c408e)

🐞 Bug Fixes

bun x instead of bunx - by @MAttila42 in https://github.com/antfu-collective/ni/issues/219 (13282)

View changes on GitHub

`v0.22.0`

Compare Source

🚀 Features

Interactive package management - by @gearonix and @antfu in https://github.com/antfu-collective/ni/issues/202 (7787a)

🐞 Bug Fixes

Packager detect tests are not running - by @zhyupe in https://github.com/antfu-collective/ni/issues/199 (9fb5b)
bun: Incorrect bun frozen-lockfile command - by @mrsekut in https://github.com/antfu-collective/ni/issues/214 (e0816)

View changes on GitHub

`v0.21.12`

Compare Source

🐞 Bug Fixes

Properly detect and install yarn@>1 and pnpm@<7 - by @auvred in https://github.com/antfu/ni/issues/190 (2fbce)

View changes on GitHub

`v0.21.11`

Compare Source

🐞 Bug Fixes

Correctly override local agent - by @so1ve in https://github.com/antfu/ni/issues/188 (76059)

View changes on GitHub

`v0.21.10`

Compare Source

🐞 Bug Fixes

.nirc may not exist - by @a1mersnow and @antfu in https://github.com/antfu/ni/issues/186 (88123)

View changes on GitHub

`v0.21.9`

Compare Source

🚀 Features

Support detect the range version of packageManager - by @Dunqing in https://github.com/antfu/ni/issues/179 (b616e)

🐞 Bug Fixes

-v flag not working for yarn@berry - by @Dimava in https://github.com/antfu/ni/issues/175 (9e3c9)

View changes on GitHub

`v0.21.8`

Compare Source

🚀 Features

programmatic: Allow passing custom args - by @antfu (7a165)

View changes on GitHub

`v0.21.7`

Compare Source

🚀 Features

Add flag to show agent versions - by @Dimava and @antfu in https://github.com/antfu/ni/issues/169 (3566e)

🐞 Bug Fixes

Regex typo - by @Steven4857 and 洪伟 in https://github.com/antfu/ni/issues/171 (b351d)

View changes on GitHub

`v0.21.6`

Compare Source

🚀 Features

Add nu support for bun - by @jatindotdev in https://github.com/antfu/ni/issues/167 (63b6a)

View changes on GitHub

`v0.21.5`

Compare Source

🚀 Features

Expose getCliCommand function - by @ghengeveld and @antfu in https://github.com/antfu/ni/issues/164 (17d8e)

🐞 Bug Fixes

If there are spaces in args, then wrap them with quotes - by @FrankFang and @antfu in https://github.com/antfu/ni/issues/160 (3ae42)

View changes on GitHub

`v0.21.4`

Compare Source

🚀 Features

Silent programmatic usage - by @millsp in https://github.com/antfu/ni/issues/151 (3f86b)

View changes on GitHub

`v0.21.3`

Compare Source

No significant changes

View changes on GitHub

`v0.21.2`

Compare Source

🐞 Bug Fixes

Install specific version of agent - by @sxzz in https://github.com/antfu/ni/issues/149 (0e196)

View changes on GitHub

`v0.21.1`

Compare Source

`v0.21.0`

Compare Source

🚨 Breaking Changes

Rename nix to nlx - by @antfu (ee46d)

🚀 Features

Add error message for unsupported commands/package managers - by @Zeko369 and @antfu in https://github.com/antfu/ni/issues/129 (1a7e9)

🐞 Bug Fixes

Windows cmd detection - by @vaaski in https://github.com/antfu/ni/issues/136 (d28d4)

🏎 Performance

Optimize code performance - by @kirklin in https://github.com/antfu/ni/issues/148 (4cd9e)

View changes on GitHub

pnpm/pnpm (pnpm)

`v10.12.1`

Minor Changes

Experimental. Added support for global virtual stores. When enabled, node_modules contains only symlinks to a central virtual store, rather to node_modules/.pnpm. By default, this central store is located at <store-path>/links (you can find the store path by running pnpm store path).

In the central virtual store, each package is hard linked into a directory whose name is the hash of its dependency graph. This allows multiple projects on the system to symlink shared dependencies from this central location, significantly improving installation speed when a warm cache is available.

This is conceptually similar to how NixOS manages packages, using dependency graph hashes to create isolated and reusable package directories.

To enable the global virtual store, set enableGlobalVirtualStore: true in your root pnpm-workspace.yaml, or globally via:
```
pnpm config -g set enable-global-virtual-store true
```
NOTE: In CI environments, where caches are typically cold, this setting may slow down installation. pnpm automatically disables the global virtual store when running in CI.

Related PR: #8190

The pnpm update command now supports updating catalog: protocol dependencies and writes new specifiers to pnpm-workspace.yaml.
Added two new CLI options (--save-catalog and --save-catalog-name=<name>) to pnpm add to save new dependencies as catalog entries. catalog: or catalog:<name> will be added to package.json and the package specifier will be added to the catalogs or catalog[<name>] object in pnpm-workspace.yaml #9425.
Semi-breaking. The keys used for side-effects caches have changed. If you have a side-effects cache generated by a previous version of pnpm, the new version will not use it and will create a new cache instead #9605.
Added a new setting called ci for explicitly telling pnpm if the current environment is a CI or not.

Patch Changes

Sort versions printed by pnpm patch using semantic versioning rules.
Improve the way the error message displays mismatched specifiers. Show differences instead of 2 whole objects #9598.
Revert #9574 to fix a regression #9596.

`v10.11.1`

Compare Source

Patch Changes

Fix an issue in which pnpm deploy --legacy creates unexpected directories when the root package.json has a workspace package as a peer dependency #9550.
Dependencies specified via a URL that redirects will only be locked to the target if it is immutable, fixing a regression when installing from GitHub releases. (#9531)
Installation should not exit with an error if strictPeerDependencies is true but all issues are ignored by peerDependencyRules #9505.
Use pnpm_config_ env variables instead of npm_config_ #9571.
Fix a regression (in v10.9.0) causing the --lockfile-only flag on pnpm update to produce a different pnpm-lock.yaml than an update without the flag.
Let pnpm deploy work in repos with overrides when inject-workspace-packages=true #9283.
Fixed the problem of path loss caused by parsing URL address. Fixes a regression shipped in pnpm v10.11 via #9502.
pnpm -r --silent run should not print out section #9563.

`v10.11.0`

Compare Source

Minor Changes

A new setting added for pnpm init to create a package.json with type=module, when init-type is module. Works as a flag for the init command too #9463.
Added support for Nushell to pnpm setup #6476.
Added two new flags to the pnpm audit command, --ignore and --ignore-unfixable #8474.

Ignore all vulnerabilities that have no solution:
```
> pnpm audit --ignore-unfixable
```
Provide a list of CVE's to ignore those specifically, even if they have a resolution.
```
> pnpm audit --ignore=CVE-2021-1234 --ignore=CVE-2021-5678
```
Added support for recursively running pack in every project of a workspace #4351.

Now you can run pnpm -r pack to pack all packages in the workspace.

Patch Changes

pnpm version management should work, when dangerouslyAllowAllBuilds is set to true #9472.
pnpm link should work from inside a workspace #9506.
Set the default workspaceConcurrency to Math.min(os.availableParallelism(), 4) #9493.
Installation should not exit with an error if strictPeerDependencies is true but all issues are ignored by peerDependencyRules #9505.
Read updateConfig from pnpm-workspace.yaml #9500.
Add support for recursive pack
Remove url.parse usage to fix warning on Node.js 24 #9492.
pnpm run should be able to run commands from the workspace root, if ignoreScripts is set tot true #4858.

`v10.10.0`

Compare Source

Minor Changes

Allow loading the preResolution, importPackage, and fetchers hooks from local pnpmfile.

Patch Changes

Fix cd command, when shellEmulator is true #7838.
Sort keys in pnpm-workspace.yaml #9453.
Pass the npm_package_json environment variable to the executed scripts #9452.
Fixed a mistake in the description of the --reporter=silent option.

`v10.9.0`

Compare Source

Minor Changes

Added support for installing JSR packages. You can now install JSR packages using the following syntax:
```
pnpm add jsr:<pkg_name>
```
or with a version range:
```
pnpm add jsr:<pkg_name>@&#8203;<range>
```
For example, running:
```
pnpm add jsr:@&#8203;foo/bar
```
will add the following entry to your package.json:
```
{
  "dependencies": {
    "@&#8203;foo/bar": "jsr:^0.1.2"
  }
}
```
When publishing, this entry will be transformed into a format compatible with npm, older versions of Yarn, and previous pnpm versions:
```
{
  "dependencies": {
    "@&#8203;foo/bar": "npm:@&#8203;jsr/foo__bar@^0.1.2"
  }
}
```
Related issue: #8941.

Note: The @jsr scope defaults to https://npm.jsr.io/ if the @jsr:registry setting is not defined.
Added a new setting, dangerouslyAllowAllBuilds, for automatically running any scripts of dependencies without the need to approve any builds. It was already possible to allow all builds by adding this to pnpm-workspace.yaml:
```
neverBuiltDependencies: []
```
dangerouslyAllowAllBuilds has the same effect but also allows to be set globally via:
```
pnpm config set dangerouslyAllowAllBuilds true
```
It can also be set when running a command:
```
pnpm install --dangerously-allow-all-builds
```

Patch Changes

Fix a false negative in verifyDepsBeforeRun when nodeLinker is hoisted and there is a workspace package without dependencies and node_modules directory #9424.
Explicitly drop verifyDepsBeforeRun support for nodeLinker: pnp. Combining verifyDepsBeforeRun and nodeLinker: pnp will now print a warning.

`v10.8.1`

Compare Source

Patch Changes

Removed bright white highlighting, which didn't look good on some light themes #9389.
If there is no pnpm related configuration in package.json, onlyBuiltDependencies will be written to pnpm-workspace.yaml file #9404.

`v10.8.0`

Compare Source

Minor Changes

Experimental. A new hook is supported for updating configuration settings. The hook can be provided via .pnpmfile.cjs. For example:

module.exports = {
  hooks: {
    updateConfig: (config) => ({
      ...config,
      nodeLinker: "hoisted",
    }),
  },
};

Now you can use the pnpm add command with the --config flag to install new configurational dependencies #9377.

Patch Changes

Do not hang indefinitely, when there is a glob that starts with !/ in pnpm-workspace.yaml. This fixes a regression introduced by #9169.
pnpm audit --fix should update the overrides in pnpm-workspace.yaml.
pnpm link should update overrides in pnpm-workspace.yaml, not in package.json #9365.

`v10.7.1`: pnpm 10.7.1

Compare Source

Patch Changes

pnpm config set should convert the settings to their correct type before adding them to pnpm-workspace.yaml #9355.
pnpm config get should read auth related settings via npm CLI #9345.
Replace leading ~/ in a path in .npmrc with the home directory #9217.

Platinum Sponsors

Gold Sponsors

`v10.7.0`

Compare Source

Minor Changes

pnpm config get and list also show settings set in pnpm-workspace.yaml files #9316.
It should be possible to use env variables in pnpm-workspace.yaml setting names and value.
Add an ability to patch dependencies by version ranges. Exact versions override version ranges, which in turn override name-only patches. Version range * is the same as name-only, except that patch application failure will not be ignored.

For example:
```
patchedDependencies:
  foo: patches/foo-1.patch
  foo@^2.0.0: patches/foo-2.patch
  [email protected]: patches/foo-3.patch
```
The above configuration would apply patches/foo-3.patch to [email protected], patches/foo-2.patch to all foo versions which satisfy ^2.0.0 except 2.1.0, and patches/foo-1.patch to the remaining foo versions.
[!WARNING]
The version ranges should not overlap. If you want to specialize a sub range, make sure to exclude it from the other keys. For example:
```
# pnpm-workspace.yaml
patchedDependencies:
  # the specialized sub range
  '[email protected]': patches/foo.2.2.0-2.8.0.patch
  # the more general patch, excluding the sub range above
  'foo@>=2.0.0 <2.2.0 || >2.8.0': 'patches/foo.gte2.patch
```
In most cases, however, it's sufficient to just define an exact version to override the range.
pnpm config set --location=project saves the setting to a pnpm-workspace.yaml file if no .npmrc file is present in the directory #9316.
Rename pnpm.allowNonAppliedPatches to pnpm.allowUnusedPatches. The old name is still supported but it would print a deprecation warning message.
Add pnpm.ignorePatchFailures to manage whether pnpm would ignore patch application failures.

If ignorePatchFailures is not set, pnpm would throw an error when patches with exact versions or version ranges fail to apply, and it would ignore failures from name-only patches.

If ignorePatchFailures is explicitly set to false, pnpm would throw an error when any type of patch fails to apply.

If ignorePatchFailures is explicitly set to true, pnpm would print a warning when any type of patch fails to apply.

Patch Changes

Remove dependency paths from audit output to prevent out-of-memory errors #9280.

`v10.6.5`

Compare Source

Patch Changes

Remove warnings after having explicitly approved no builds #9296.
When installing different dependency packages, should retain the ignoredBuilds field in the .modules.yaml file #9240.
Fix usages of the catalog: protocol in injected local workspace packages. This previously errored with ERR_PNPM_SPEC_NOT_SUPPORTED_BY_ANY_RESOLVER. #8715
Setting workspace-concurrency to less than or equal to 0 should work #9297.

`v10.6.4`

Compare Source

Patch Changes

Fix pnpm dlx with --allow-build flag #9263.
Invalid Node.js version in use-node-version should not cause pnpm itself to break #9276.
The max amount of workers running for linking packages from the store has been reduced to 4 to achieve optimal results #9286. The workers are performing many file system operations, so increasing the number of CPUs doesn't help performance after some point.

`v10.6.3`

Compare Source

Patch Changes

pnpm install --prod=false should not crash, when executed in a project with a pnpm-workspace.yaml file #9233. This fixes regression introduced via #9211.
Add the missing node-options config to recursive run #9180.
Removed a branching code path that only executed when dedupe-peer-dependents=false. We believe this internal refactor will not result in behavior changes, but we expect it to make future pnpm versions behave more consistently for projects that override dedupe-peer-dependents to false. There should be less unique bugs from turning off dedupe-peer-dependents.

See details in #9259.

`v10.6.2`

Compare Source

Patch Changes

pnpm self-update should always update the version in the packageManager field of package.json.
Fix running pnpm CLI from pnpm CLI on Windows when the CLI is bundled to an executable #8971.
pnpm patch-commit will now use the same filesystem as the store directory to compare and create patch files.
Don't show info output when --loglevel=error is used.
peerDependencyRules should be set in pnpm-workspace.yaml to take effect.

`v10.6.1`

Compare Source

Patch Changes

The pnpm CLI process should not stay hanging, when --silent reporting is used.
When --loglevel is set to error, don't show installation summary, execution time, and big tarball download progress.
Don't ignore pnpm.patchedDependencies from package.json #9226.
When executing the approve-builds command, if package.json contains onlyBuiltDependencies or ignoredBuiltDependencies, the selected dependency package will continue to be written into package.json.
When a package version cannot be found in the package metadata, print the registry from which the package was fetched.

`v10.6.0`

Compare Source

Minor Changes

pnpm-workspace.yaml can now hold all the settings that .npmrc accepts. The settings should use camelCase #9211.

pnpm-workspace.yaml example:
```
verifyDepsBeforeRun: install
optimisticRepeatInstall: true
publicHoistPattern:
  - "*types*"
  - "!@&#8203;types/react"
```
Projects using a file: dependency on a local tarball file (i.e. .tgz, .tar.gz, .tar) will see a performance improvement during installation. Previously, using a file: dependency on a tarball caused the lockfile resolution step to always run. The lockfile will now be considered up-to-date if the tarball is unchanged.

Patch Changes

pnpm self-update should not leave a directory with a broken pnpm installation if the installation fails.
fast-glob replace with tinyglobby to reduce the size of the pnpm CLI dependencies #9169.
pnpm deploy should not remove fields from the deployed package's package.json file #9215.
pnpm self-update should not read the pnpm settings from the package.json file in the current working directory.
Fix pnpm deploy creating a package.json without the imports and license field #9193.
pnpm update -i should list only packages that have newer versions #9206.
Fix a bug causing entries in the catalogs section of the pnpm-lock.yaml file to be removed when dedupe-peer-dependents=false on a filtered install. #9112

`v10.5.2`

Compare Source

Patch Changes

The pnpm config set command should change the global .npmrc file by default.
This was a regression introduced by #9151 and shipped in pnpm v10.5.0.

`v10.5.1`

Compare Source

Patch Changes

Throw an error message if a pnpm-workspaces.yaml or pnpm-workspaces.yml file is found instead of a pnpm-workspace.yaml #9170.
Fix the update of pnpm-workspace.yaml by the pnpm approve-builds command #9168.
Normalize generated link paths in package.json #9163
Specifying overrides in pnpm-workspace.yaml should work.
pnpm dlx should ignore settings from the package.json file in the current working directory #9178.

`v10.5.0`

Compare Source

Minor Changes

Allow to set the "pnpm" settings from package.json via the pnpm-workspace.yaml file #9121.
Added support for automatically syncing files of injected workspace packages after pnpm run #9081. Use the sync-injected-deps-after-scripts setting to specify which scripts build the workspace package. This tells pnpm when syncing is needed. The setting should be defined in a .npmrc file at the root of the workspace. Example:
```
sync-injected-deps-after-scripts[]=compile
```
The packages field in pnpm-workspace.yaml became optional.

Patch Changes

pnpm link with no parameters should work as if --global is specified #9151.
Allow scope registry CLI option without --config. prefix such as --@scope:registry=https://scope.example.com/npm #9089.
pnpm link <path> should calculate relative path from the root of the workspace directory #9132.
Fix a bug causing catalog snapshots to be removed from the pnpm-lock.yaml file when using --fix-lockfile and --filter. #8639
Fix a bug causing catalog protocol dependencies to not re-resolve on a filtered install #8638.

`v10.4.1`

Compare Source

Patch Changes

Throws an error when the value provided by the --allow-build option overlaps with the pnpm.ignoredBuildDependencies list #9105.
Print pnpm's version after the execution time at the end of the console output.
Print warning about ignored builds of dependencies on repeat install #9106.
Setting init-package-manager should work.

`v10.4.0`

Compare Source

Minor Changes

pnpm approve-builds --global works now for allowing dependencies of globally installed packages to run postinstall scripts.
The pnpm add command now supports a new flag, --allow-build, which allows building the specified dependencies. For instance, if you want to install a package called bundle that has esbuild as a dependency and want to allow esbuild to run postinstall scripts, you can run:
```
pnpm --allow-build=esbuild add bundle
```
This will run esbuild's postinstall script and also add it to the pnpm.onlyBuiltDependencies field of package.json. So, esbuild will always be allowed to run its scripts in the future.

Related PR: #9086.
The pnpm init command adds a packageManager field with the current version of pnpm CLI #9069. To disable this behaviour, set the init-package-manager setting to false.

Patch Changes

pnpm approve-builds should work after two consecutive pnpm install runs #9083.
Fix instruction for updating pnpm with corepack #9101.
The pnpm version specified by packageManager cannot start with v.

`v10.3.0`

Compare Source

Minor Changes

Added a new setting called strict-dep-builds. When enabled, the installation will exit with a non-zero exit code if any dependencies have unreviewed build scripts (aka postinstall scripts) #9071.

Patch Changes

Fix a false negative of verify-deps-before-run after pnpm install --production|--no-optional #9019.
Print the warning about blocked installation scripts at the end of the installation output and make it more prominent.

`v10.2.1`

Compare Source

Patch Changes

Don't read a package from side-effects cache if it isn't allowed to be built #9042.
pnpm approve-builds should work, when executed from a subdirectory of a workspace #9042.
pnpm deploy --legacy should work without injected dependencies.
Add information about how to deploy without "injected dependencies" to the "pnpm deploy" error message.

`v10.2.0`

Compare Source

Minor Changes

Packages executed via pnpm dlx and pnpm create are allowed to be built (run postinstall scripts) by default.

If the packages executed by dlx or create have dependencies that have to be built, they should be listed via the --allow-build flag. For instance, if you want to run a package called bundle that has esbuild in dependencies and want to allow esbuild to run postinstall scripts, run:
```
pnpm --allow-build=esbuild dlx bundle
```
Related PR: #9026.

Patch Changes

Quote args for scripts with shell-quote to support new lines (on POSIX only) #8980.
Fix a bug in which pnpm deploy fails to read the correct projectId when the deploy source is the same as the workspace directory #9001.
Proxy settings should be respected, when resolving Git-hosted dependencies #6530.
Prevent overrides from adding invalid version ranges to peerDependencies by keeping the peerDependencies and overriding them with prod dependencies #8978.
Sort the package names in the "pnpm.onlyBuiltDependencies" list saved by pnpm approve-builds.

`v10.1.0`

Compare Source

Minor Changes

Added a new command for printing the list of dependencies with ignored build scripts: pnpm ignored-builds #8963.
Added a new command for approving dependencies for running scripts during installation: pnpm approve-builds #8963.
Added a

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 · 2025-02-02T10:16:51Z

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

 ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)

Your pnpm version is incompatible with "/tmp/renovate/repos/github/rspack-contrib/rsbuild-ecosystem-ci".

Expected version: 10.0.0
Got: 10.12.1

This is happening because the package's manifest has an engines.pnpm field specified.
To fix this issue, install the required pnpm version globally.

To install the latest version of pnpm, run "pnpm i -g pnpm".
To check your pnpm version, run "pnpm -v".

renovate bot added the dependencies label Nov 18, 2024

renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 8df1e2b to a4aed74 Compare November 23, 2024 11:24

renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from b2534da to 0374365 Compare November 29, 2024 03:01

renovate bot force-pushed the renovate/all-minor-patch branch from 0374365 to d93131a Compare December 11, 2024 16:54

renovate bot force-pushed the renovate/all-minor-patch branch from d93131a to 03446e5 Compare December 22, 2024 08:37

renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 8622a05 to d906770 Compare January 6, 2025 23:44

renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 334ffdf to 59b1346 Compare January 23, 2025 07:19

renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 791bf55 to 88ad81f Compare January 31, 2025 07:40

renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 66c68e5 to 55b0982 Compare February 2, 2025 10:16

renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 822ca28 to 10eed02 Compare February 6, 2025 21:41

renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from fd5d30c to 67e3529 Compare February 17, 2025 02:38

renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 4489acd to 12398ea Compare February 25, 2025 23:14

renovate bot force-pushed the renovate/all-minor-patch branch from 12398ea to db7fbe2 Compare February 26, 2025 15:00

renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 4ae5115 to 12fad8f Compare April 28, 2025 01:53

renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from bf5c79f to 5eaf4e7 Compare May 6, 2025 03:43

renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from e88096c to a557c7d Compare May 12, 2025 19:04

renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from fad505f to 35718a7 Compare May 20, 2025 19:51

renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 936389c to 73a17fe Compare May 27, 2025 20:04

renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from bc07f8e to 1fafd0a Compare June 2, 2025 14:54

renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from c62069b to 20e447c Compare June 11, 2025 03:09

fix(deps): update all non-major dependencies

fdc427e

renovate bot force-pushed the renovate/all-minor-patch branch from 20e447c to fdc427e Compare June 11, 2025 14:36

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

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

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

renovate bot commented Nov 18, 2024 •

edited

Loading

Uh oh!

renovate bot commented Feb 2, 2025 •

edited

Loading

Uh oh!

Uh oh!

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

Are you sure you want to change the base?

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

Conversation

renovate bot commented Nov 18, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

🚀 Features

🐞 Bug Fixes

🚨 Breaking Changes

🐞 Bug Fixes

🐞 Bug Fixes

🚀 Features

🐞 Bug Fixes

🚀 Features

🐞 Bug Fixes

🐞 Bug Fixes

🐞 Bug Fixes

🐞 Bug Fixes

🚀 Features

🐞 Bug Fixes

🚀 Features

🚀 Features

🐞 Bug Fixes

🚀 Features

🚀 Features

🐞 Bug Fixes

🚀 Features

🐞 Bug Fixes

🚨 Breaking Changes

🚀 Features

🐞 Bug Fixes

🏎 Performance

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

v10.7.1: pnpm 10.7.1

Patch Changes

Platinum Sponsors

Gold Sponsors

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Configuration

Uh oh!

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

Uh oh!

⚠️ Artifact update problem

File name: pnpm-lock.yaml

Uh oh!

renovate bot commented Nov 18, 2024 •

edited

Loading

`v10.7.1`: pnpm 10.7.1

renovate bot commented Feb 2, 2025 •

edited

Loading