chore(deps): update dependency npm-check-updates to v23 - #324
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update dependency npm-check-updates to v23#324renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
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
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:
22.2.9→23.0.0Release Notes
raineorshine/npm-check-updates (npm-check-updates)
v23.0.0Compare Source
1. Node.js 22+ required (#1844)
The minimum supported Node.js is now 22. Supported versions:
^22.22.2 || ^24.15.0 || >=26.0.0(and npm>=10).2. Pure ESM package — CJS build dropped, default export is now callable (#1916, #1894)
The package is now pure ESM (no more CommonJS build), and the default export is now callable directly.
ncu.run()andncu.defineConfig()still work as namespaced properties.require()of ESM (Node 22+), but the import shape changed:3.
filterVersion/rejectVersionno longer accept a predicate function. Usefilter/rejectinstead. (#1933)These options now accept only a string, wildcard, glob, comma/space-delimited list, or
/regex/. (CLI usage is unchanged — the CLI never supported functions.)filterVersion/rejectVersionin.ncurc.jsor via the module API, move it tofilter/rejectinstead. Those receive the package name and the parsed current version, so they can match on both:4. Output is now grouped by default (#1937)
--formatnow defaults to["group"], so upgrades are grouped by major / minor / patch out of the box. This is a better default for most users.no-prefix removes a value from the default list instead of replacing the whole list, so--format no-group,timedisables grouping while adding publish times.5.
--target semvernow respects explicit upper bounds (#1920)An explicit upper bound in a range is now preserved and never exceeded, e.g.
^9.5.0 <10→^9.7.0 <10(previously the bound could be overrun). This can change which versions are selected for ranges with explicit upper bounds.✨ Other improvements
npm-registry-fetchfor faster startup (#1898), and reduced dependencies for a lighter install.@(#1923),--doctor+--errorLevel 2crash (#1900), registry settings ignored by--enginesNode/--ownerChanged(#1925), and YAML catalog preservation (#1922), abort packument stream once required fields are parsed (#1901) for better performance, fix cli options being overridden by .ncurc in --deep mode (#1902), and upgrade a package in all selected sections when versions differ.Full changelog: raineorshine/npm-check-updates@v22.2.9...v23.0.0
Configuration
📅 Schedule: (in timezone Europe/Oslo)
🚦 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.