Version Details and Security Vulnerabilities

📦

@commitlint/cli

17.2.0

Comparision Betweeen 17.2.0 and 17.1.2

Identify the differences between the current version of the package and the previous one.

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

28.83 KB

27.83 KB

Version 17.2.0 Details

@commitlint/cli helps developers enforce commit message conventions for cleaner project histories. Version 17.2.0 introduces several updates compared to the previous stable version, 17.1.2. Primarily, core dependencies have been bumped. @commitlint/lint, responsible for the actual linting process, jumps from version 17.1.0 to 17.2.0, likely including new rules, bug fixes, or performance enhancements in the linting logic. Similarly, @commitlint/load, which handles loading configuration files, moves from 17.1.2 to 17.2.0 suggesting improvements in configuration handling or supported configuration formats. The @commitlint/read package moves from 17.1.0 to 17.2.0, implying changes or fixes on parsing the commit messages.

Moreover, the testing and utility devDependencies see upgrades: @commitlint/test and @commitlint/utils both move from 17.0.0 to 17.2.0. No new dependencies are added. Developers upgrading should particularly review the changelogs for @commitlint/lint, @commitlint/load, @commitlint/read, @commitlint/test and @commitlint/utils for specific details on new features or breaking changes. These upgrades can enhance the accuracy and flexibility of commit message linting, and improve the developer experience. Developers can expect more stable and performant testing and utility functionalities also. @commitlint/types and @commitlint/format didn't receive updates between the versions. The package size also increased slightly.

Security Vulnerabilities

This site is an independent open-source project and is not affiliated with, endorsed by, or sponsored by npm, Inc. or GitHub, Inc. The name “npm” is a registered trademark of npm, Inc., used here solely to describe compatibility and reference publicly available npm package data.