Understanding project versioning

based on Blog: https://gomakethings.com/semantic-versioning/

Coding projects majorly use semantic versioning, sometimes called semver.

Semantic versioning uses a major.minor.patch pattern.

If a piece code was version 4.2.1, 4 would be the major version, 2 would be the minor version, and 1 would be the patch.

1. MAJOR version when you make incompatible API changes,
2. MINOR version when you add functionality in a backwards compatible manner, and
3. PATCH version when you make backwards compatible bug fixes.

We can think of it like,

breaking.feature.fix

1. A major version bump breaks the existing code base’s backwards compatibility.
2. A minor version bump adds one or more new features.
3. A patch version bump fixes bugs or security issues.

Note: To solve the confusion: Pick the highest version type that applies

— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —

Version Bumping:

It means to increment the version number to a new, unique value.

What is bump in GitHub?

Bump updates the project’s version, updates/creates the changelog, makes the bump commit, tags the bump commit and makes the release to GitHub.