Skip to content

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

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

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

Conversation

@renovate

@renovate renovate Bot commented Oct 4, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
npm-check-updates ~12.0.0 → ~23.1.0 age adoption passing confidence
npm-check-updates ^12.0.0 → ^23.0.0 age adoption passing 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

What's Changed

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

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

v22.2.9

Compare Source

What's Changed

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

v22.2.8

Compare Source

What's Changed

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

v22.2.7

Compare Source

What's Changed

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

v22.2.6

Compare Source

What's Changed

New Contributors

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

v22.2.5

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

Compare Source

What's Changed

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

v22.2.2

Compare Source

What's Changed

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

v22.2.1

Compare Source

What's Changed

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

v22.2.0

Compare Source

What's Changed

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

v22.1.1

Compare Source

What's Changed

New Contributors

Full Changelog: raineorshine/npm-check-updates@v22.1.0...v22.1.1

v22.1.0

Compare Source

What's Changed

Full Changelog: raineorshine/npm-check-updates@v22.0.1...v22.1.0

v22.0.1

Compare Source

What's Changed

  • fix: suppress cooldown config log messages when JSON output is active by @​Copilot in #​1692

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

v22.0.0

Compare Source

v21.0.3

Compare Source

What's Changed

Full Changelog: raineorshine/npm-check-updates@v21.0.2...v21.0.3

v21.0.2

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 becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

  • If you want to rebase/retry this PR, check this box

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

@KovacZan KovacZan mentioned this pull request Oct 5, 2026
Merged
KovacZan added a commit that referenced this pull request Oct 5, 2026
@KovacZan
chore(nameservice): integrate open pull requests #141, #143, #144, #145…
10e1d02 
… into develop (PR #146)

Squash-merge of the integration chain factory/develop-integration-d027c425 (baseline 2147c60): per-PR merge commits 9e4fca0 (#141), 1ed0d0b (#143), 8a23ae7 (#144), b85a2f5 (#145) summarized here because the repository does not allow merge commits on develop. All gates green; conflict union documented in PR body. #140 and #142 excluded (incompatible, see PR body).
@KovacZan

KovacZan commented Oct 5, 2026

Copy link
Copy Markdown
Member

Integrated into develop in 10e1d02. Its contents reached develop through PR #146 (squash merge — this repository does not allow merge commits or direct pushes to the protected develop branch). The integration branch factory/develop-integration-d027c425 contained the integration merge commit 9e4fca0 with this PR's head c380d03 as its second parent; GitHub merge detection did not attribute this local merge, so it is closed as integrated-by-link.

@KovacZan KovacZan closed this Oct 5, 2026
@renovate renovate Bot changed the title chore(deps): update dependency npm-check-updates to v23 chore(deps): update dependency npm-check-updates to v23 - autoclosed Oct 5, 2026
@renovate
renovate Bot deleted the renovate/npm-check-updates-23.x branch October 5, 2026 06:29
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.

1 participant

@KovacZan