Look at integrating release-it

[softchris]

Description

This library facilitates versioning and helps to publish to NPM https://www.npmjs.com/package/release-it

Type of change

Please delete options that are not relevant.

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

Closing issues

Put closes #XXXX in your comment to auto-close the issue that your PR fixes (if such).

Assignee

Please add yourself as the assignee

Projects

Please add relevant projects so this issue can be properly tracked.

[johnpapa]

While I like this idea - I am hesitant to automate this until we know exactly what we want our release cycle to include. Then we can automate it.

Thoughts?

[sinedied]

I definitely agree with @johnpapa about the release cycle. Though we could still setup everything to have a semi-automated workflow (aka npm run release and take a ☕️ ) in the meantime. Also I suggest using semantic-release instead of release-it, to push the automation a bit further and reduce the maintenance pain:

• force usage of conventional commits
• generate changelogs automatically
• follow semver and bump version automatically according to commits
• publish to npm & create github release with the changelog What do you think?