fix(security): update dependencies

BREAKING CHANGE: Drop node 6 and 8 support

Author: Simon Mollweide

.contributebuddy/config.json

@@ -30,9 +30,6 @@
 		},
 		{
 			"path": "/docs/technology-stack.md"
-		},
-		{
-			"path": "/docs/release.md"
 		}
 	],
 	"links": [

.travis.yml

@@ -5,14 +5,12 @@ cache:
 notifications:
   email: true
 node_js:
-  - '8'
-  - '6'
+  - '12'
+  - '15'
 before_script:
   - npm prune
 script:
   - npm run lint
   - npm run test
   - npm run build
-after_success:
-  - npm run report-coverage
-  - npm run semantic-release
+

README.md

@@ -23,7 +23,6 @@ Also the `.contributebuddy` directory will be added.
 Contribute buddy collect all readme files in the project and split them into sections and topics by using the `h1` and `h2` headlines. These sections and topics will be displayed in the cli before start (and after install) if you didn't read them before and nothing had changed. The reading history will be stored in your filesystem (user directory).
 
 ## Shields
-[![coverage status](https://coveralls.io/repos/github/smollweide/contribute-buddy/badge.svg?branch=master)](https://coveralls.io/github/smollweide/contribute-buddy?branch=master)
 [![npm](https://img.shields.io/npm/v/contribute-buddy.svg)](http://npm.im/contribute-buddy)
 [![downloads](https://img.shields.io/npm/dm/contribute-buddy.svg)](https://npm-stat.com/charts.html?package=contribute-buddy)
 [![MIT License](https://img.shields.io/npm/l/contribute-buddy.svg)](http://opensource.org/licenses/MIT)

docs/code-guidelines.md

@@ -12,6 +12,3 @@ We using [prettier](https://github.com/prettier/prettier) for code formatting. Y
 ## Unit Tests
 We using [jest](https://github.com/facebook/jest) for unit testing and the coverage should be higher than 90%.
 The coverage will be reported and checked before commit.
-
-## Commit style
-We using [commitizen](https://github.com/commitizen/cz-cli) for commit styles. Please run `npm run commit` to commit your changes. Also the commit messages are used to build a clean and helpful changelog. Because of this please use well written commit messages.