Skip to content

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

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-check-updates-23.x
Open

chore(deps): update dependency npm-check-updates to v23#326
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-check-updates-23.x

Conversation

@renovate

@renovate renovate Bot commented Sep 9, 2026 •
edited
Loading

Copy link
Copy Markdown

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
npm-check-updates 16.14.20 → 23.1.0 age confidence

Release Notes

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

v23.1.0

Compare Source

Added new option: --interactiveSelect

Usage:

ncu -i --interactiveSelect [value]

Default: auto

Control which upgrades are pre-selected in interactive mode. Only applies with --interactive.

autoPre-selects patch and minor upgrades with --format group, which is enabled by default, and all upgrades otherwise. This is what ncu -i does. (default)
noneNothing is pre-selected.
patchPatch upgrades are pre-selected.
minorPatch and minor upgrades are pre-selected.
allAll upgrades are pre-selected, including major.

Specify auto explicitly to restore the default when another value is set in your config file.

Major version zero upgrades (e.g. 0.1.0 → 0.2.0) are only pre-selected by all, since anything may change before 1.0.0. Custom groups returned by --groupFunction are likewise only pre-selected by all.

Other Changes
New Contributors

Full Changelog: raineorshine/npm-check-updates@v23.0.2...v23.1.0

v23.0.2

Compare Source

Added new option: --interactiveSelect

Usage:

ncu -i --interactiveSelect [value]

Default: auto

Control which upgrades are pre-selected in interactive mode. Only applies with --interactive.

autoPre-selects patch and minor upgrades with --format group, which is enabled by default, and all upgrades otherwise. This is what ncu -i does. (default)
noneNothing is pre-selected.
patchPatch upgrades are pre-selected.
minorPatch and minor upgrades are pre-selected.
allAll upgrades are pre-selected, including major.

Specify auto explicitly to restore the default when another value is set in your config file.

Major version zero upgrades (e.g. 0.1.0 → 0.2.0) are only pre-selected by all, since anything may change before 1.0.0. Custom groups returned by --groupFunction are likewise only pre-selected by all.

Other Changes
New Contributors

Full Changelog: raineorshine/npm-check-updates@v23.0.2...v23.1.0

v23.0.1

Compare Source

What's Changed

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

v23.0.0

Compare Source

What's Changed

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

v22.2.9

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

v22.2.8

Compare Source

What's Changed

Full Changelog: raineorshine/npm-check-updates@v22.2.8...v22.2.9

v22.2.7

Compare Source

What's Changed

Full Changelog: raineorshine/npm-check-updates@v22.2.7...v22.2.8

v22.2.6

Compare Source

What's Changed

Full Changelog: raineorshine/npm-check-updates@v22.2.6...v22.2.7

v22.2.5

Compare Source

What's Changed
New Contributors

Full Changelog: raineorshine/npm-check-updates@v22.2.5...v22.2.6

v22.2.3

Compare Source

e951cf4 Bump minor and patch.
0f9f53d prettier
edf4212 Make deep tests path-agnostic with regex patterns
b820131 Only show missing time when time or cooldown format is requested

Full Changelog: raineorshine/npm-check-updates@v22.2.3...v22.2.5

v22.2.2

Compare Source

What's Changed

Full Changelog: raineorshine/npm-check-updates@v22.2.2...v22.2.3

v22.2.1

Compare Source

What's Changed

Full Changelog: raineorshine/npm-check-updates@v22.2.1...v22.2.2

v22.2.0

Compare Source

What's Changed

Full Changelog: raineorshine/npm-check-updates@v22.2.0...v22.2.1

v22.1.1

Compare Source

What's Changed

❗ Important

✂ PR body was truncated to here.

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 was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/npm-check-updates-23.x branch from 5815961 to 4f14b42 Compare September 10, 2026 00:49
@coderabbitai

coderabbitai Bot commented Sep 10, 2026 •
edited
Loading

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: f8daae08-d0fa-4de2-b80c-3266e9663c6a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

@renovate
renovate Bot force-pushed the renovate/npm-check-updates-23.x branch 9 times, most recently from 15a12cd to 1f5113c Compare September 17, 2026 00:53
@renovate
renovate Bot force-pushed the renovate/npm-check-updates-23.x branch 7 times, most recently from 2a83e38 to 9c9009a Compare September 24, 2026 01:03
@renovate
renovate Bot force-pushed the renovate/npm-check-updates-23.x branch 8 times, most recently from b7186e0 to 10ac5be Compare October 2, 2026 00:55
@nx-cloud

nx-cloud Bot commented Oct 2, 2026 •
edited
Loading

Copy link
Copy Markdown

View your CI Pipeline Execution ↗ for commit b74db35

Command Status Duration Result
nx affected --target=build --output-style=strea... ✅ Succeeded 2m 43s View ↗

💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗

☁️ Nx Cloud last updated this comment at 2026-10-07 01:02:09 UTC

@renovate
renovate Bot force-pushed the renovate/npm-check-updates-23.x branch 3 times, most recently from e041650 to c479102 Compare October 5, 2026 01:01
@renovate
renovate Bot force-pushed the renovate/npm-check-updates-23.x branch from c479102 to cf299c7 Compare October 6, 2026 00:58
@renovate
renovate Bot force-pushed the renovate/npm-check-updates-23.x branch from cf299c7 to b74db35 Compare October 7, 2026 00:58

This branch has not been deployed

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

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants