update(deps-dev): bump @commitlint/config-conventional from 20.2.0 to 20.4.2#250
Conversation
Bumps [@commitlint/config-conventional](https://github.com/conventional-changelog/commitlint/tree/HEAD/@commitlint/config-conventional) from 20.2.0 to 20.4.2. - [Release notes](https://github.com/conventional-changelog/commitlint/releases) - [Changelog](https://github.com/conventional-changelog/commitlint/blob/master/@commitlint/config-conventional/CHANGELOG.md) - [Commits](https://github.com/conventional-changelog/commitlint/commits/v20.4.2/@commitlint/config-conventional) --- updated-dependencies: - dependency-name: "@commitlint/config-conventional" dependency-version: 20.4.2 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
| "@commitlint/cli": "^20.2.0", | ||
| "@commitlint/config-conventional": "^20.2.0", | ||
| "@commitlint/config-conventional": "^20.4.2", |
There was a problem hiding this comment.
📝 Info: @commitlint/cli and @commitlint/config-conventional version specifiers are now mismatched
After this PR, @commitlint/cli remains pinned to ^20.2.0 (package.json:6) while @commitlint/config-conventional is bumped to ^20.4.2 (package.json:7). Because both use caret ranges within the same major version (20), npm will resolve compatible versions and this won't cause runtime issues. However, keeping these two sibling packages at the same minimum version is a common convention in commitlint setups. A future Dependabot PR will likely bump @commitlint/cli as well, but if it doesn't, the drift could grow. Not a bug, but worth noting for housekeeping.
Was this helpful? React with 👍 or 👎 to provide feedback.
Bumps @commitlint/config-conventional from 20.2.0 to 20.4.2.
Release notes
Sourced from
@commitlint/config-conventional's releases.... (truncated)
Changelog
Sourced from
@commitlint/config-conventional's changelog.Commits
81cfc9ev20.4.2e7ae28dv20.4.1c68de5ev20.4.03aaf0a6feat: upgrade conventional commit packages #4082 (#4597)be3a280v20.3.11c5734dv20.3.0Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)