chore(deps-dev): bump @commitlint/config-conventional from 20.5.3 to 21.0.0#265
chore(deps-dev): bump @commitlint/config-conventional from 20.5.3 to 21.0.0#265dependabot[bot] wants to merge 21 commits into
Conversation
Bumps [@commitlint/config-conventional](https://github.com/conventional-changelog/commitlint/tree/HEAD/@commitlint/config-conventional) from 20.5.3 to 21.0.0. - [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/v21.0.0/@commitlint/config-conventional) --- updated-dependencies: - dependency-name: "@commitlint/config-conventional" dependency-version: 21.0.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
…nventional-21.0.0
…nventional-21.0.0
don-petry
left a comment
don-petry
left a comment
There was a problem hiding this comment.
Dev-Lead Review
This is a major version bump with a breaking change worth flagging:
Breaking change: @commitlint/config-conventional v21.0.0 raises the minimum Node.js requirement from ≥18 to ≥22. The CI pipeline currently uses Node 20 (node-version: '20' in .github/workflows/ci.yml).
Practical impact: Commitlint runs only in pre-commit hooks (via Husky), not in CI directly, so all CI checks still pass. However, developers running Node 20 locally will get an unsupported-engine warning (or may hit runtime errors depending on which Node 22 built-ins v21 now uses directly).
Related PR: #269 bumps @commitlint/cli to v21.0.0 as well — these two packages must move together since they belong to the same monorepo and must stay on matching majors. Merging this PR alone while @commitlint/cli stays at v20 will create a version mismatch.
Recommendation: Merge #265 and #269 together (or in quick succession), and consider bumping node-version in the CI workflow to '22' at the same time to stay consistent with the new engine requirement.
All other checks pass — no functional issues introduced.
…nventional-21.0.0
|
A newer version of @commitlint/config-conventional exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged. |
…nventional-21.0.0
…nventional-21.0.0
|
@dev-lead - please fix this PR |
…nventional-21.0.0
…nventional-21.0.0
…nventional-21.0.0
…nventional-21.0.0
…nventional-21.0.0
…nventional-21.0.0
…nventional-21.0.0
…nventional-21.0.0
…nventional-21.0.0
…nventional-21.0.0
…nventional-21.0.0
…nventional-21.0.0
…nventional-21.0.0
…nventional-21.0.0
…nventional-21.0.0
|
1 participant
Bumps @commitlint/config-conventional from 20.5.3 to 21.0.0.
Release notes
Sourced from @commitlint/config-conventional's releases.
Changelog
Sourced from @commitlint/config-conventional's changelog.
Commits
f081a8ev21.0.044c3174chore: update dependency yargs to v18 #4432 (#4686)ac2b3f4chore!: minimum node version v22 (#4679)Dependabot 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)