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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Merged

haoqunjiang merged 1 commit intomainfromrenovate/all-minor-patch

Mar 31, 2025

Merged

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

haoqunjiang merged 1 commit intomainfromrenovate/all-minor-patch

Mar 31, 2025

Conversation

Copy link

Contributor

renovatebot commentedMar 31, 2025•
edited
Loading

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/node (source)	`^22.13.11` ->`^22.13.14`
cypress (source)	`^14.2.0` ->`^14.2.1`
pnpm (source)	`10.6.5` ->`10.7.0`
vitest (source)	`^3.0.9` ->`^3.1.1`

Release Notes

cypress-io/cypress (cypress)

`v14.2.1`

Compare Source

Changelog:https://docs.cypress.io/app/references/changelog#14-2-1

pnpm/pnpm (pnpm)

`v10.7.0`

Compare Source

Minor Changes

pnpm config get andlist also show settings set inpnpm-workspace.yaml files#9316.
It should be possible to use env variables inpnpm-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.patchfoo@^2.0.0:patches/foo-2.patchfoo@2.1.0:patches/foo-3.patch
```
The above configuration would applypatches/foo-3.patch tofoo@2.1.0,patches/foo-2.patch to allfoo versions which satisfy^2.0.0 except2.1.0, andpatches/foo-1.patch to the remainingfoo 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.yamlpatchedDependencies:# the specialized sub range'foo@2.2.0-2.8.0':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 apnpm-workspace.yaml file if no.npmrc file is present in the directory#9316.
Renamepnpm.allowNonAppliedPatches topnpm.allowUnusedPatches. The old name is still supported but it would print a deprecation warning message.
Addpnpm.ignorePatchFailures to manage whether pnpm would ignore patch application failures.
IfignorePatchFailures 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.
IfignorePatchFailures is explicitly set tofalse, pnpm would throw an error when any type of patch fails to apply.
IfignorePatchFailures is explicitly set totrue, pnpm would print a warning when any type of patch fails to apply.