Thilawyn/website
1
0
Fork 0
Code Issues 1 Pull Requests 11 Actions Packages Projects Releases Wiki Activity

Update dependency npm-check-updates to v23 - autoclosed #90

Closed
renovate-bot wants to merge 1 commits from renovate/npm-check-updates-23.x into next
pull from: renovate/npm-check-updates-23.x
merge into: Thilawyn:next
Conversation 0 Commits 1 Files Changed 2
+3 -3
renovate-bot commented 2026-07-27 04:25:00 +02:00
Collaborator
Copy Link
Copy Source

This PR contains the following updates:

Package Change Age Confidence
npm-check-updates ^22.2.0 → ^23.0.0 age confidence

Release Notes

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

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

Full changelog: https://github.com/raineorshine/npm-check-updates/compare/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 becomes conflicted, 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.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [npm-check-updates](https://github.com/raineorshine/npm-check-updates) | [`^22.2.0` → `^23.0.0`](https://renovatebot.com/diffs/npm/npm-check-updates/22.2.9/23.0.0) | ![age](https://developer.mend.io/api/mc/badges/age/npm/npm-check-updates/23.0.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/npm-check-updates/22.2.9/23.0.0?slim=true) | --- ### Release Notes <details> <summary>raineorshine/npm-check-updates (npm-check-updates)</summary> ### [`v23.0.0`](https://github.com/raineorshine/npm-check-updates/releases/tag/v23.0.0) [Compare Source](https://github.com/raineorshine/npm-check-updates/compare/v22.2.9...v23.0.0) ##### ⚠️ Breaking changes & migration **1. Node.js 22+ required** ([#&#8203;1844](https://github.com/raineorshine/npm-check-updates/issues/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** ([#&#8203;1916](https://github.com/raineorshine/npm-check-updates/issues/1916), [#&#8203;1894](https://github.com/raineorshine/npm-check-updates/issues/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):* ```js // 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: ```js // 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.** ([#&#8203;1933](https://github.com/raineorshine/npm-check-updates/issues/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: ```js // before filterVersion: (name, semver) => !(name.startsWith('@&#8203;myorg/') && +semver[0].major > 5) // after filter: (name, semver) => !(name.startsWith('@&#8203;myorg/') && +semver[0].major > 5) ``` **4. Output is now grouped by default** ([#&#8203;1937](https://github.com/raineorshine/npm-check-updates/issues/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: ```bash 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** ([#&#8203;1920](https://github.com/raineorshine/npm-check-updates/issues/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 ([#&#8203;1888](https://github.com/raineorshine/npm-check-updates/issues/1888)), lazy-loaded `npm-registry-fetch` for faster startup ([#&#8203;1898](https://github.com/raineorshine/npm-check-updates/issues/1898)), and reduced dependencies for a lighter install. - Numerous bug fixes: scoped-package 404s with encoded `@` ([#&#8203;1923](https://github.com/raineorshine/npm-check-updates/issues/1923)), `--doctor` + `--errorLevel 2` crash ([#&#8203;1900](https://github.com/raineorshine/npm-check-updates/issues/1900)), registry settings ignored by `--enginesNode`/`--ownerChanged` ([#&#8203;1925](https://github.com/raineorshine/npm-check-updates/issues/1925)), and YAML catalog preservation ([#&#8203;1922](https://github.com/raineorshine/npm-check-updates/issues/1922)). **Full changelog:** <https://github.com/raineorshine/npm-check-updates/compare/v22.2.9...v23.0.0> </details> --- ### 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 this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yODEuMSIsInVwZGF0ZWRJblZlciI6IjQzLjI4MS4xIiwidGFyZ2V0QnJhbmNoIjoibmV4dCIsImxhYmVscyI6W119-->
renovate-bot added 1 commit 2026-07-27 04:25:00 +02:00
Update dependency npm-check-updates to v23
Lint / lint (push) Failing after 27s
Details
Build / build (pull_request) Successful in 1m21s
Details
4b31c0de2a
renovate-bot changed title from Update dependency npm-check-updates to v23 to Update dependency npm-check-updates to v23 - autoclosed 2026-07-27 14:08:41 +02:00
renovate-bot closed this pull request 2026-07-27 14:08:41 +02:00
Some checks are pending
Lint / lint (push) Failing after 27s
Details
Build / build (pull_request) Successful in 1m21s
Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
renovate-bot (Renovate Bot) Thilawyn (Julien Valverdé)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Thilawyn/website#90
Delete Branch "renovate/npm-check-updates-23.x"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?