@commitlint/cli version 13.2.1 is a patch release following closely on the heels of 13.2.0, providing minor updates and fixes to the commit message linter. Both versions build upon the existing functionality to enforce commit message conventions, promoting consistency and clarity in project histories. Dependencies like yargs, lodash, resolve-from and @commitlint/* packages remain largely consistent, suggesting a focus on refining existing features rather than introducing significant overhauls. A notable difference lies in updated @commitlint/load dependency in the newer relase.
Developers will appreciate that the core purpose of the tool remains unaffected: ensuring commit messages adhere to a defined style, which is crucial for automated changelog generation, improved collaboration, and easier understanding of project evolution. By integrating @commitlint/cli into their workflows, teams can automate the process of validating commit messages, catching style errors early and improving the overall code quality. The dependency on @commitlint/format will make possible to customize the output of the command and improving the developer experience.
The patch specifically addresses potential issues or minor improvements in the loading or handling of commitlint configurations, with the updated @commitlint/load fixing some possible bugs or inconsistencies. The updated @types/node dependency in the newer version suggests there has been some minor changes in the typing definitions. For developers already using 13.2.0, upgrading to 13.2.1 is recommended to leverage these refinements and ensure a more stable and reliable commit linting experience. The update is seamless and doesn't require modifications to existing configurations unless facing issues related to config loading.
All the vulnerabilities related to the version 13.2.1 of the package
semver vulnerable to Regular Expression Denial of Service
Versions of the package semver before 7.5.2 on the 7.x branch, before 6.3.1 on the 6.x branch, and all other versions before 5.7.2 are vulnerable to Regular Expression Denial of Service (ReDoS) via the function new Range, when untrusted user data is provided as a range.