Update dependency npm-check-updates to v18 #54

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.

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom

Open

renovate wants to merge 1 commit into master from renovate/npm-check-updates-18.x

Contributor

renovate bot commented Apr 21, 2025 •

edited

Loading

This PR contains the following updates:

Package	Change	Age	Confidence
npm-check-updates	`^16.9.0` -> `^18.0.0`

Release Notes

raineorshine/npm-check-updates (npm-check-updates)

`v18.0.2`

`v18.0.1`

`v18.0.0`

Breaking

The only breaking change in v18 is with the -g/--global flag.

npm-check-updates -g will now auto-detect your package manager based on the execution path. Previously, it defaulted to npm.

yarn dlx ncu -g --packageManager yarn → yarn dlx ncu -g
pnpm dlx ncu --global --packageManager pnpm → pnpm dlx ncu -g
bunx ncu -g--packageManager pnpm → bunx ncu -g

If for some reason you were running ncu -g with an alternative package manager and relying on it checking the global npm packages, you will need to now explicitly specify npm:

ncu -g → ncu -g--packageManager npm

Thanks to @LuisFerLCC for the improvement (#1514).

`v17.1.18`

`v17.1.17`

`v17.1.16`

`v17.1.15`

`v17.1.14`

`v17.1.13`

`v17.1.12`

`v17.1.11`

`v17.1.10`

`v17.1.9`

`v17.1.8`

`v17.1.7`

`v17.1.6`

`v17.1.5`

`v17.1.4`

`v17.1.3`

`v17.1.2`

`v17.1.1`

`v17.1.0`

`v17.0.6`

`v17.0.5`

`v17.0.4`

`v17.0.3`

`v17.0.2`

`v17.0.1`

`v17.0.0`

Breaking

Require node >= 18.18.0
In workspaces mode, --root is now set by default (#1353)
- To not check the root package.json, use --no-root.
If you have a packageManager field in your package.json, it is now upgraded by default (#1390)
- Use --dep prod,dev,optional for the old behavior.

raineorshine/npm-check-updates@v16.14.20...v17.0.0

`v16.14.20`

Breaking

Require node >= 18.18.0
In workspaces mode, --root is now set by default (#1353)
- To not check the root package.json, use --no-root.
If you have a packageManager field in your package.json, it is now upgraded by default (#1390)
- Use --dep prod,dev,optional for the old behavior.

raineorshine/npm-check-updates@v16.14.20...v17.0.0

`v16.14.19`

`v16.14.18`

`v16.14.17`

`v16.14.16`

`v16.14.15`

`v16.14.14`

`v16.14.13`

`v16.14.12`

`v16.14.11`

`v16.14.10`

`v16.14.9`

`v16.14.8`

`v16.14.7`

`v16.14.6`

`v16.14.5`

`v16.14.4`

`v16.14.3`

`v16.14.2`

Breaking

Require node >= 18.18.0
In workspaces mode, --root is now set by default (#1353)
- To not check the root package.json, use --no-root.
If you have a packageManager field in your package.json, it is now upgraded by default (#1390)
- Use --dep prod,dev,optional for the old behavior.

raineorshine/npm-check-updates@v16.14.20...v17.0.0

`v16.14.1`

`v16.14.0`

Feature

Added experimental support for bun package manager.
Automatically used if bun.lockb is detected.
Assistance needed to test it out on different platforms.

$ ncu --packageManager bun
$ ncu -p bun

Thanks to @ImBIOS for the PR!

`v16.13.4`

`v16.13.3`

`v16.13.2`

`v16.13.1`

`v16.13.0`

Feature

Added --install option to control auto-install behavior.

Usage:

ncu --install [value]

Default: prompt

Control the auto-install behavior.

always	Runs your package manager's install command automatically after upgrading.
never	Does not install and does not prompt.
prompt	Shows a message after upgrading that recommends an install, but does not install. In interactive mode, prompts for install. (default)

`v16.12.3`

`v16.12.2`

`v16.12.1`

`v16.12.0`

`v16.11.2`

`v16.11.1`

`v16.11.0`

`v16.10.19`

`v16.10.18`

`v16.10.17`

`v16.10.16`

`v16.10.15`

`v16.10.14`

`v16.10.13`

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, check this box

This PR was generated by Mend Renovate. View the repository job log.


          Update dependency npm-check-updates to v18

846a55c

renovate bot force-pushed the renovate/npm-check-updates-18.x branch from 95181d1 to 846a55c Compare

July 23, 2025 03:42

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet