You should know about these

Semantic Versioning

format: ..

MAJOR Introduce a new backward-incompatible change 1.0.0 → 2.0.0 MINOR Introduce a new backward-compatible change 1.0.0 → 1.1.0 PATCH Fix a bug while maintaining backward-compatibility 1.0.0 → 1.0.1

Major

Remove an operation, i.e. remove an HTTP verb/path combination Add a mandatory field to a request payload Add/remove a field to a response payload Adding a field may not be a breaking change if all consumers are deemed sufficiently tolerant

Minor

Add a new operation, i.e. a new HTTP verb/path combination Add an optional field to a request payload

Patch

No interface changes

after then install this packages: npm i --save-dev standard-version

then we just need to add a script in our package.json { "script":{ "release":"standard-version" } }

first commit: Major feat: init BREAKING CHANGE: change license

then excute in any commit: "npm run release"

second commit: Minor 1. feat(my-operation): allow users to provide an optional name to override the default 2. feat: add operation to retrieve sub-records

thirth commit: Patch 1. fix: remove the infinite loop 2. fix(my-operation): handle null input field

forth commit: N/A 1. test: refactor user management test cases 2. ci: point to the new registry 3. docs: add missing method documentation in create operation