Automate release and changelog

[ypid]

I have experience with commitizen (Python) but there is also a commitizen (JavaScript)/commit-and-tag-version. The later seem better integrated into the NodeJS/Husky/NPM ecosystem. Both of them can be used to generate the changelog.

@KristjanESPERANTO What do you think? Which one do you prefer? I saw the need for those tools because the release process currently requires you to manually update multiple files:

• package.json
• package-lock.json
• bower.json

cz-cli does not seem to integrate with pre-commit.com. Ref: commitizen/cz-cli#801

I don’t want to push into any direction. It needs to work primarily for @KristjanESPERANTO. I just want to kick this discussion off.

• Setup commitlint, gitlint (Python) has been tested in chore: lint git commit messages with gitlint #492 but this seems to be less common in JavaScript projects.

[KristjanESPERANTO]

I'm familiar with using husky in combination with lint-staged to automatically lint staged files before committing them. Therefore, and while this is a JavaScript project, I would prefer cz-cli. I haven't used it until now, but it seems useful and I would like to check it out.

the release process currently requires you to manually update multiple files

To do just that, bummp would be much more lightweight.

But cz-cli seems to have additional advantages such as more standardized commit messages and simplified creation of the CHANGELOG.

As far as I'm concerned, we can go in that direction 🙂

[KristjanESPERANTO]

Switching the changelog to markdown is a step in that direction: #509 🙂