chore: update @commitlint/cli and husky dev dependencies #959
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates the
@commitlint
dependencies to their latest versions, fixing another 5 vulnerability reports from runningnpm install
. The big change from7.*
to8.*
was:However, this has no effect in usage with husky, and the usage string remains the same. However, given their connection, I also updated husky as well from
1.*
to2.*
where the breaking change was that it dropped Node 6 support. The commitlint repo dropped Node 6 support on the8.1.0
release.There is an even newer version of husky (v3) that is available, but it adds a requirement on having
git >= 2.13.2
which is probably largely true on most systems, but figured that might be a bit too breaking. However, if it's decided that's not really that big of an issue, there is no issue moving to v3 from v2.Checklist
npm test
passes (tip:npm run autofix
can correct most style issues)