feat: Update `@commitlint/cz-commitlint` peerDependency on `inquirer@9` to `inquirer@latest`

[chris-dura]

Expected Behavior

The @commitlint/cz-commitlint docs list a required peer dependency on inquirer@9. The inquirer package is now at v13, and eventually this requirement of an out-of-date version may cause problems for users.

• https://www.npmjs.com/package/@commitlint/cz-commitlint#getting-started

Current Behavior

No response

Affected packages

• cli
• core
• prompt
• config-angular

Possible Solution

No response

Context

No response

[YasharF]

I have already incorporating this in the PR I am working on. Although, I have been looking at moving to @inquirer/prompt , because the folks at inquirer have said that is the upgrade path. inquirer v12 is the final version, and projects need to move to @inquirer/prompt sooner or later.

[johnny-the-coder]

Hello, can we expect a new release including an update of the inquirer in the near future (this year)?
Basically, a release with updated outdated dependencies.

[YasharF]

So sorry, I got dragged into another project. I will be getting back to work on this this week.

[escapedcat]

No worries, thanks for the update!

[kennethwkz-mm]

thanks for the update

[johnny-the-coder]

Hello, any news on updating the dependency in the near future?

[escapedcat]

We currently need to stay on node v18. But whoever is motivated could give upgrading a try and create a PR

Version Compatibility Matrix

Inquirer Version	Node.js Requirement	Compatible with commitlint (Node >=18)?
v9.3.8 (legacy)	>=18	✅ Yes (currently used)
v10.x	>=18	✅ Yes
v11.x	>=18	✅ Yes
v12.x	>=18	✅ Yes
v13.x (latest)	>=20.12.0	❌ No (requires Node 20.12+)

[YasharF]

I am so sorry if I missed it from the other issues, but what is driving the requirement to continue supporting node v18, and not just staying with LTS versions at https://github.com/nodejs/Release?

[escapedcat]

I am so sorry if I missed it from the other issues, [...]

No worries, it's mainly related to which version Ubtuntu LTS supports and if we have good reasons to move to an new minimum version.

From this issues description:

[...] eventually this requirement of an out-of-date version may cause problems for users.

As long as nothing causing an issue for users we do not have to upgrade I guess.

[YasharF]

Totally get wanting to minimize churn. It feels like keeping Node 18 as the floor is already creating extra work by having to tiptoe around dependencies that have dropped or are dropping non‑Foundation LTS support, like cross-env, yargs, and @inquirer/prompt. As the ecosystem moves on, that maintenance cost typically just grows. Aligning with the Node Foundation's active LTS window will likely make things easier in the long run.

[escapedcat]

The good news is that the new Ubuntu LTS will drop soon. So once that is out, we can move.

Ubuntu 26.04 LTS (Resolute Raccoon)

• Release Date: April 23, 2026 (source (https://discourse.ubuntu.com/t/resolute-raccoon-release-schedule/47198))
• Node.js Version: 22.22.0 (source (https://packages.ubuntu.com/resolute/nodejs))
• Codename: Resolute Raccoon