Upgrade dependencies #10
Conversation
migrate eslint prettier plugin and configuration plugin configuration due to breaking changes
lint all files by executing 'lint' npm script
it contains all TypeScript type declarations for commitlint package types
initialize husky to install git commit hooks in prepare script
as discussion at: https://github.com/xeptore/commitiquette/pull/1#pullrequestreview-626076153 we decided to remove prentheses around sole arrow function paraemeters. a re-linting commit will be issued in the next commit.
as the result of disscussion at: https://github.com/xeptore/commitiquette/pull/1#pullrequestreview-626057744, we decided to revert back to '== null' checks.
Upgrade Dependencies
|
It looks like tests failed in relation to full-stop. I think commitlint used to require a provided full-stop char, but then they removed that param. If I remember right. |
|
About the failing tests, there is a bug I found in some rule configuration type declarations of |
typescript 4.2.3 => 4.2.4
tslib 2.1.0 => 2.2.0
@typescript-eslint/eslint-plugin 4.20.0 => 4.21.0 @typescript-eslint/parser 4.20.0 => 4.21.0
@commitlint/cli 12.0.1 => 12.1.1 @commitlint/config-conventional 12.0.1 => 12.1.1 @commitlint/load 12.0.1 => 12.1.1 @commitlint/types 12.0.1 => 12.1.1
|
conventional-changelog/commitlint#2534 has been merged. Waiting for the new version publish to update our dependencies. |
|
@xeptore I believe the changes you made to commitlint have been released. Can you update this PR with an updated commitlint version? |
Codecov Report
@@ Coverage Diff @@
## master #10 +/- ##
==========================================
+ Coverage 79.03% 79.47% +0.44%
==========================================
Files 12 12
Lines 372 380 +8
Branches 77 88 +11
==========================================
+ Hits 294 302 +8
+ Misses 78 77 -1
- Partials 0 1 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
|
|
@martinmcwhorter, all outdated dependencies, including commitlint were updated. It seems it is a bad credential error that causes the Node.js CI job to fail, and everything else is working fine. |
Upgrade all dependencies to their latest version.
Closes #4.