Update dependency commander to v14 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
commander	^13.1.0 -> ^14.0.0

---

Release Notes

tj/commander.js (commander)

v14.0.2

Compare Source

Changed

• improve negative number auto-detection test ([#​2428])
• update (dev) dependencies

v14.0.1

Compare Source

Fixed

• broken markdown link in README ([#​2369])

Changed

• improve code readability by using optional chaining ([#​2394])
• use more idiomatic code with object spread instead of Object.assign() ([#​2395])
• improve code readability using string.endsWith() instead of string.slice() ([#​2396])
• refactor .parseOptions() to process args array in-place ([#​2409])
• change private variadic support routines from ._concatValue() to ._collectValue() (change code from array.concat() to array.push()) ([#​2410])
• update (dev) dependencies

v14.0.0

Compare Source

Added

• support for groups of options and commands in the help using low-level .helpGroup() on Option and Command, and higher-level .optionsGroup() and .commandsGroup() which can be used in chaining way to specify group title for following options/commands ([#​2328])
• support for unescaped negative numbers as option-arguments and command-arguments ([#​2339])
• TypeScript: add parseArg property to Argument class ([#​2359])

Fixed

• remove bogus leading space in help when option has default value but not a description ([#​2348])
• .configureOutput() now makes copy of settings instead of modifying in-place, fixing side-effects ([#​2350])

Changed

• Breaking: Commander 14 requires Node.js v20 or higher
• internal refactor of Help class adding .formatItemList() and .groupItems() methods ([#​2328])

---

Configuration

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

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: src/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @commander-js/[email protected]
npm error Found: [email protected]
npm error node_modules/commander
npm error   commander@"^14.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer commander@"~13.1.0" from @commander-js/[email protected]
npm error node_modules/@commander-js/extra-typings
npm error   @commander-js/extra-typings@"^13.1.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/commander
npm error   peer commander@"~13.1.0" from @commander-js/[email protected]
npm error   node_modules/@commander-js/extra-typings
npm error     @commander-js/extra-typings@"^13.1.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --no-strict-peer-deps, --force, or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-11-18T10_16_14_443Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-11-18T10_16_14_443Z-debug-0.log