chore(deps): update dependency npm-check-updates to v18#675
Merged
Conversation
renovate
Bot
force-pushed
the
renovate/npm-check-updates-18.x
branch
from
b9f672f to
374e230
Compare
renovate
Bot
force-pushed
the
renovate/npm-check-updates-18.x
branch
from
374e230 to
ea9b770
Compare
renovate
Bot
force-pushed
the
renovate/npm-check-updates-18.x
branch
from
ea9b770 to
f4fb056
Compare
erik-slovak
approved these changes
May 14, 2025
Contributor
|
🎉 This PR is included in version 1.0.20 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^17.1.18->^18.0.1Release Notes
raineorshine/npm-check-updates (npm-check-updates)
v18.0.1Compare Source
v18.0.0Compare Source
Breaking
The only breaking change in v18 is with the
-g/--globalflag.npm-check-updates -gwill now auto-detect your package manager based on the execution path. Previously, it defaulted tonpm.yarn dlx ncu -g --packageManager yarn→yarn dlx ncu -gpnpm dlx ncu --global --packageManager pnpm→pnpm dlx ncu -gbunx ncu -g--packageManager pnpm→bunx ncu -gIf for some reason you were running
ncu -gwith an alternative package manager and relying on it checking the globalnpmpackages, you will need to now explicitly specify npm:ncu -g→ncu -g--packageManager npmThanks to @LuisFerLCC for the improvement (#1514).
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.
This PR was generated by Mend Renovate. View the repository job log.