Skip to content

chore(deps): update dependency npm-check-updates to v23 - #629

Merged
ffurrer2 merged 1 commit into
mainfrom
renovate/npm-check-updates-23.x
Aug 6, 2026
Merged

chore(deps): update dependency npm-check-updates to v23#629
ffurrer2 merged 1 commit into
mainfrom
renovate/npm-check-updates-23.x

Conversation

@ffurrer2-renovate

@ffurrer2-renovate ffurrer2-renovate Bot commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
npm-check-updates devDependencies major 22.2.923.0.1

Release Notes

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

v23.0.1

Compare Source

What's Changed

Full Changelog: raineorshine/npm-check-updates@v23.0.0...v23.0.1

v23.0.0

Compare Source

⚠️ Breaking changes & migration

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).

  • Migration: Upgrade Node before installing. On older Node, stay on v22.x.

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() and ncu.defineConfig() still work as namespaced properties.

  • Migration (ESM):
    // before
    import * as ncu from 'npm-check-updates'
    const upgraded = await ncu.run({ /* ... */ })
    // after
    import ncu from 'npm-check-updates'
    const upgraded = await ncu({ /* ... */ }) // ncu.run({...}) also still works
  • Migration (CommonJS): Still usable via Node's native require() of ESM (Node 22+), but the import shape changed:
    // before
    const ncu = require('npm-check-updates')
    // after
    const { default: ncu } = require('npm-check-updates')
    ncu({ /* ... */ }).then(upgraded => console.log(upgraded))

3. filterVersion / rejectVersion no longer accept a predicate function. Use filter / reject instead. (#​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.)

  • Migration: If you passed a function to filterVersion/rejectVersion in .ncurc.js or via the module API, move it to filter / reject instead. Those receive the package name and the parsed current version, so they can match on both:
    // before
    filterVersion: (name, semver) => !(name.startsWith('@myorg/') && +semver[0].major > 5)
    // after
    filter:        (name, semver) => !(name.startsWith('@myorg/') && +semver[0].major > 5)

4. Output is now grouped by default (#​1937)
--format now defaults to ["group"], so upgrades are grouped by major / minor / patch out of the box. This is a better default for most users.

  • Migration: To get the old flat output, use:
    ncu --format no-group
    The new no- prefix removes a value from the default list instead of replacing the whole list, so --format no-group,time disables grouping while adding publish times.

5. --target semver now 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
  • Native TypeScript loading (#​1888), lazy-loaded npm-registry-fetch for faster startup (#​1898), and reduced dependencies for a lighter install.
  • Numerous bug fixes: scoped-package 404s with encoded @ (#​1923), --doctor + --errorLevel 2 crash (#​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: (UTC)

  • 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 is behind base branch, 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 has been generated by Mend Renovate CLI.

@ffurrer2-renovate ffurrer2-renovate Bot added the dependencies Pull requests that update a dependency file label Aug 2, 2026
@ffurrer2-renovate
ffurrer2-renovate Bot requested a review from ffurrer2 as a code owner August 2, 2026 02:05
@ffurrer2-renovate ffurrer2-renovate Bot added renovate Pull requests of Renovate dependencies Pull requests that update a dependency file labels Aug 2, 2026
@ffurrer2-renovate
ffurrer2-renovate Bot force-pushed the renovate/npm-check-updates-23.x branch from aaa1244 to 6ee848e Compare August 4, 2026 09:50
@ffurrer2
ffurrer2 merged commit 22857a8 into main Aug 6, 2026
18 checks passed
@ffurrer2
ffurrer2 deleted the renovate/npm-check-updates-23.x branch August 6, 2026 09:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file renovate Pull requests of Renovate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant