Closed greenkeeper[bot] closed 5 years ago
Merging #9 into master will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #9 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 3 3
Lines 58 58
=====================================
Hits 58 58
Continue to review full report at Codecov.
Legend - Click here to learn more
Ξ = absolute <relative> (impact)
,ΓΈ = not affected
,? = missing data
Powered by Codecov. Last update ab8a3a8...cf853b2. Read the comment docs.
Update to this version instead π
rules: remove typo in error message of type-case
devDependency
@commitlint/cli was updated from 5.2.8
to 7.2.0
.devDependency
@commitlint/cli was updated from 5.2.8
to 7.2.1
.devDependency
@commitlint/cli was updated from 5.2.8
to 7.3.1
.devDependency
@commitlint/cli was updated from 5.2.8
to 7.3.2
.devDependency
@commitlint/cli was updated from 5.2.8
to 7.5.1
.devDependency
@commitlint/cli was updated from 5.2.8
to 7.5.2
.devDependency
@commitlint/cli was updated from 5.2.8
to 7.6.0
.devDependency
@commitlint/cli was updated from 5.2.8
to 7.6.1
.devDependency
@commitlint/cli was updated from 5.2.8
to 8.0.0
.DeepCode analyzed this pull request. There are no new issues.
Version 6.0.0 of @commitlint/cli was just published.
The version 6.0.0 is not covered by your current version range.
If you donβt accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of @commitlint/cli.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you donβt have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v6.0.06.0.0 (2018-01-09)
Bug Fixes
Styles
BREAKING CHANGES
commitlint config, previously ignored rule
settings are now considered critical errors
when starting the CLI. The new behaviour is
designed to help developers find issues with
their configuration quicker.
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those donβt help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: