I'm totally with you on this and I can't help but recommend using Semantic Versioning [1] + Semantic Release [2] in combination with Conventional Commits to automagically generate release notes/changelogs.
I just did a presentation yesterday for my colleagues at work on that subject [3]
The semantic release configuration is within the .releaserc file.
Running npm run release triggers a local release based on the commits history and the latest generated tag.
This is awesome, thank you for sharing! I have an upcoming presentation at work regarding conventional commits + tooling, and I will absolutely bring Semver + Semantic Release up.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hey Cole,
I'm totally with you on this and I can't help but recommend using Semantic Versioning [1] + Semantic Release [2] in combination with Conventional Commits to automagically generate release notes/changelogs.
I just did a presentation yesterday for my colleagues at work on that subject [3]
The semantic release configuration is within the
.releasercfile.Running
npm run releasetriggers a local release based on the commits history and the latest generated tag.[1] semver.org/
[2] github.com/semantic-release/semant...
[3] github.com/bchhun/my-wonderful-book
This is awesome, thank you for sharing! I have an upcoming presentation at work regarding conventional commits + tooling, and I will absolutely bring Semver + Semantic Release up.