1

I am new to the concept of SemVer. It's seems like very promising idea to implement in my current project.

According to the SemVer concept, if a project is name project-a.b.c then, a is Major update(breaking changes), b is Minor update(newer implementations), c is patch update(bug fixes).

My question is, say if I had a Very Small breaking change for which I need to build and update my repo. What should I do then?

Is it a Major update or a Patch update?

Also, is SemVer only suitable for certain software technologies and not for every thing? For example, some Node Devs told me they rarely use this. But, I am not sure what percentage of people are practising it.

Thinker-101
  • 554
  • 5
  • 19

1 Answers1

1

Breaking change is a breaking change, no ifs or buts. You should do a MAJOR update.

SemVer purpose is to convey meaning about the underlying code and what has been modified from one version to the next. This scheme is suitable for everything where there is a need to solve compatibility issues of any kind and SemVer convention fits the purpose.

https://semver.org/

igor
  • 5,351
  • 2
  • 26
  • 22