raineorshine/npm-check-updates
### [`v15.0.2`](https://togithub.com/raineorshine/npm-check-updates/compare/v15.0.1...v15.0.2)
[Compare Source](https://togithub.com/raineorshine/npm-check-updates/compare/v15.0.1...v15.0.2)
### [`v15.0.1`](https://togithub.com/raineorshine/npm-check-updates/compare/v15.0.0...v15.0.1)
[Compare Source](https://togithub.com/raineorshine/npm-check-updates/compare/v15.0.0...v15.0.1)
### [`v15.0.0`](https://togithub.com/raineorshine/npm-check-updates/blob/HEAD/CHANGELOG.md#1500---2022-06-30)
[Compare Source](https://togithub.com/raineorshine/npm-check-updates/compare/v14.1.1...v15.0.0)
##### Breaking
- node >= 14.14 is now required ([#1145](https://togithub.com/raineorshine/npm-check-updates/issues/1145))
- Needed to upgrade `update-notifier` with has a moderate severity vulnerability
- yarn autodetect has been improved ([#1148](https://togithub.com/raineorshine/npm-check-updates/issues/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
### [`v14.1.1`](https://togithub.com/raineorshine/npm-check-updates/compare/v14.1.0...v14.1.1)
[Compare Source](https://togithub.com/raineorshine/npm-check-updates/compare/v14.1.0...v14.1.1)
### [`v14.1.0`](https://togithub.com/raineorshine/npm-check-updates/releases/tag/v14.1.0)
[Compare Source](https://togithub.com/raineorshine/npm-check-updates/compare/v14.0.2...v14.1.0)
#### 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](https://togithub.com/dylang/npm-check#-u---update).
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](https://togithub.com/agrouse) who did a fine job on the PR.
Example:
```sh
$ ncu --packageManager staticRegistry --registry ./my-registry.json
```
my-registry.json:
```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:
```sh
$ 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`](https://togithub.com/raineorshine/npm-check-updates/compare/v14.0.1...v14.0.2)
[Compare Source](https://togithub.com/raineorshine/npm-check-updates/compare/v14.0.1...v14.0.2)
### [`v14.0.1`](https://togithub.com/raineorshine/npm-check-updates/compare/v14.0.0...v14.0.1)
[Compare Source](https://togithub.com/raineorshine/npm-check-updates/compare/v14.0.0...v14.0.1)
### [`v14.0.0`](https://togithub.com/raineorshine/npm-check-updates/blob/HEAD/CHANGELOG.md#1400---2022-06-16)
[Compare Source](https://togithub.com/raineorshine/npm-check-updates/compare/v13.1.5...v14.0.0)
##### Breaking
Prerelease versions are now "upgraded" to versions with a different [preid](https://docs.npmjs.com/cli/v8/commands/npm-version#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](https://togithub.com/raineorshine/npm-check-updates/issues/new). 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](https://togithub.com/IMalyugin).
### [`v13.1.5`](https://togithub.com/raineorshine/npm-check-updates/compare/v13.1.4...v13.1.5)
[Compare Source](https://togithub.com/raineorshine/npm-check-updates/compare/v13.1.4...v13.1.5)
### [`v13.1.4`](https://togithub.com/raineorshine/npm-check-updates/compare/v13.1.3...v13.1.4)
[Compare Source](https://togithub.com/raineorshine/npm-check-updates/compare/v13.1.3...v13.1.4)
### [`v13.1.3`](https://togithub.com/raineorshine/npm-check-updates/compare/v13.1.2...v13.1.3)
[Compare Source](https://togithub.com/raineorshine/npm-check-updates/compare/v13.1.2...v13.1.3)
### [`v13.1.2`](https://togithub.com/raineorshine/npm-check-updates/compare/v13.1.1...v13.1.2)
[Compare Source](https://togithub.com/raineorshine/npm-check-updates/compare/v13.1.1...v13.1.2)
### [`v13.1.1`](https://togithub.com/raineorshine/npm-check-updates/compare/v13.1.0...v13.1.1)
[Compare Source](https://togithub.com/raineorshine/npm-check-updates/compare/v13.1.0...v13.1.1)
### [`v13.1.0`](https://togithub.com/raineorshine/npm-check-updates/compare/v13.0.4...v13.1.0)
[Compare Source](https://togithub.com/raineorshine/npm-check-updates/compare/v13.0.4...v13.1.0)
### [`v13.0.4`](https://togithub.com/raineorshine/npm-check-updates/compare/v13.0.3...v13.0.4)
[Compare Source](https://togithub.com/raineorshine/npm-check-updates/compare/v13.0.3...v13.0.4)
### [`v13.0.3`](https://togithub.com/raineorshine/npm-check-updates/compare/v13.0.2...v13.0.3)
[Compare Source](https://togithub.com/raineorshine/npm-check-updates/compare/v13.0.2...v13.0.3)
### [`v13.0.2`](https://togithub.com/raineorshine/npm-check-updates/compare/v13.0.1...v13.0.2)
[Compare Source](https://togithub.com/raineorshine/npm-check-updates/compare/v13.0.1...v13.0.2)
### [`v13.0.1`](https://togithub.com/raineorshine/npm-check-updates/compare/v13.0.0...v13.0.1)
[Compare Source](https://togithub.com/raineorshine/npm-check-updates/compare/v13.0.0...v13.0.1)
### [`v13.0.0`](https://togithub.com/raineorshine/npm-check-updates/blob/HEAD/CHANGELOG.md#1300---2022-05-15)
[Compare Source](https://togithub.com/raineorshine/npm-check-updates/compare/v12.5.12...v13.0.0)
##### 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`
### [`v12.5.12`](https://togithub.com/raineorshine/npm-check-updates/compare/v12.5.11...v12.5.12)
[Compare Source](https://togithub.com/raineorshine/npm-check-updates/compare/v12.5.11...v12.5.12)
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, click this checkbox.
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
12.5.11->15.0.2Release Notes
raineorshine/npm-check-updates
### [`v15.0.2`](https://togithub.com/raineorshine/npm-check-updates/compare/v15.0.1...v15.0.2) [Compare Source](https://togithub.com/raineorshine/npm-check-updates/compare/v15.0.1...v15.0.2) ### [`v15.0.1`](https://togithub.com/raineorshine/npm-check-updates/compare/v15.0.0...v15.0.1) [Compare Source](https://togithub.com/raineorshine/npm-check-updates/compare/v15.0.0...v15.0.1) ### [`v15.0.0`](https://togithub.com/raineorshine/npm-check-updates/blob/HEAD/CHANGELOG.md#1500---2022-06-30) [Compare Source](https://togithub.com/raineorshine/npm-check-updates/compare/v14.1.1...v15.0.0) ##### Breaking - node >= 14.14 is now required ([#1145](https://togithub.com/raineorshine/npm-check-updates/issues/1145)) - Needed to upgrade `update-notifier` with has a moderate severity vulnerability - yarn autodetect has been improved ([#1148](https://togithub.com/raineorshine/npm-check-updates/issues/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 nowConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.