Updates introducing a breaking change are unwelcome, especially when this happens without warning. Semantic versioning is one of the most popular solutions for this. By Tomas Fernandez.
One of the drawbacks with all of these versioning approaches is that they don’t tell us anything about compatibility between releases. The way to find out is to dig through changelogs.
In the article:
- What is semantic versioning?
- Automating versions with semantic-release
- How to get started with semantic-release
- Semantic versioning with CI/CD
- Disable tags on Semaphore
- Continuous delivery pipeline with semantic versioning
- Extending the delivery pipeline
Semantic versioning is a versioning scheme that aims to communicate the level of compatibility between releases at a glance. It uses a three-part numbering system: major.minor.patch (e.g. 1.2.3) which may or may not be suffixed with special identifiers such as -alpha or -rc1. Maintaining consistent version numbers will help you gain the trust of users and other developers. Good read!
[Read More]