CI(semver): Add semantic versioning
- Dominant language
- Jupyter Notebook
- Stars
- 30
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
Copied from https://github.com/apache/flagon-useralejs/issues/447
**Problem**
We currently use semantic versioning but rely on developers to manually update versionings and change logs. This creates lots of room for error.
**Solution**
Enforce proper semantic versioning and change log updates via [commitizen](https://www.npmjs.com/package/commitizen).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing how this repository currently stores its version and updates changelogs, then read the linked commitizen documentation and compare its setup requirements with the project. Done means semantic-versioning rules and changelog updates are enforced through the project’s CI or release workflow rather than relying on manual developer updates.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100