Semantic Versioning
A few examples of when to increment semantic system
When discussing periodic releases of your software application or product, we usually refer to a versioning system. Proper semantic versioning offers significant information to users of your software. If your product is used as a dependency, it is crucial to follow appropriate semantic conventions. Here is a quick overview of examples to help you understand semantic versioning system.
Version numbers and their changes convey important information about the underlying code and the modifications made from one version to the next.
You need to provide an appropriate versioning strategy for your software products if you want to avoid dependency hell. However, occasionally changes that are merged into the main branch cause confusion about which number, major or minor, should increase. We’ll go over a few examples below that may help you decide which number to increase when releasing your product.
Additionally, we haven’t spent much time on hot fixes, patches, or bug fixes, which are rapid fixes for previously released versions of code that eliminate any after-release defects.
The following examples are only a few use cases; some developers may disagree with some of the points, but they are suggested so that you can discuss them among your team members before deciding to actually create your app.
See example below
Teams can adhere to their own set of guidelines, such as the one given above.
I’ve made an effort to cover the majority of use cases that might arise; if I missed any, please let me know in the comments. Additionally, the team may choose to continue changing their build number rather than updating the Major or Minor and patch version, which has a few use cases that we already mentioned. Regardless of your choice, it will assist you in effectively distributing your product. If you are using a multi-rep architecture, this could be a huge aid in preventing dependency management nightmares.
And that’s it. Thank you for reading my post. I really appreciate your time. If you think it’s helpful, please clap or comment. And in the next one, I see you. 🙌
