Update @metahub/cz-conventional-commit to the latest version 🚀 #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
Codecov Report
@@ Coverage Diff @@
## master #1 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 8 8
Lines 83 83
=====================================
Hits 83 83Continue to review full report at Codecov.
|
Version 1.1.1 just got published. |
pvdlg
force-pushed
the
greenkeeper/@metahub/cz-conventional-commit-1.1.0
branch
from
4582d87
to
b836bf0
Compare
greenkeeper
bot
deleted the
greenkeeper/@metahub/cz-conventional-commit-1.1.0
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Version 1.1.0 of @metahub/cz-conventional-commit just got published.
The version 1.1.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of @metahub/cz-conventional-commit.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
v1.1.01.1.0 (2017-08-24)
Builds
Chores
Continuous Integrations
Features
Commits
The new version differs by 19 commits.
dc4cb0bMerge pull request #3 from vanduynslagerp/update9b47044ci(codeclimate): Add Code Climate support ⚙️c1545d5chore(lint): Add prepush hook ♻️f3d265ffeat(types): use conventional-changelog-metahub ✨c1ebc7cbuild(travis): Use Travis stages 🛠80b29fabuild(release): Use conventional-changelog-metahub release config 🛠2844677build(release): Add semantic-release plugin sr-commit-analyzer 🛠0574331chore(package): update eslint-plugin-prettier to version 2.2.0 ⬆️25c6f6cchore(package): update sinon to version 3.2.1 ⬆️2f24685chore(package): update sr-release-notes-generator to version 1.1.1 ⬆️42fded6chore(package): update @metahub/eslint-config to version 1.6.1 ⬆️7c0de28chore(package): update semantic-release to version 8.0.0 ⬆️07977c6chore(package): update eslint to version 4.5.0 ⬆️259b222chore(package): update babel-cli to version 6.26.0 ⬆️deba9c0chore(package): update @commitlint/core to version 3.1.3 ⬆️There are 19 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴