Version Details and Security Vulnerabilities

@commitlint/cli has been updated from version 17.8.1 to 18.0.0, marking a notable release for developers using this commit message linter. Both versions share the same core functionality of linting commit messages and similar dependencies like execa, yargs, and resolution utilities. The primary difference lies in the updated versions of core @commitlint dependencies. Notably, @commitlint/lint, @commitlint/load, @commitlint/read, @commitlint/types, and @commitlint/format have all jumped from 17.8.1 to 18.0.0. This suggests significant internal updates, potentially incorporating new features, bug fixes, or performance improvements within the commitlint ecosystem.

For developers, this upgrade means staying current with the latest rule sets, configuration options, and best practices for commit message formatting enforced by commitlint. While the API surface might remain relatively stable, upgrading is generally recommended to leverage the most recent enhancements and security patches within the core linting logic and related utilities. A key change to also consider is the updated @types/node dependency in the new version, going from ^14.0.0 to ^18.11.9. This indicates that the newer version now requires a newer Node.js version, ensure the environments where this new package is deployed fulfills this requirement. Always refer to the official commitlint documentation for a comprehensive migration guide and detailed release notes to understand the specific changes in version 18.0.0 and adapt tooling, configurations, and workflows accordingly.