feat: automate changelog

[silentnoodlemaster]

we should still discuss:

• do we need commitlint
• do we need to adjust the configuration files
• ???

todo:

• [ ] documentation

closes #15

[silentnoodlemaster]

alternatively commitizen instead of commitlint

(or both)

[taromorimoto]

How does the automatic versioning work?

[silentnoodlemaster]

@taromorimoto

How does the automatic versioning work?

this readme will explain it better than i ever could https://github.com/conventional-changelog/standard-version

[oxyc]

I think I personally need commitlint/commitizen in the beginning to get used to it :D if we want we can always drop it later.

So we should also update https://github.com/generoi/genero-design-system#publishing-a-new-version

Something like:

# Create release, generate changelog and bump the version based on commit log
npm run release
# Create a named prerelease version
npm run release -- --prerelease beta
# Manually specifify the version bump
npm run release -- --release-as minor
npm run release -- --release-as 1.1.0

# Push and publish release
git push
git push --tags
npm publish

[oxyc]

If we do, should we point people to https://www.conventionalcommits.org/en/v1.0.0/ or will the lint error be descriptive enough to lead people there?

[taromorimoto]

If we do, should we point people to https://www.conventionalcommits.org/en/v1.0.0/ or will the lint error be descriptive enough to lead people there?

I would imagine that the lint error should be enough. The readme will anyways talk about using this.

[taromorimoto]

@silentnoodlemaster can you add @oxyc's suggestions to readme and merge?