chore(deps): update dependency npm-check-updates to v15 #239

renovate · 2022-07-01T17:45:27Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
npm-check-updates	`12.5.4` -> `15.0.3`

Release Notes

raineorshine/npm-check-updates

Breaking

node >= 14.14 is now required (#1145)
- Needed to upgrade update-notifier with has a moderate severity vulnerability
yarn autodetect has been improved (#1148)
- This is a patch, though technically it is breaking. In the obscure case where --packageManager is not given, there is no package-lock.json in the current folder, and there is a yarn.lock in an ancestor directory, npm-check-updates will now use yarn.
- More practically, if you needed to specify --packageManager yarn explicitly before, you may not have to now

raineorshine/npm-check-updates@v14.1.1...v15.0.0

`v14.1.1`

Compare Source

`v14.1.0`

Compare Source

Features

Group

You can now group upgrades by risk level using --format group:

##### Interactive Mode

Interactive mode was completely rewritten for a better user experience.

Inspired by npm-check.

Combine with --format group for a truly luxe experience:

##### Static Registry

A new option --packageManager staticRegistry allows upgrades to be recommended from a static JSON file. This can be used to power custom versioning infrastructure that is completely independent from the npm registry.

Thanks to agrouse who did a fine job on the PR.

Example:

$ ncu --packageManager staticRegistry --registry ./my-registry.json

my-registry.json:

{
  "prettier": "2.7.0",
  "typescript": "4.7.0"
}

The latest versions of prettier and typescript are set in the registry file. When ncu is run, it will recommend upgrades from the static registry file without touching the npm registry:

$ ncu --packageManager staticRegistry --registry ./my-registry.json
Checking /Users/raine/projects/ncu-issues/14.1.0/package.json
[====================] 2/2 100%

 prettier    ^2.0.1  →  ^2.7.0
 typescript  ^3.4.0  →  ^4.7.0

Run ncu -u to upgrade package.json

`v14.0.2`

Compare Source

`v14.0.1`

Compare Source

`v14.0.0`

Compare Source

Breaking

Prerelease versions are now "upgraded" to versions with a different preid.

For example, if you have a dependency at 1.3.3-next.1 and the version fetched by ncu is 1.2.3-dev.2, ncu will suggest an "upgrade" to 1.2.3-dev.2. This is because prerelease versions with different preids are incomparable. Since they are incomparable, ncu now assumes the fetched version is desired.

Since this change affects only prereleases, there is no impact on default ncu usage that fetches the latest version. With --pre or --target newest or --target greatest, this change could affect which version is suggested if versions with different preids are published. The change was made to support the new --target @[tag] feature.

If you have a use case where this change is not what is desired, please report an issue. The intention is for zero disruption to current usage.

Features

You can now upgrade to a specific tag, e.g. --target @next. Thanks to IMalyugin.

raineorshine/npm-check-updates@v13.1.5...v14.0.0

`v13.1.5`

Compare Source

`v13.1.4`

Compare Source

`v13.1.3`

Compare Source

`v13.1.2`

Compare Source

`v13.1.1`

Compare Source

`v13.1.0`

Compare Source

`v13.0.4`

Compare Source

`v13.0.3`

Compare Source

`v13.0.2`

Compare Source

`v13.0.1`

Compare Source

`v13.0.0`

Compare Source

Breaking

node >= 14 is now required
Several options which have long been deprecated have been removed:
- --greatest - Instead use --target greatest
- --newest - Instead use --target newest
- --ownerChanged - Instead use --format ownerChanged
- --semverLevel - Renamed to --target